...
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. Hence, a lifecycle has emerged which yielded the following management workflows:
| 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 | samvera-deprecated |
| Promotion | samvera-labs | Updated to meet requirements | 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.
Product Owners and Technical Leads
As an administrative requirement for GitHub projects to remain in samvera or be promoted from samvera-labs, for each project which can be considered a Core Component, there must be a single member of the community who volunteers to serve as the Product Owner of a project. This process consists of simply notifying the community of their willingness to serve as the Product Owner using either the samvera-tech Google Group (https://groups.google.com/forum/#!forum/samvera-tech) or the Samvera Community Slack (https://samvera.slack.com/).
As enumerated on the Community Guide, there are several duties obligatory for the role of Product Owner (https://samvera.github.io/core_components.html#product-owner-responsibilities). However, it should be noted that these need not actually be exclusively addressed by the single Product Owner alone; the Working Group has understood that there are many cases where it is preferable or necessary to permit the Produce Owner to identify and delegate some of these responsibilities to another community volunteer. This has traditionally been someone in the community who has some deep knowledge of the code base for the project, and this role is defined as the Technical Lead. Unlike the Product Owner role, Core Components are *not* required to have a designated Technical Lead.