...

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.

Documentation

Documentation requirements are explicitly stated within the technical requirements for promoting projects to a Core Component (https://samvera.github.io/samvera_labs.html#documentation-requirements), but it should be noted that there is quite a bit of standardization in the Markdown for these files. As stated in the guidelines, the following files *must* be present in order to become a Core Component:

• LICENSE
• README
• CONTRIBUTING

However, it should be noted that the following files are also typically included within a given project:

• SUPPORT
• CHANGELOG

Regarding the templates for these, there is no existing, separate GitHub repository which provides the updated text for many of these files. It is recommended that one contact the current chair for assistance in meeting the documentation requirements.