Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define project written Governance #243

Open
qu1queee opened this issue Sep 20, 2024 · 0 comments
Open

Define project written Governance #243

qu1queee opened this issue Sep 20, 2024 · 0 comments
Assignees

Comments

@qu1queee
Copy link
Contributor

Part of #240

Goal

Adopt a form of Governance model for Project Shipwright. This provides in written form the way the project does things, explicitly.
In addition, it should explain the project roles(from contributors to maintainers), the contributor ladder, values, etc.

Please Consider

CNCF provides three templates for governance, see here. I believe we should adopt the Maintainer Council one.

As part of the Maintainer Council, we need to carefully define the following:

  • Values: figure out your actual values
  • Becoming a Maintainer: adjust maintainer requirements
  • Meetings: fill in with how your project communications actually work
  • Code of Conduct: who handles CoC reports?
  • Security Response Team: who handles security reports?
  • Voting: where do Maintainers take votes?

In addition, I propose to have the specification of roles:

  • contributors, approver, maintainer, admins.

Outcome

A PR containing a Governance.md file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants