Page History

...

1. Announcements

2. Fedora Design Meeting Debrief
3. Next Steps:  Sprints
   1. Fedora 6  - https://doodle.com/poll/4am7iqptx5arb4ce
   2. Import Export - https://doodle.com/poll/cshgyw3wr87ivckf
4. Way forward on Camel Tooling
   1. Stay the course (fix karaf) or setup to run without karaf
      1. if run without karaf, what are our options?
   2. vagrant and docker

5. 
   

6. 
   

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

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. Fedora design meeting was successful. Further debrief to come.
2. James Silas Creel indicating that the CAP system has changes and documentation to make it work with alternate authentication systems. These will be ready for a forthcoming release.
3. Camel toolbox is not working and seems to be problematic to move to work with Fedora 5.
   1. Some time needs to be spent on how the parts still work together.
   2. If we are moving to a deployable jar then the structure should considered to allow.
   3. Jared Whiklo will continue to work on the fcrepo-camel-toolbox in Karaf, but a implementation as a JAR/WAR could be.
   4. https://github.com/fcrepo4-labs/fcrepo-camel-webapp - an old wrapper for the fcrepo-camel that allows you to compile in whichever options you want in a single WAR file.
   5. Bethany Seeger mentioned that at Amherst they are working with Gradle and maybe there are simpler fixes there.
   6. Aaron Birkland suggests that each executable component would result in an executable JAR, then each could be deployed separately and connected as needed.
4. Clear resolution on how to map OCFL to LDP model. Review the Fedora 6 sprint document and comment on the page and/or ask questions in Slack.
   1. Transactions are expected to remain, but there is some desire to not have the API change. Perhaps using the sidecar transaction specification for the time being.
   2. Aaron Birkland has written up a high-level summary for JHU which might have people understand the decisions - https://docs.google.com/document/d/1-VXJ3JjtWWUooxCWegptWAUwvCp1SYjgzqZI9a1r45c/edit
5. Actions

•  Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
•  Peter Eichman  will take charge of the fcrepo-camel/fcrepo-camel-toolbox release process.
•  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 the updates to Ben Pennell 's PR for 

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

•  Ben Pennell : to dig up local camel-toolbox code that deploys as a webapp into Jetty... instead of OSGi
•  Jared Whiklo : to take the baton on 

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

•  Peter Eichman : to review 

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

...