On 6/15/11 10:42 AM, Volker Simonis wrote: > So for me the "Author" role is a little artificial, because already > "Contributors" have the right to submit changes. Why do you need > special rights to create changesets for a specific code repository?
A Contributor may or may not have been granted direct push access to a Project’s code repositories. An Author with that right is a Committer. > Moreover the bylaws do not define a way how to become an Author > (except for newly created Projects where the initial Authors are > appointed by the Project Lead). To quote from the final draft: http://openjdk.java.net/groups/gb/bylaws/draft-openjdk-bylaws-10 A Project Lead is a Committer to that Project who is responsible for directing and coordinating the Project’s activities. A Project’s Lead has: [snip] The authority to appoint and remove Authors who are not also Committers; cheers, dalibor topic -- Oracle <http://www.oracle.com> Dalibor Topic | Java F/OSS Ambassador Phone: +494023646738 <tel:+494023646738> | Mobile: +491772664192 <tel:+491772664192> Oracle Java Platform Group ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
