Meeting Notes from 07/14/25
Time: 14:00 - 14:30 PM EDT/11:00 - 11:30 AM PDT
Zoom URL: https://princeton.zoom.us/my/jrgriffiniii
Attendees
@James Griffin (Princeton University Library)
@Heather Greer Klein (Samvera Community)
@Chris Colvard (Indiana University)
@Shana Moore (Notch8)
@Daniel Pierce (Indiana University)
Discussion Items
Member Updates
Next Samvera Board Meeting (07/18/25)
Last Partner Meeting was last Thursday
No urgent issues for this WG arose during the last Partner Meeting
RubyGems Permissions
@James Griffin working to develop a tool within a private GitHub repository
Managing permissions using a JavaScript application (prototyped) for interacting with the RubyGems HTTP API
Currently trying to finish the prototype
Samvera GitHub Organization
Auditing Owners and GitHub Authorizations for Samvera Organizations
Ability to assign members into specific groups requires Owner permissions
We require a set list of who can be Owners
Rules for determining the role of who can serve as an Owner
Actively being discussed between Daniel and Heather
Defining Roles
Major Project Contributors and Tech. Leads need to be identified
Community Manager (Heather)
Board Chair
Implementation Timeline: Uncertain
Need to publish an announcement to the Samvera Community
These roles apply to the GitHub Organizations
samvera
samvera-labs
samvera-deprecated
Uncertain as to the permissions at the repository level
There might need to be a defined process for creating a Samvera GitHub repository within the samvera-labs Organization
New contributors without the proper authorization would need have a process for requesting a new GitHub repo.
Also: Heather confirms that there can be less restrictions for samvera-labs Organization
Rubric for identifying Core Components as candidates for deprecation
Samvera existing documentation: Samvera Organizations: Deprecation
Review of existing frameworks
Eclipse Foundation -
Eclipse Foundation Development Process | The Eclipse Foundation
No firm rubric for termination review
Apache Incubator Graduation - https://incubator.apache.org/cookbook/#graduation_readiness_assessment
Apache Incubator Retirement - https://incubator.apache.org/guides/retirement.html
No firm rubric
Apache Project Maturity Model - https://community.apache.org/apache-way/apache-project-maturity-model.html
Apache Attic - https://attic.apache.org/
Suggested guidelines: no active committers, non-responsive, or not able to get 3 votes for releases
A model for software lifespan - http://oss-watch.ac.uk/resources/ssmm
See level 8 summary description - momentum/control beyond single contributor
Discuss the rubric
Aside from Eclipse and Apache, no one could attest to having found any structured, formal approach to deprecating open source components or projects
Should consider the possibility of a revived component or project which was once deprecated and must be repromoted to core due to popular demand or interest
Current Samvera Guidelines
3 institutions is still a fine threshold
3 institutions running in production is different from multiple organizations actively developing without production deployments
Sustainability Maturity Model: There is control which has grown beyond one institution
Idea of two institutions or more for independent, ongoing active development
Do we know of any current Core Components which might be candidates for deprecation in the manner of Apache Attic?
questioning-authority?
There is a pull request for actively maintaining this
It was reviewed!
browse-everything?
Blocked as a dependency within Hyrax
@James Griffin needs to review an old list
Removing ActiveFedora/LDP dependencies from Hyrax remains a blocking milestone for contributors
There will be a list of Gems upon which Hyrax is no longer dependent
Preparation for this and having a framework ready in anticipation
(Please add additional items)