Recognize contributors and subprojects #3119
Replies: 3 comments 1 reply
-
Another interesting approach which, given our current growth phase, might be easier to achieve is the one proposed by Strimzi: https://github.com/strimzi/governance |
Beta Was this translation helpful? Give feedback.
-
The Strimzi approach it's quite more simple and basic, the one from the CNCF it's strict in a couple of rules and leave us some space to make our own model, which it's kind of nice. I think we can properly take the general rules from CNCF model and apply some specific designs from the Strmizi model, what do you all think? Regards! |
Beta Was this translation helpful? Give feedback.
-
See #4454 |
Beta Was this translation helpful? Give feedback.
-
Initially, we decided to open source CloudNativPG and adopt a simple governance model based on maintainers. At that time we used the related CNCF template as a base.
While this was the right choice at start of the project, it is proving to be inadequate for several reasons, primarily:
The idea could be to move to the next stage, by partially using the subproject template provided by the CNCF as a base and slowly integrate it in our governance model (not necessarily entirely - for example I don't think we are ready yet for elections). Subproject might need more autonomy and agility to make decisions indepedently, responsibly and in a faster way, without being slowed by the current maintainers' list.
We should also consider the contributor role (or similar) and properly document it in the ladder page.
I would like us maintainers to consider this.
Beta Was this translation helpful? Give feedback.
All reactions