> On Sept. 19, 2014, 5:24 p.m., Adam B wrote: > > 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. > > Dominic Hamon wrote: > I think exactly the opposite. I think clear guidelines give contributors > goals to attain and allow them to have an aim further than just contributing > to the project. It also reduces friction when deciding who to nominate as a > new committer and encourages the nomination of new committers as contributors > mature.
Taken the number of different views on the topic - isn't it worthwhile to bring to the dev@ list for discussion rather then iterating on a patch? Or have a google doc for mutual commenting / editing? I also have a hard time getting comfortable with establishing a process that haven't been up for vote (but written down anyway) - to put it another way: how can we honor/exercise these rules if there haven't been consensus around them? - Niklas ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25785/#review54053 ----------------------------------------------------------- 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 > >
