On Fri, 2010-05-07 at 10:17 -0400, Ben Cotton wrote:
On Fri, May 7, 2010 at 12:08 AM, Nick Bebout <nick(a)bebout.net>
wrote:
> These are the possible ideas I've heard so far:
>
> 1. Separate groups for each document as it is now, but give document
> owners and other experienced members sponsor status
>
> 2. Use "docs" as the commit group for all of our documents.
>
> 3. Use "docs" as a tracking group for all docs project members, grant
> "gitdocs" to give commit access to all documents when the member gets a
> little experience. (Eliminate the separate groups for each document.)
>
> 4. Change nothing
I pick #3. It strikes the best balance between ease of use and still
keeps training wheels for the new members.
(I loved the jumping-off-the-roof analogy that Sparks offered.
Probably because I enjoy jumping off of things so much.)
--
Ben Cotton
I like #3 but modified with some #1, about having more sponsors for
members that are comfortable. It does/would make it easier with more
members able to help out with sponsorship during hackfests and bug
stomping party's.
Eli