"Codeowner" and "Maintainer" for the Governance repository

[hdamker]

Problem description

The ProjectCharter defines that the TSC has the responsibility for most of the content of the Governance repository, but we haven't a way in place to execute on that properly in case of changes. Currently the main branch is not even protected, with the result that there are no automatic notifications about PRs.

Proposal:

• Protect the main branch in /Governance with Chair and Co-Chairs as Codeowners
• Create a GitHub team with all TSC participants
• Codeowner are responsible to invite the TSC participants for review for relevant PRs and to merge only changes which have the consensus of the TSC

Expected action

• Restrict write access to Chair and Co-Chairs (admin rights are with the CAMARA admin team)
• Create a branch protection rule and CODEOWNERS file
• Create a GitHub team TSC_participants and invite all TSC participants

Additional context

[hdamker]

@eric-murray @bigludo7 WDYT, does the proposal make sense?

[hdamker]

Approved within TSC June 6th.