11:00 AM CDT
https://northwestern.zoom.us/j/733419043
Attendees:
Discussion items:
Item | Who |
|---|---|
Debrief on partners meeting and define next steps | |
Membership rotations | |
Marketing WG would like us to provide input on this page https://samvera.org/samvera-open-source-repository-framework/technology-stack/ | |
Suggested topic: planning for cross-tech coordination |
|
Notes:
Debrief
Partners meeting notes: 2021-07-09 Partner Call
Presentation: https://docs.google.com/presentation/d/1n0XTci1dZl4g79_r8sddPTEpWQRmkkwhkiNE3bVS4Vg/edit#slide=id.ge1db9c2dd4_0_133
We said next we would work on: develop cross-technology collaboration, coordination, and code reclamation
What are our next steps to start this process?
Starting with bringing DOI back to core
emailing the 10 institutions to ask what level of collaboration they are up for? Can they give dev time to add their code to the core. How does that relate to Hyrax tech role? No need to go through them. Our ask is for a PR to move to Hyrax core. If there’s a few places with requests, then there will have to be coordination with each other to share their PRs and discuss. One place interested, just work with them.
Defining how the feature works in the UI. When is it minted after publishing, or when it is added but not yet reviewed? Should start with who is interested.
GLOBUS is another, could be another good candidate.
Membership rotations
IG reps in this group can (and should!) rotate. Feel free to request someone else represent your group.
Tech stack page
Please review: https://samvera.org/samvera-open-source-repository-framework/technology-stack/
Is this still accurate?
Needs a re-write. Jon will do a rewrite and share.
Proposal https://docs.google.com/document/d/1bwJO9dl4x8oLpQ-NoDNoV9xDW9YK3gGw6-3saviHjYU/edit?usp=sharing
Heather is launching Aug 31st, will send this group the wiki info when it is ready for review
Planning for Cross-Coordination: Next meeting will want to have everyone available to discuss how the work if different technologies overlap and what can be done to coordinate any work impacting or required by multiple technologies (ie what Hyku needs from Hyrax, when the Avalon team will be available for Hyrax work and what they will need, core components that need maintenance help, etc.). We can use this information to plan the maintenance work coming from pledged hours in 2022. We can also share this in an update at Connect, so the Community is aware.
Action Items: