Time/Place

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

• Time: 11:00am Eastern Standard Time US (UTC-5)
• U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
• International toll free:  http://www.readytalk.com/intl 
  
  • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
  • Once on the call, enter participant code 2257295
• IRC:
  
  • Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #duraspace-ff on irc.freenode.net

Attendees 

• Andrew Woods
• Nick Ruest
• Unknown User (acoburn)
• David Wilcox
• Kevin S. Clarke
• Michael Durbin
• Osman Din 
• Stefano Cossu

• Unknown User (escowles@ucsd.edu) 

• Doron Shalvi
• A. Soroka
• Unknown User (daniel-dgi)
• Yinlin Chen

Agenda

1. Islandora/F4 updates
   1. January 30, 2015 Fedora 4 IG meeting notes
   2. Use cases
2. Upgration tooling updates
   1. Mike's progress so far is that he has published a very basic utility that doesn't yet do migration, but has hooks for those things and can right now just:

      a) walk through FOXML from either exported or in the native disk storage format

      b) report

      He was able to run it through one of our repositories here to verify that it indeed could parse all the foxml and locate all the datastreams and didn't encounter any unexpected elements.

      In the coming weeks he will incorporate the fcrepo4-client and actual code to do the obvious migration bits in a parallel with consultation with Adam Wead and others who've looked at (or will soon look at) the problem.
3. 4.1.0 Release
4. Minor version support

   1. After any new minor release, how long will the preceding minor line be supported, if at all? For instance, in the event that a security bug is found in one of the 4.0.0 artifacts, would there be a 4.0.1 fix for that? Or is it the case that, once 4.1 is released, 4.0.x is officially no longer supported, and there will be no further update to that?

5. Review of JIRA tickets
6. Google Summer of Code, ideas
7. ...

Minutes

1. Islandora/F4 updates
   1. Good work happening here
   2. Nick: Should the Islandora use cases get translated into Fedora use cases?
   3. Andrew: Yes, if they are Fedora-appropriate.  Feel free to create a section to group them together.
   4. Danny: Ingest process using Camel: Islandora-specific right now, but should be generalizable.  Aaron added some great transaction support that will be useful for compound object building.  Will be useful both for bulk ingest and upgration.
2. Upgration tooling updates
   1. Mike not on the call, but sent his status via email.
   2. Andrew: There is a design page (Fedora 3 to 4 Data Migration) – please give feedback on the design and how useful the functionality would be for you.
   3. Danny: I will email him because there is definite overlap with the Islandora ingest work.
   4. Esme: Could be a good topic for a lightning talk at Code4Lib next week – people have heard about Fedora 4 for a while, so letting them know about upgrade work could be good to get people interested in helping out.
   5. Andrew: And that could lead to a breakout too.
3. 4.1.0 Release
   1. Andrew: Release just went out, finishing up docs.
   2. Not a huge milestone, but lots of work since 4.0 last fall.
   3. This release is 4.1.0 instead of 4.0.1 because of breaking config changes, RDF vocabulary updates.
   4. Several projects (message-consumer and auth modules) had javadoc errors so they didn't get released to Maven central.
      1. Not a big deal because message-consumer can be downloaded separately, and the auth modules are embedded in the auth WAR build.  But we should make sure that javadoc errors are handled before release (ideally in Jenkins).
4. Minor version support
   1. Aaron asked whether we would create bugfix updates for 4.0.x after 4.1.0 is released.
   2. Esme: Seems a lot like 3.x support, etc.: It would be nice, but may not be practical due to limited resources.
5. Review of JIRA tickets
6. Google Summer of Code, ideas