2022.12.01 Editors Meeting

Call-in

See invite

(* indicates the notetaker)

House Keeping Items
- Any updates to previous action items?
- December community meeting cancelled
Preparing for 2.0 of Spec
- Below are some open questions we might want to discuss when we are all present?
  1. Do we need an extensions tag?
    - you can actually transfer tickets to extensions, perhaps that's a better idea.
    - process: tag the ticket as extension, add a comment letting submitter know why we are saying its an extension, they then have a period of time to respond back before we move it over to extensions tickets.
    - created the extensions tag
    - also identified that https://github.com/OCFL/spec/issues/370 can be closed since we have the mutable head extension now.
  2. Should we get community input on spec
    - ask community members for their experiences with ocfl
    - repurpose community calls, broadcast those more widely
    - Neil: identify a DPC session themed with OCFL
    - All: review email list to see if we can identify who to blast at our next meeting
    - All: brainstorm themes to focus on for these "listening sessions" at our next meeting
  3. Should we review Open Issues for the spec
    - hold off on this for now
  4. Should we do a call for Use Cases
    - this is where community input comes into play
  5. When should we identify an in person meeting to begin work?
    - hold off on this for now

Andrew will reach out to Peter about transfer to OCFL repo
Peter and Wisc are to update the readme for OCFL Java after move to OCFL space
Rosalyn move Guidelines for OCFL Projects out of the Google doc and create a page on OCFL.io