Request for formal governance documentation and additional maintainers

[mnm678]

As discussed in the 6/25 weekly meeting, there are a lot of unmerged prs sitting in this repository. To address this, it would be nice to have a more formal process for getting prs merged, such as approval from multiple maintainers. To this end, we need more than 2 people able to approve and merge prs.

[mnm678]

I would also like to put myself forward as a potential maintainer.

[dlorenc]

I second @mnm678's nomination!

I'd also like to nominate @sudo-bmitch and myself (@dlorenc).

[trishankatdatadog]

I second @mnm678 @dlorenc and @sudo-bmitch.

I'd like to nominate myself, too, as a representative for Datadog who has a clear interest in this moving forward.

[dlorenc]

Ref #55

[gokarnm]

I would like to nominate myself as a potential maintainer as a representative for AWS (@gokarnm). AWS has been involved in contributions to this project and is interested in moving this project forward.

[trishankatdatadog]

To this end, we need more than 2 people able to approve and merge prs.

As with Uptane, which has stakeholders from multiple orgs, I recommend that reviews gather approval from not just more than 2 maintainers, but maintainers from separate orgs.

[lachie83]

I will work on getting a GOVERNANCE.MD together taken from other projects in the CNCF.

[sudo-bmitch]

For completeness, I'm happy to volunteer myself as a maintainer. (GitHub ID @sudo-bmitch)

[anvega]

In addition to the great list of folks nominated thus far, I'd like to also submit @nishakm and @joshuagl for consideration. Should both of them be willing, I think both possess the ability to help maintain the project in an official capacity.

[anvega]

A starting point might be to arrive at a proposed number of maintainer seats. The number chosen should account for what represents a healthy distribution of responsibility/load given the current and projected volume of project activity. Typically, an odd number is highly desirable for dispute resolution.

A project that has gone through plenty of deliberation and refinement of its governance procedures is the spiffe project. Here are couple links that might serve as a reference to extrapolate from:

• Governance
• Maintainers

[lachie83]

Please review #78. The idea was to start with a lightweight governance structure to establish who the maintainers are and the process to become a maintainer. Once we get initial quorum of maintainers they can then choose to further build out the governance structure.

[lachie83]

A starting point might be to arrive at a proposed number of maintainer seats. The number chosen should account for what represents a healthy distribution of responsibility/load given the current and projected volume of project activity. Typically, an odd number is highly desirable for dispute resolution.

A project that has gone through plenty of deliberation and refinement of its governance procedures is the spiffe project. Here are couple links that might serve as a reference to extrapolate from:

• Governance
• Maintainers

These are a great set of docs. Thanks for sharing. In addition, I've also seen this format which has come from the some of the members of SIG Contributor experience https://github.com/openservicemesh/osm/blob/main/CONTRIBUTING_LADDER.md.

[nishakm]

In addition to the great list of folks nominated thus far, I'd like to also submit @nishakm and @joshuagl for consideration. Should both of them be willing, I think both possess the ability to help maintain the project in an official capacity.

I'm in! Happy to volunteer as a maintainer :)

[joshuagl]

In addition to the great list of folks nominated thus far, I'd like to also submit @nishakm and @joshuagl for consideration. Should both of them be willing, I think both possess the ability to help maintain the project in an official capacity.

I appreciate the nomination, I'd be very happy to help.

[lachie83]

@justincormack is working on this here notaryproject/notary#1606

[dtzar]

Closing this out since we do have a formal governance document. If you'd like to get involved in the project as a maintainer for notary v2 (notation), showing up meet twice a week on the community calls is a good start.