Page History

...

1. Star master
2. Announcements
   1. Holiday Party follow up meeting :  Monday January 8th at 3PM Eastern 
      
      1. https://docs.google.com/document/d/10TpyqAVgy110Zph_aYAH-bJIfNZr4Vj1e3-vhTfUv4U/edit#
      2. Shall we put it out there.
3. 4.7.5 release - Planning for week of January,15th 2018
   1. Shall we push it out a week?  
      1. Announcement needs to be sent
   2. Release manager - Osman Din ? Need confirmation
   3. Volunteers
      1. Testers
         1. Danny Bernstein
         2. Joshua Westgard
         3. Peter Eichman
         4. ?
      2. Someone to review 4.7.5 commit message for signs of missing documentation?

      3. Preparers of Module Release Candidates

         Module	Who?
         fcrepo-module-auth-rbacl	Osman Din
         fcrepo-module-auth-xacml	Osman Din
         fcrepo-module-auth-webac	Osman Din
         fcrepo-mint	Osman Din
         fcrepo-audit	Osman Din
         fcrepo-webapp-plus	Osman Din
         fcrepo4-vagrant	Osman Din

         
         

   4. Resources:
      1. component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
      2. Release Testing - 4.7.5
4. Fedora API Test Suite... needing:
   
   1. Try the tool against an API implementation
   2. Code reviewing the tool... lots of low-hanging fruit
5. Simple, synchronous query in Fedora
   1. What will it take to make this happen?
   2. Prior art
   3. Queries to support
      1. select ?s where {?s ?p ?o}
      2. select ?s where {?s <some-pred> ?o}
      3. select ?s where {?s <some-pred> <some-object>}
   4. Michael Durbin:  do we have a link to the document tracking  known limitations of modeshape implementation and requirements?
6. Tickets requiring attention

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2520

      - Bethany Seeger
      1. Any more discussion needed here?  If a mimetype goes in, it should come out at the very least. 
      2. Bethany Seeger suggested an alternative implementation: https://github.com/fcrepo4/fcrepo4/pull/1272#issuecomment-353173508 that would move the check closer to the HTTP layer
      3. Ralf Claussnitzer: Sounds reasonable. HTTP servers should respond with BAD REQUEST if given an unparsable mime type string.  Should the repository layer check again?

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2659

      - Ralf Claussnitzer to explore?

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2650

      - Ben Pennell to explore?
      
      
7. 5.0.0 release
   1. API Alignment
   2. Pairtrees?
      1. Esmé Cowles : status of proposal and/or any feedback from community? 
8. Beyond 5.0.0 - Areas of improvement
   
   1. Persistence?
   2. Journaling?
   3. Simple, synchronous query?
9. ...

10. Tickets In-Review

    Expand
    Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=14307 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

    
    

...