Copy of Samvera Component Maintenance Announcement

Hello Everyone,

This message is to serve as an announcement and request for support from Samvera Community members.

As some members may be aware, from 2020 onwards, there has been a hiatus on much of the maintenance labor required in order to ensure that Ruby Gems identified as Samvera Core Components [1] comply with those community requirements necessary to classify them as Core Components [2].

In order to address this situation, Heather has led a number of members of the community (who have generously volunteered their time) to assist with identifying possible strategies for remedying this state of affairs.

Following a meeting held on 11/07/22, the group has agreed to propose the following measures:

Request for Updated Product Owners

Please note that these Components currently do not have Product Owners. As such, they would be scheduled for deprecation should no community members be available to serve as Product Owners. Those interested may please contact me using jrg5 [at] princeton [dot] edu, or using the #devs Channel for the Samvera Slack.

This request is to enquire as to who may be available and willing to serve as Product Owner for any of the following projects:

• hydra-derivatives

• iiif-manifest

• ldp

• questioning_authority

Please note that time spent in this maintenance leadership role, and all time spent on component maintenance, can be included in your institution’s pledge hours as part of the 2023 Technology Maintenance Pledge.

Request for Deprecation

After discussions with members of the Samvera Community, it was determined that it may be preferable to please propose that the following project be transferred into the Samvera Deprecated GitHub Organization:

• rubydora

Request for Integration into Hyrax (in support of Valkyrization labor)

The Core Component Interest Group will contact the Hyrax Maintenance Working Group to coordinate with these efforts. It is assumed that the labor for these proposed goals will be concentrated within Hyrax sprints.

• hydra-editor

• hydra-file_characterization

• hydra-head

• hydra-pcdm

• hydra-role-management

• hydra-works

• noid-rails

Request for Integration into samvera/maintenance

• bixby (the Core Component Interest Group can address this)

• samvera-circleci-org (the Core Component Interest Group can address this)

Request to Schedule for Future Deprecation

The Core Component Interest Group will contact the Hyrax Maintenance Working Group to coordinate with these efforts. It is assumed that the labor for these proposed goals will be concentrated within Hyrax sprints.

• active_fedora (a path for full deprecation must be identified, as Hyrax depends upon this until Valkyrization has completed)

• browse-everything (a path for full deprecation must be identified, however there have been discussions related to seeking the usage of a third-party solution)

• http://samvera.github.io (a path for full deprecation must be identified, as there has been discussed a desire to move this to a new GitHub repository, which would include http://samvera.org and hyku.github.io)

Timeline

Following the process for Core Component deprecation [3], we would like to please request that those who are available to assist with these efforts please response within approximately 30 days of this e-mail message (2022-12-30 will be the deadline, as this should account for availability during the holiday season). Should it be necessary to proceed with deprecating any of these components, the accompanying efforts would then be undertaken by the Core Component Interest Group.

[1] https://samvera.github.io/core_components.html
[2]
[3]