feat: adds governance document. #2
Conversation
|
|
||
| Team members may retire at any time by opening a github issue in this repository requesting for removal. | ||
|
|
||
| Team members can be removed by [majority vote](#majority-vote) opening a github issue and voting in the next 48 hours. |
There was a problem hiding this comment.
Since we do have Slack as a backchannel, I'd suggest removal not be in a public issue as it can be sensitive
There was a problem hiding this comment.
Removing people is a painful process for any project. It needs to be there, but I don't have a clear idea of how to do it. Do we know how other open-source projects do this?
There was a problem hiding this comment.
It should consider a on-boarding and off-boarding process
|
|
||
| In case a member leaves, the [offboarding](#offboarding) procedure is applied. | ||
|
|
||
| The current team members can be found under this link. |
|
|
||
| This document describes the rules and governance of the Coraza project. It is meant to be followed by all the developers of the project and the Coraza community. | ||
|
|
||
| ## Community overview |
There was a problem hiding this comment.
Just a share you may have already read it but if not, GitHub's guide is really awesome. Perhaps there are tidbits you can source if you haven't seen it yet
|
|
||
| ### Administrators | ||
|
|
||
| Administrators are team member with access to manage the [Coraza organization](https://github.com/corazawaf). Any change in the organization should be agree upon vote in the `#coraza-core` channel. The role of administrator does not represent any kind of hierarchy among team members. |
|
|
||
| Administrators are team member with access to manage the [Coraza organization](https://github.com/corazawaf). Any change in the organization should be agree upon vote in the `#coraza-core` channel. The role of administrator does not represent any kind of hierarchy among team members. | ||
|
|
||
| For the sake of independence, no two administrators can work for the same company despite the regime (full time, consultancy, etc). |
There was a problem hiding this comment.
If three people are deciding, then two of them should not have the same background.
But if more people are in the mix, then the number must be different. I think the idea is that if N persons if the size of the core, then at most (N/2)-1 people can share the same background, and take over the decisions of the global community.
Closes #1
Ping @corazawaf/core-developers @nacx