...
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 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 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
Hence, a lifecycle has emerged which yielded the following management workflows:
...