2020.07.21 Editors Meeting - OCFL/spec GitHub Wiki

Call-in

See invite

Attendees

  • Julian Morley (Stanford)
  • Rosy Metz (Emory)
  • Simeon Warner (Cornell)
  • Andrew Woods (Lyrasis) *
  • Andrew Hankinson (Bodleian Libraries)
  • Neil Jefferies (Bodleian Libraries)

(* indicates the notetaker)

Agenda

  1. OCFL Nominations
    1. Digital Preservation Awards
    2. NDSA Innovation Awards
  2. Andrew H's departure
    1. Handover of documentation, storage location?
    2. What does Andrew bring to the table that we would like to replace?
    3. What process do we want to use to fill the vacancy?
  3. Extensions
    1. Open PRs
      1. Especially: Extension Naming and Versioning, pr-13
    2. Open Issues
      1. Especially: Establish review and merge policy, issue-21
  4. Use Cases
    1. Clean up of Use Cases
    2. Identify in scope

Notes

  1. OCFL Nominations
  2. Andrew H's departure
    • Early docs to be saved in GitHub
      • Andrew H to create 'history' folder as destination
      • Andrew H to move to OCFL Google Doc, as appropriate
    • Traits of a replacement
      • Diversity (gender, location, race, etc)
      • "Can do" attitude
      • Involved with an implementation
      • From institution that plans on using OCFL
      • From institution for which 1.0 is insufficient
    • Process
      • Seeking nominations
      • Provide criteria
      • Ideally, someone will emerge from community
    • Reflecting on other examples
      • IIIF
      • Open source project committership
    • No immediate urgency
      • For now, we wait
  3. Extensions
    • PR-13
      • ACTION from all to review and get it merged
        • Try to merge by next Editors meeting: Aug 4
    • Issue-21
      • Objective: make it easier to move extensions forward
      • ACTION: Andrew W to draft "Policy"
        • Define potentially long time period for review
        • Need three institutions with up-votes
        • Need two editor up-votes, with no editor down-votes
        • Pull-requests should have title that indicates "final"
        • Apply "ready for review" label when out of draft phase
      • Where would the policy live?
        • wiki?
        • Contributing.md that links to policy
      • Create GitHub group for extensions?
        • Sure... if that would be helpful
        • Group would allow for applying labels... such as "ready for review"
        • Add anyone who has submitted a PR to the GitHub group
    • Pull-requests
      • Are current PRs still "draft"?
    • Open Issues
      • For Neil: Issue-04, -14, -15, -18 may be ready to close
      • For Andrew W: Issue-21

Previous Action Items

  • Simeon to add validation codes to his validator

Action Items

  • Rosy to submit for NDSA
  • Simeon to start submission for DPC
  • Andrew H to create 'history' folder as destination for early docs
  • Andrew H to move to OCFL Google Doc, as appropriate
  • All to review extensions pr-13
  • Andrew W to draft policy for extensions issue-21
  • Neil to review, potentially close extensions issue-04
  • Neil to review, potentially close extensions issue-14
  • Neil to review, potentially close extensions issue-15
  • Neil to review, potentially close extensions issue-18