Triple +1 Sent from my iPhone
On Sep 26, 2013, at 9:05 PM, "Alan Gates" <[email protected]> wrote: > Apache culture is frowns on creating specific types of committers. If > someone is focussed on docs (or qa, or whatever) more than code, I think they > should still be a regular committer. Those parts of a software project are > just as important as writing code. In the pig project we voted in a person > who worked just on docs, and it went fine. In general, before you trust > someone enough to make him a committer you should trust him enough to know > his limits and not be checking in patches to parts of the project that aren't > his expertise. > > Alan. > > On Sep 26, 2013, at 7:07 AM, Kevin Minder wrote: > >> Hey Everyone, >> >> My recent change to move most of the release specific docs from wiki to svn >> is likely to create a bottleneck for us. The one thing that I really liked >> about using the wiki was that it had a very low barrier to entry for anyone >> interested in working with docs. Specifically we have direct control over >> the wiki permissions so it is very easy to grant privs. Now this being said >> we have been fairly free (possible too free) in granting those privs. >> Having these docs in svn will require commit privs in that repo for release >> doc updates. >> >> So my question is do we want to distinguish between a code and doc >> committer? If not, what should the process be for making someone a doc >> committer? Does it have to be a formal as it is for code committers? >> >> Kevin. >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader of >> this message is not the intended recipient, you are hereby notified that any >> printing, copying, dissemination, distribution, disclosure or forwarding of >> this communication is strictly prohibited. If you have received this >> communication in error, please contact the sender immediately and delete it >> from your system. Thank You. > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
