-
Notifications
You must be signed in to change notification settings - Fork 14
2022.06.16 Editors Meeting
Rosalyn Metz edited this page Jun 21, 2022
·
17 revisions
See invite
- Julian Morley (Stanford)
- Rosy Metz (Emory) *
- Simeon Warner (Cornell)
- Andrew Woods (Harvard)
- Neil Jefferies (Oxford)
(* indicates the notetaker)
-
House Keeping Items
- Any updates to previous action items?
-
Contributed Projects in OCFL’s GitHub
- document was spurred on by OCFL Java
- restructured the document to incorporate feedback from the community meeting the other week.
- Rosy to edit the Contributed Projects in OCFL’s GitHub and send to the editors slack channel. Also pass on to Scott.
-
Review outstanding 1.1 Tickets
-
PR #583. Andrew still hasn't updated this.
- Issue #557. Will close with PR #583
- Issue #565. Will close with PR #583
- PR #606. adds implementations to the homepage. Approved, squashed and merged.
- PR #601. Replaces #590. Approved, squashed and merged.
- PR #600. Include Andrew Hankinson as a previous editor. Approved, squashed and merged.
- Rosalyn to draft release notes via Issue #570
-
PR #583. Andrew still hasn't updated this.
-
Conference timetables
- iPres - Sept 12-16, 2022 in Scotland
- NDSA - October 12-13, 2022 in Baltimore, Maryland.
- presentation submitted. see proposal document. still waiting to hear about voting.
-
Zenodo Integration - what do we want to configure?
- we can have zenodo archive our github repo when we do new releases
- documentation from zenodo
- we would create a 1.0.1 release for the spect that would create the integration with zenodo.
- archiving spec, extensions, and fixtures
- extensions and fixtures we're doing the minimum; for the spec we're doing the creators.
- when do we do a release for fixtures and extensions? dated release for these and we create a release when we add something new.
- neil to test this with extensions, and then move on to the spec.
- Spec
- Extensions
- Fixtures
- Preparing for 2.0 of Spec
- We should do a call for use cases
- How do we get over the travel issues to sit down and work on this?
- Rosy to edit the Contributed Projects in OCFL’s GitHub and send to the Slack Channel
- Rosy to send the Contributed Projects in OCFL’s GitHub document to Scott.
- Neil to test the zenodo workflow with extensions, and then move on to the spec.
- Rosy put something in the Fedora slack pointing them to use cases
- Rosy to merge PR #596 on Monday assuming Andrew doesn't merge it first
- Andrew to update PR #583 to markdown
- Rosy to draft a maintainer model for OCFL related code hosted in their repositories, should be based on Drupal's maintainer model
- Neil to investigate who at Oxford owns ocfl.io
- Simeon to add some of the documentation about implementations to the OCFL homepage
- Andrew will upload older OCFL community videos to Zenodo
- Rosy to draft release notes via Issue #570