Hello All, I’ve noticed that while some Apache projects lay out explicit guidelines for becoming a committer, others keep it more informal and less transparent. To help align expectations for current and future contributors (even though I learned that such a role is offered and not requested) , I would like to start a brief discussion on what the typical path to committership looks like for this project.
Some Apache communities adhere to the *CoPDoC* framework to clearly outline the expectations across non-code and code contributions alike: - *(Co)munity:* Active interaction (e.g. bi-monthly meeting) - *(P)roject:* Participating in feature discussions. - *(Do)cumentation:* Writing user-oriented guides, examples, and improving the website. - *(C)ode:* Submitting high-quality code (requiring minimal changes for it to be merged), adding tests and fixing potential related bugs. Note (especially concerning the non-committers long term active members of the project): Isn't tying committership merit solely to a high bar code-wise (which is to be defined) actually creating too high of a barrier to join as a PPMC? Additionally, how is the decision to initiate a vote for a new committer reached? Thanks for this clarification. With best regards.
