Call-in

See invite

Attendees

• Julian Morley (Stanford)
• Rosy Metz (Emory)
• Simeon Warner (Cornell)
• Andrew Woods (Harvard) *
• Neil Jefferies (Oxford)

(* indicates the notetaker)

Agenda & Notes

1. Review previous action items
2. Version 1.1 of Spec
   1. 1.1 Milestone
   2. Update on communications to the community (see action item)
3. Spec
   1. Open PRs
      • PR #556 - Waiting on JM or AW
      • PR #550 - Waiting on JM or AW
   2. Open Issues
      • Issue #555 - Do we want to request a use case OR do we want to write one OR something else?
4. Extensions
   1. Open PRs
   2. Open Issues
5. Fixtures
   1. Open PRs
   2. Open Issues

Notes

1. Review previous action items
2. Version 1.1 of Spec
   1. 1.1 Milestone
      • Ready for review = we have a suggestion give a thumbs up
      • Needs Discussion = we aren't sure what we're going to do; add it to an agenda to discuss
      • Folks should look at the milestone and pick up ones that don't have either of the tags above.
   2. Update on communications to the community (see action item)
      • Neil hasn't done this yet.
   3. Issue #543 - confirming what we agreed upon, some notes added to the ticket.
3. Spec
   1. Open PRs
      • PR #556 - approved and merged by JM
      • PR #550 - SW needs to make some updates requested by AW
   2. Open Issues
      • Issue #555 - Neil will ask the EARK folks to write a use case; there are some real things to talk about here. Perhaps a sidecar file that talks about what's in the tar file. But yes a use case would help us with discussing when we get to 2.0.
4. Transitioning to Markdown
   1. it would make it easier to create a text version of the spec
   2. do we want to do it for 1.0? not really sure...because work...but maybe?
   3. we are agreed to move it to markdown for 1.1.
   4. Simeon will move this to markdown

Action Items

• Simeon will move the spec and implementatin notes to markdown
• Neil will ask the EARK folks to write a use case around Issue #555
• Andrew will upload videos to the Zenodo community
• Andrew to finish reviewing outstanding issues for inclusion in 1.1
• All to look through the 1.1 "Ready for Review" issues and see what they can pick up

Previous Action Items

• Neil to look into Zenodo for hosting our community meeting videos.
  • Neil set up a community for us https://zenodo.org/communities/ocfl
  • There are github integrations if we need it
• Neil to draft 1.1 release process
  • Include: community review of at least one month
  • Include: period for iteration/response to community review
  • Include: requirement for creation of fixtures and validators prior to 1.1
• Andrew to categorize outstanding 1.1 git issues into: non-controversial issues, requiring broader discussion, etc

Future Agenda Items

1. Preparing for 2.0 of Spec
   1. Review use case repo during our next meeting