This is a great discussion for our community to have. I wonder if other Apache communities have a similar document detailing their guidelines. Something to keep in mind as we form our guidelines is the overall Apache view of committers (from https://community.apache.org/contributors/):
Becoming a Committer There is nothing at The Apache Software Foundation that says you must write code in order to be a committer. Anyone who is supportive of the community and works in any of the CoPDoC areas (*Co*mmunity, *P*roject, *Do*cumentation, *C*ode) is a likely candidate for committership. Apache is a meritocracy. That is, once someone has contributed sufficiently to any area of CoPDoC they can be voted in as a committer. *Being a committer does not mean you commit code, it means you are committed to the project. (emphasis added)* One of the key contributions people can make to the community is through the support of a wide user base by assisting users on the user list, writing user oriented docs and ensuring the user viewpoint is understood by all developers. A main idea behind being a committer is the ability to be a mentor and to work cooperatively with your peers. Some of those users become committers in their own right. Some will test code, some will write documentation, some will do bug triage and some will write code. On Thu, May 21, 2015 at 9:56 AM Christopher Shannon < [email protected]> wrote: > I usually like to create Jira tickets and submit pull requests for them > without first bringing it up on the dev list. I find it's easier to discuss > the issue directly on Jira after I have a patch already created. I think > it gives the reviewer a better idea of what I'm trying to accomplish and > they can provide more useful feedback if I've submitted something to > review. Plus the issue on Jira gets linked automatically with the commit > so it is easy to view later. > > I agree with Thiago that having a guide is welcome because I've also been > wondering what is required to become a committer on ActiveMQ. > > On Thu, May 21, 2015 at 11:59 AM, Clebert Suconic < > [email protected] > > wrote: > > > > Also, when offering pull requests, have they created a JIRA issue? Have > > > they discussed their issue on the mailing list? Etc. > > > > Pull requests comments are sent to the dev-list. I don't think we > > should enforce discussion on the list before a Pull Request. It's nice > > in some cases but that's a case by case I think > > >
