...
The primary Samvera code repository contains the Samvera community’s current consensus on what we are using, maintaining, and recommending. Ideally, this repository only contains code modules that are being actively used and maintained. Anything that falls into disuse should be a candidate for deprecation.
...
[bulkrax is not a core component but is now promoted out of Samvera-labs to Samvera and should be listed with product owner.]
bulkrax
Product Owner: Rob Kaufman
Core Components - Requirements
Code is stored in a repository in the Samvera github organization https://github.com/samvera and meets the requirements for being there.
Component has a designated product owner.
A participant of the Component Interest Group must have a vested interest in the maintenance of that component, acting as a representative for their institution’s needs.
...
Ensure a release gets cut.
Decide when a release is done, what the version number should be, what will be in a release, ensure the CHANGELOG is updated, and announce the release to the community.
Decide what the policy for your component is in regards to backwards compatibility and which versions are supported.
Own the Backlog
Handle incoming issue labeling
Create tickets for security issues discovered by automated tooling.
Ensure pull requests aren’t sitting around without any response for a long time.
Know what priorities are by being in touch with stakeholders enough to understand what the greatest pain points/desires for features are.
Be able to give the Component Interest Group a gauge of how important a set of work is and when it needs to be done. Have a ready answer for “if we could give you a week of work, what would you spend it on?”
Be able to find answers for “so and so wants to do this with the library, is that a good idea?”
Act as point of contact for questions about the component’s goals and path
Ensure there’s sufficient documentation for the component to be useful
Doesn’t necessarily have to write the documentation, but should know what’s out there and have an idea of what might need to be updated if the scope changes, etc.
Actively participate during sprints to provide guidance and prioritization.
Report on whether the component still meets the requirements for being a core component.
Meets the criteria here: httphttps://samvera-labs.github.io/promotion.htmlatlassian.net/wiki/spaces/samvera/pages/2225111271/Samvera+Organizations+Samvera+Labs#Guidelines-for-Promotion-to-Samvera-from-Labs
Recruit any necessary positions for better maintaining their component.
E.g a technical lead.
...
Please note that Hyrax is not considered a ‘component’ under the definition used by the CCMWG.
active_fedora
Code: active_fedora
Product Owner: Tamsin Johnson
Vital Statistics:
...
...
browse-everything
Product Owner: James R. Griffin III
Vital Statistics:
...
hydra-derivatives
Code: hydra-derivatives
Product Owner: Stuart KennyVital Statistics:
...
hydra-editor
Code: hydra-editor
Product Owner: James R. Griffin III
Vital Statistics:
...
hydra-file_characterization
...
hydra-file_characterization
Product Owner: Jamie Little
Vital Statistics:
hydra-head
Code: hydra-head
Product Owner: Chris ColvardVital Statistics:
hydra-pcdm
Code: hydra-pcdm
Product Owner: Mark Bussey
Vital Statistics:
hydra-role-management
Code: vacant
hydra-role-management
Product Owner: James R. Griffin III
Vital Statistics:
hydra-works
Code: hydra-works
Product Owner: Mark BusseyVital Statistics: vacant
iiif_manifest
Code: iiif_manifest
Product Owner: Karen Shaw
Vital Statistics:
ldp
Code: ldp
Product Owner: Randall Floyd
Vital Statistics:
...
Code:
noid-rails
Product Owner: Justin Coyne
Vital Statistics:
...
Code:
questioning_authority
Product Owner: James R. Griffin III
Vital Statistics:
rubydora
Code: rubydora
Product Owner: Justin Coyne
Vital Statistics:
...
Code: samvera.github.io
Product Owner: Andrew Myers
Vital Statistics:
valkyrie
Code: valkyrie
Product Owner: Alexandra Dunn
Technical Lead: Trey Pendragon
Vital Statistics:
...
bixby
Code: bixby
Product Owner: James R. Griffin III
Vital Statistics:
...
Code:
samvera-circleci-orb
Product Owner: James R. Griffin III
Technical Lead: Collin BrittleVital Statistics:
Gem Release Process
Create a new branch of the following form:
git checkout -b prepare-release-3.2.1
where3
is the major release,2
is the minor release, and1
is the patch release (please see Semantic Versioning for reference).Within this branch, please update the following:
Version number (this is often found within
lib/[GEM_NAME]/version.rb
)The CHANGELOG.md
Any additional documentation and areas of code
Commit these changes (using
git commit
) and push these to the GitHub repository usinggit push origin prepare-release-3.2.1
Create a Pull Request and request a review from
@samvera/maintenance
A member of the Component Maintenance Interest Group should approved of and merge the pull request
One this has been completed, there are now two tasks left (both can be delegated to members of
@samvera/maintenance
):The new Gem release can be published to RubyGems 1. Invoke
bundle exec rake release
1. This requires that one have an account with the necessary privileges on RubyGemsAs this creates a new
git tag
with the version as the tag name, this can be used to draft and publish a release on GitHubPlease notify any member of the Component Maintenance Interest Group, and we can assist by announcing the new release to the
#devs
Samvera Slack Channel and the samvera-tech Google Group.