----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25785/#review54053 -----------------------------------------------------------
I think it's valuable to outline some guidelines for anybody interested in becoming a committer, but I don't think we should set too many strict rules and regulations around it. Other thoughts below. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93988> I like how BenH words it as a committer is "somebody who is committed to the project". That's the most important thing, whether they are c++ code committers, build committers, doc committers, website committers, etc. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93998> Let's call out the kinds of things we expect for community participation (IRC, mailing lists, reviewing other patches/JIRAs, etc.) docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93994> 10-20 non-trivial patches seems arbitrarily high. I've seen us call votes for contributors with as few as a dozen patches, and some of them may have been "trivial" by some definition. We should discuss what the actual (non-trivial) patch limit should be. I would be fine nominating somebody with 5 non-trivial patches if they are active in the community and committed to the project. If they are to be a docs or website committer, the requirements could be even less. Maybe we shouldn't even publish a hard limit publicly. Maybe anybody can "ask" to be nominated, and the existing committers can evaluate the requirements for that individual/role. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93990> "code" is relative, since some committers don't even write/commit c++ code. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment94002> Why do you even need to specify real names? An email address and github/jira/review-board handle should be sufficient. I'd nominate an pseudononymous contributor who's been writing awesome code for us. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment94004> Why 10 days? Why not 1 week? How did you arrive at this number? docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93991> Or you need to show more community involvement on JIRA/RB, mailing lists, and/or IRC. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment94005> You can also get access to the Jenkins server, the Maven repo, and possibly the github.com/mesos organization. docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93992> Does that mean we will be revoking committer status from the Berkeley guys who have moved on to other things and are no longer contributing to Mesos? docs/becoming-a-committer.md <https://reviews.apache.org/r/25785/#comment93993> Has this process been used/defined previously, or are you proposing a new process here? How long does the revocation vote last? - Adam B On Sept. 18, 2014, 10:41 a.m., Dominic Hamon wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/25785/ > ----------------------------------------------------------- > > (Updated Sept. 18, 2014, 10:41 a.m.) > > > Review request for mesos and Vinod Kone. > > > Bugs: MESOS-1815 > https://issues.apache.org/jira/browse/MESOS-1815 > > > Repository: mesos-git > > > Description > ------- > > Add a guide to becoming a committer. > > > Diffs > ----- > > docs/becoming-a-committer.md PRE-CREATION > > Diff: https://reviews.apache.org/r/25785/diff/ > > > Testing > ------- > > > Thanks, > > Dominic Hamon > >
