search

openebs / community

OpenEBS community resources
Apache License 2.0
3 stars 2 forks source link

docs: update GOVERNANCE #48

Closed tiagolobocastro closed 5 months ago

tiagolobocastro commented 5 months ago
  1. You create an GitHub ISSUE in the community Repo, recommending the Maintainers consider your proposal to change the Governance doc. (you don't need to detail your changes in the doc). We need an ISSUE as it is our core reference to this possible event.

Another suggestion is to do it on a PR so everyone can comment inline, rather than a plain issue. I'm not sure how we can convey changes effectively on an issue, perhaps a PR would be better suited.

  • This is why we must have an ISSUE vote first. A PR has a different more relaxed approval process where only a 'reasonable number of reviewers' need to approve a PR. Which is too unsafe for a change to our Governance doc

As long as the same rule is in place, not sure what makes it unsafer. I'd argue a PR is safer, because reviewers would get to see whatever is being modified as opposed to reaching some kind of consensus only for it to diverge in the actual PR. Another approach could be an RFC-line process.

As for your PR... I think jumping to the PR step first, is an accelerating the process a little bit too quickly. As is taking general public feedback/vote in the PR "Review comments" where the Maintainers haven't had a chance to review the conceptual changes first... and refine the language (in a closed safe session).

Ok...

  • For Governance doc changes, we need to be extremely carful & vigilant.

I recommend we put this PR on hold/draft until we achieve steps 1, 2, 3 & 4.

Which is why I raised it as a draft to begin with 👍

tiagolobocastro commented 5 months ago

Closing until we have an established procedure to update the Governance