Governance Changes #165
Governance Changes #165
Conversation
Signed-off-by: Joe Kutner <jpkutner@gmail.com>
jkutner
requested review from
natalieparellano,
ekcasey,
hone,
jromero,
nebhale,
sambhav and
sclevine
Signed-off-by: Joe Kutner <jpkutner@gmail.com> Co-authored-by: Sambhav Kothari <skothari44@bloomberg.net>
Signed-off-by: Emily Casey <ecasey@vmware.com>
Signed-off-by: Emily Casey <ecasey@vmware.com> Co-authored-by: Joe Kutner <jpkutner@gmail.com>
* Makes requirements for election and removal of maintainers symmetrical * Fixes copypasta error in contributor removal Signed-off-by: Emily Casey <ecasey@pivotal.io>
Governance Clarifications
* consistent casing * typo fix Signed-off-by: Emily Casey <ecasey@pivotal.io>
typographical fixes for governance changes
| * [spec](https://github.com/buildpacks/spec) | ||
| * [rfcs](https://github.com/buildpacks/rfcs) | ||
| * defining and maintaining the technical vision for the CNB project. | ||
| * fostering a healthy and welcoming community, including by defining and enforcing our [Code of Conduct](https://github.com/buildpacks/.github/blob/main/CODE_OF_CONDUCT.md). |
There was a problem hiding this comment.
@ekcasey Is this really the role of a Technical Oversight Committee? Should this be a responsibility of the Team Leads?
There was a problem hiding this comment.
I would say yes, because
- It's the only oversight committee that exists and fulfills other non-technical steering-like responsibilities
- It is responsible for personnel decisions like appointing the team leads and creating a welcoming and inclusive community should be a priority when appointing folks to leadership positions
- We gave the TOC responsibility for governance and project priorities (via the roadmap) and this is related to both governance and priorities.
- We don't say that the TOC is solely responsible for any of these items but "a mandate to drive consensus for..."
It is everyone's responsibility to foster a welcoming community but the TOC should set the example and own the code of conduct document as it does the governance structure.
I would be happy to say it is the combined responsibility of the team leads and the TOC. I thought about adding a Leadership team section that defines leadership team as the union of TOC and leads and assigns shared responsibilities.
There was a problem hiding this comment.
Rename to "Oversight Committee"? ;)
There was a problem hiding this comment.
For context, I was talking to Joe about this and I wanted to empower Team Leads to be able to do this in the community. If this is just part of "governance", then I'm fine with it as is.
In accordance with discussions among the Cloud Native Buildpacks leadership.