Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora 
  

  • Dial-in: 
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

• Join fedora-project.slack.com on the "tech" channel

Attendees

1. Danny Bernstein
2. Andrew Woods - out
3. Aaron Birkland 
4. Bethany Seeger 
5. Ben Pennell 
6. Jared Whiklo 
7. James Silas Creel 
8. Yinlin Chen 
9. Peter Eichman
10. David Wilcox
11. Jon Roby

Agenda

1. Announcements

   1. Upcoming 2019-02 Fedora Design Meeting
2. 5.0.2:
   

   1. Release manager: Yinlin Chen

   2. New Date: February 11th?

   3. Release Testing - 5.0.2
   Ecosystem release/development policy review

3. Status on current tools:

   1. fcrepo-camel 
      1. https://github.com/fcrepo4-exts/fcrepo-camel/pull/149
   2. and fcrepo-camel-toolbox toolbox
      1. Outstanding PR:  https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/pull/142
         1. Question:  snapshot releases to sonatype
      2. updating fcrepo-parent to 5.0.1 and other dependencies has proven to be complicated.  
         
         1. (branch to go here)The current state of the work: https://github.com/dbernstein/fcrepo-camel-toolbox/tree/update-fcrepo-parent-pom
   3. fcrepo4-vagrant 
   4. fcrepo4-docker
      1. Please review this PR: https://github.com/fcrepo4-labs/fcrepo4-docker/pull/35
4. Next steps for import/export/4→5 migration
   1. Proposal: Two pronged attack
      
      1. round-tripping 5.x data (add support for versions and webacs)
      2. fcrepo-migrate:   transform 4.7 export into 5.x export
   2. A starting list of Jiras

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

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

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

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

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

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

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

5. 5.1.0 
   1. Ready for review
      

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

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

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

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

      5. "Check if metadata is available in commons.js" : https://github.com/fcrepo4/fcrepo4/pull/1499
   2. TODO
      Issues that are ready to be worked:
      

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

6. <your issue here>

7. Please squash a bug!

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

   
   

8. Tickets resolved this week:

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

   
   

9. Tickets created this week:

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

   
   

Minutes

1. There will be a Fedora 6 design meeting. One of the main task is to replace Modeshape with OCFL.
2. Fedora
3. Announcements
   Nothing in particular
4. 5.0.2 Release Candidate - 2
   Off to the races!  Yinlin has taken role of release manager.
5. Ecosystem release/development policy review
   Yinlin had asked about the fcrepo4/docker project in the context of policies on merging PRs.  There’s no official policy on the labs repositories unlike the extensions or main repositories.  This is justifiable since there’s no guarantee of support for labs repositories’ code. But naturally, people can/should request reviews of PRs as a best practice.
6. will be released today
7. Fcrepo-camel and Fcrepo-camel-toolboxStatus on current tools 
   
   1. Need help! People who used in the past or had experience on building these two projects, please help!
   2. Build issues in this PR: https://github.com/fcrepo4-exts/fcrepo-camel/pull/149 (Peter and Andrew will provide help). 
   1. fcrepo-camel and fcrepo-camel-toolbox
   : the latter has some commits to master intended for release 4.7.3 that Peter’s using locally.  He asks what the RC policy should be there.  Daniel recommends an evaluation period for the toolbox since it is widely used.  A maintenance branch should be created, an RC tag cut, and a RC announcement should be made, but there’s no need for a wiki page, etc.
   Jared suggests that the maintenance branch may be superfluous as there are unlikely to be additional PRs in the interim. The evaluation period will be 1 week.
   There’s a problem building both camel and camel-toolbox with how they reference the parent pom.  Danny Bernstein will explore updates to fcrepo-camel-tests to resolve PAX Exam issue.
8. Next steps for import/export 4->5 migration
   Daniel’s feeling is that we’re not far away from being able to do this migration.  Two parallel tacks can be pursued.  We can focus on round-tripping 5.x data (exporting version, exporting webacs, and importing versions).  Also, create a new tool that would transform a 4.7 export to a 5 export.  
   It seems reasonable that we’ll make people upgrade to an appropriate version of 4.x before attempting the migration to 5.
   Consensus is that this approach is sound. Documentation will indicate the versions for the export and the import, and wiring in a migration tool at that point will be straightforward.
   Aaron points out that migrating the webacs could be the tricky part, since if there are containment relations between them, these will need to go away, and if there are out-links from any resources to the webacs that are not of the “this is my webac” variety, these will need to be eliminated.
9. 5.1.0
   Item 6.a.v is of questionable value as it’s for a rather customized case – it’ failing tests, but if the PR authors can fix that, it will all be good.

...

1. 1. are now once again connected with Jenkins: https://ci.fcrepo.org/
   2. Update maintainers? 

      https://github.com/fcrepo4-exts/fcrepo-camel#maintainers
      https://github.com/fcrepo4-exts/fcrepo-camel-toolbox#maintainers

   3. Suggest that campel version is decoupled with fedora version and also bump version.

2. Import/export tool, see 

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

3. Introducing CAP https://duraspace.org/introducing-cap-curators-administrative-platform-from-texas-am-university-libraries/
4. Goal in the first quarter is to release Fedora 5.0.2 and 5.1.0 Release

Actions

•  Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
•  Danny Bernsteinto create a JIRA around the problems update the parent past 4.7 and test updating https://github.com/fcrepo4-exts/fcrepo-camel-tests
•  Peter Eichman  will take charge of the fcrepo-camel/fcrepo-camel-toolbox release process.
•  Jared Whiklo  will rebase the PR for 

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

   and make sure Andrew Woods's and Peter Eichman's concerns are addressed.
•  Peter Eichman :  will complete review of 

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

   when Jared Whiklo  is finished with the above.
•  Danny Bernstein  will test  Ben Pennell 's version import PR  for 4.7.5

...