...
The Samvera Core Component Maintenance Working Group was established within the guidelines of the Samvera Interest Group/Working Group framework (https://wiki.lyrasis.org/pages/viewpage.action?pageId=87460622) to to facilitate the community with the active maintenance of existing Ruby Gems and Rails Engines which have been maintained and are actively used by members of the Samvera Community. Unlike other Working Groups, the Component Maintenance WG has been rechartered consistently in a series of “phases”; this has been done in compliance with the IG/WG framework, with each phase having a defined conclusion date, and a discrete number of deliverables.
History of the Working Group
- Phase 1
- Chartered initially to run from 01/18 - 04/18 (Spring 2018 Samvera Partners Meeting)
- Phase 2
- Chartered to run from 04/18 (Spring 2018 Samvera Partners Meeting) - 10/18 (Samvera Connect 2018)
- Two Community sprints were successfully held
- Phase 3
- Initially chartered to run from 01/19 - 04/19 (Spring 2019 Samvera Partners Meeting)
- After discussions at Samvera Connect, charter was extended on 03/01/19 to run instead until 10/19 (Samvera Connect 2019)
- Two Community Sprints were successfully held
- Waffle.io closed May 16th, 2019
- Decided to proceed with GitHub Projects in its absence
- Phase 4
- Chartered to run from 10/18 (Samvera Connect 2018) - 04/19 (Spring 2019 Samvera Partners Meeting)
...
During Phase 1 of the Working Group, a list of technical () and administrative requirements () were were defined in order to provide some mechanism by which to determine whether or not a Samvera project can be considered a Core Component. Further, it was determined by the Working Group at this time that projects which have been reference by the community as “solution bundles” are simply too complex to be considered a component which this WG could reasonably maintain. This includes (but is not limited to) the following projects:
...
However, beyond these criteria and noted exceptions, Core Components compromise many of the projects which one finds within the Samvera samvera GitHub Organization. By the conclusion of Phase 1 of the Working Group, an actively-curated list for the Core Components was published to the Samvera Community Guide (https://samvera.github.io/core_components.html).
...
Much of the effort within Phase 1 and Phase 2 of the Working Group were directed at first defining the requirements for a Core Component, and then mobilizing members of the Working Group in order to ensure that any existing Ruby Gems or Rails Engines under the Samvera samvera GitHub Organization either met the requirements, or were deprecated and moved to a separate GitHub Organization. This organization is samvera-deprecated, and is reserved for projects which are no longer actively maintained or used by the majority of the community.
...
The process of deprecation is not solely undertaken with the discretion of this Working Group, and the Community Guidelines describe the process for this as well (https://samvera.github.io/deprecation.html). The formal process of deprecation does require that a call be made to the samvera-tech Google Group to deprecate the project, and a 30-day window is required in order to provide all community members with the opportunity to intervene and guide the Working Group in ensuring that the project meets Core Component requirements. An example of this process can be found in the following discussion thread: https://groups.google.com/d/msg/samvera-tech/2Ul7fumgJbA/qr9BsZSDAAAJ
...
Following these initial achievements was the determination of a set of guidelines by which to ensure that projects within Samvera which were under active development could remain publicly accessible and used in production, but also separated from proper Core Components. This organization is samvera-labs, and is reserved for all members in the community with a proper Contributor License Agreement to freely publish and share their own experimental projects.
Further, these efforts defined the steps for a process of promotion, such that should a popular project be developed to eventually meet the community requirements to serve as a Core Component, it could then be moved into the Samvera samvera GitHub Organization. As as the case with deprecation, the process for this is also outlined in the Community Guidelines: https://samvera.github.io/samvera_labs.html#guidelines-for-promotion-to-samvera-from-labs. Requests for promotion are also issued to the samvera-tech Google Group, and these typically also include a call for a community member to serve as a Product Owner. Please see one case for such a call: https://groups.google.com/d/msg/samvera-tech/3nR6aWRCsE4/DyO9FzuVDQAJ
...
| Lifecycle Process | Initial Project Status | Tasks | Final Project Status |
|---|---|---|---|
| Audit | (pre-existing samvera project) | Updated to meet requirements | samvera |
| Deprecation | (pre-existing samvera project) | Call for deprecation issued to the community | samvera-deprecated |
| Promotion | samvera-labs | Updated to meet requirements and call for promotion issued to the community | samvera |
At this point in time, there has been no request to extend these guidelines in order to provide for a process by which to ensure that projects which have been moved to samvera-deprecated can be revived/repromoted to samvera. Should there be any interested in addressing such a case, this Working Group would be eager to engage with the interested parties and assist with defining this.
...