Skip to content

Define project written Governance #243

Open
@qu1queee

Description

@qu1queee

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.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

  • Status

    No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions