Samvera Tech Call 2021-06-23


Meeting Logistics:

Agenda

(meeting notes below)

  • Question from yesterday's Metadata Interest Group meeting: Knowledge base - question about frequency, timelines for updating. There is open PR for updating the MAP. Who to ask? Previously there was a working group doing this work. No longer meeting? Was this the Documentation WG? (Heather)


Moderator: Lynette Rayle (Cornell University)

Notetaker: James Griffin (Princeton University Library)

Attendees:



Meeting Process

 Moderator and Note Taker - click to see meeting process...
  1. Standing pre-agenda items (moderator)
    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items
  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)
  3. Standing post-agenda items (moderator)
    1. call for next moderator and note taker (moderator)
      1. Moderator:
      2. Notetaker:
    2. Samvera help follow-up (moderator)
    3. Pull request review (moderator)
  4. Post-meeting action (note taker)
    1. After call, this week's notetaker should create the agenda for the next call:
      1. Open template agenda titled "Samvera Tech Call 2021-xx-xx"
      2. Click on ... in the top right corner, and select copy.
      3. Popup will open for location. It should contain:
        1. Space: Samvera
        2. Parent page: 2021
      4. Select copy. New page should be created.
      5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish. 



Notes

  • Call for New Agenda Items
    • (No new agenda items)
  • MAP open pull request and the knowledge base for merging pull requests
    • Who to ask regarding who might be appropriate for enquiring regarding reviewing and merging pull requests
    • Is there a Documentation Interest Group? There was one for a Working Group?
    • https://samvera.github.io/core_components.html#samveragithubio
      • James needs to take ownership of this, there was an update for this
      • Lynette does not know of an Interest Group, there wasn't much support
      • For now, the recommendation would be to put out a request for anyone on the samvera-tech mailing list
      • Lynette can review it in order to ensure that this can be integrated without breaking the GitHub Pages site
        • One can clone this and ensure that Jekyll builds the site within a local development environment
    • Tamsin: As a matter of policy, anyone can move this forward
      • Other than this, the gatekeeping mechanism is just to issue a pull request and request a review
      • The Metadata Interest Group should not feel hesitant to merge pull requests, there should not be imposter syndrome over this
    • Heather will relay that one should not hesitate  back to members of the Metadata IG
    • Thomas: Please recall that GitHub is a versioning tool, and is not just for software
    • Heather: Where might someone find the documentation for referencing policies regarding who can/cannot issue pull requests and what is involved in reviewing and merging pull requests
      • There is a CONTRIBUTING.md, but this might not be practically referenced on a regular basis
      • PR Checklist
    • Tamsin: It would be nice to have a bundle of resources which can be offered on a regular basis, particularly as it could be useful for onboarding those who are new to the process of contributing
      • Heather: There is a Confluence Page which can be referenced for this
      • Perhaps enumerate a list of contributions which can be undertaken which do not involve joining and participating in a Working Group
  • Community Updates
    • Starting the half-hour Office Hours sign-up process is going to be addressed soon
      • Aim is to have this addressed within a 2 month period, and will look to try to have leaders present on a topic, or, welcome questions
      • This could be defined pretty broadly
        • Example: Have a developer who has had contributed only a small number of commits discuss their experience with making smaller contributions
      • Propose to meeting every other week (in order to avoid conflicts with the Hyrax Interest Group)
    • OASIS Attorney and the IIIF Repository
      • Michael B. Klein has wanted to move this into the samvera GitHub Organization
      • Anything with a simple Apache 2 license should not require that anything be signed
  • Next Meeting
    • Moderator
      • Tamsin
    • Notetaker
      • James

Meeting adjourned at 09:21PDT/12:21EDT