2022.07.20 OCFL Java Community Meeting

Call-in

See invite

Attendees

• Scott Prater (UW Madison)*
• Arran Griffith (Lyrasis/Fedora)*
• Rosalyn Metz (Emory/OCFL Editor)
• Tim Shearer (UNC Chapel Hill/Fedora)
• Andrew Woods (Harvard)
• Peter Winckles (OCFL-Java author)
• Jennifer Gilbert (National Library of Medicine/Fedora)
• Thomas Edvardsen (National Library of Norway)
• Oliver Schoener (Berlin State Library)
• Robert Stephan (University Library of Rostock)
• Tow Wrobel (Aura @ Bodlein)
• Birkin Diana (Brown Univbersity Library)
• Lucy Wang (Brown University Library)

(* indicates the notetaker)

Agenda & Notes

1. Introductions

2. Brief recap of discussions up to this point

   • UW Madison was developing OCFL-java in-house when Peter was there
   • Currently maintaining the codebase on their University Library Github site and Peter is still maintaining it as a personal project in his own time
   • University is not in a position to be actively maintaining it or developing the code base
   • Need to begin thinking about how to maintain the code as users
   • Code is in a steady state currently - no outstanding bugs
   • When 1.1 spec is released, Peter has a branch ready to be merged
   • Harvard indicated there was a need for performance improvements for S3 reads/writes
   • Where should the code live? Who should be responsible for maintaining the code base?

3. Discussion

   • Rosalyn: code can live in community, but editors not in a position to maintain code; developed Guidelines for OCFL Projects; light governance; OCFL Java could be first project to use guidelines
   • Arran: Shared responsibility to maintain OCFL Java code, not just Fedora techs
   • Tim: concerns: multiple voices, not just Peter; needs more Java developers; best home under OCFL umbrella; it works; how de we make sure it keeps working
   • Birkin: agrees that this model sounds good, exstensible to other projects
   • Robert, Stephan: agree that under OCFL umbrella would be good; willing to contribute, not necessarily ready to take on maintenance
   • Tim: many institutions at Fedora 3; OCFL Java in Fedora 6; OCFL Java may become more visible as people migrate; there may be a higher need for maintenance on it the more people that use it
   • Scott: Optimistic that OCFL Java will be robust and low-maintenance for the foreseeable future

4. Next steps

   • Rosalyn: move repo to OCFL github; need to meet with OCFL editorial board to discuss how to do that
   • Peter: need some documentation updates; could roll in 1.1 changes, too
   • Birkin: do we need a home for 1.0 too?
   • Peter: OCFL Java adds support for 1.1, but is still backwards compatible with 1.0
   • Peter: also change artifacts, package names (remove edu.wisc...); package name changes require implementer changes; lower priority
   • Scott: Roles for new project?
     • Thomas tentatively can commit to some work
     • As can Fedora/Lyrasis and Harvard (Andrew)
     • Peter will be primary committer/maintainer
   • Andrew: Maven group ID: io.ocfl; need to prove ownership of that domain to Sonatype (Oxford: Tom can work with Neal on that)
   • Arran, Andrew: let's schedule more meetings to talk about OCFL Java; to be discussed in OCFL Community meeting
   • Arran: do we need scheduled meetings for this group?
   • Andrew: might be good to have a meeting on the calendar
   • Arran: schedule another meeting after ocfl java is moved over

To Do List:

• Neal, Tom: register ocfl.io domain with Sonatype
• Peter: Update OCFL Java documentation, update Maven package group ID, merge in OCFL 1.1 branch when updated spec is released
• Rosalyn: make OCFL Github beautifuller
• Scott, Peter: Migrate OCFL Java from UW Madison Github to OCFL Github
• Arran: schedule follow-up meeting of this group, set up standing meetings