+1 Makes sense. My rational is that since "Any committer may serve as the manager of a release" http://www.apache.org/dev/release-publishing.html#release_manager then any committer needs access to the whole tree.
Thanks, --Konstantin On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins <e...@cloudera.com> wrote: > Per this thread [1] should we have a single set of committers for the > entire Hadoop project, ie all subprojects? > > If the vote passes, current and future committers will gain commit > rights in all current (Common, HDFS, MapReduce, YARN) and future > Hadoop subprojects. The specific change to the bylaws follows: > > Index: main/author/src/documentation/content/xdocs/bylaws.xml > =================================================================== > --- main/author/src/documentation/content/xdocs/bylaws.xml (revision > 1376823) > +++ main/author/src/documentation/content/xdocs/bylaws.xml (working copy) > @@ -64,10 +64,9 @@ > <li> <strong>Committers</strong> > > <p>The project's Committers are responsible for the project's > - technical management. Committers have access to a specified > - set of subprojects' subversion repositories. Committers on > - subprojects may cast binding votes on any technical discussion > - regarding that subproject.</p> > + technical management. Committers have access to all subproject > + subversion repositories. Committers may cast binding votes on > + any technical discussion regarding that subproject.</p> > > > This vote will run for 7 days. Since the vote represents a > modification of the bylawys [2] it requires a lazy majority of active > PMC members. > > 1. http://s.apache.org/WW1 > 2. http://hadoop.apache.org/bylaws.html > > Here's my +1
