In general, from painful experience, I do encourage distinguishing
between the two. I agree with David that right now it's less of an
issue. My rule of thumb is:
1. if you trust one with the code: vote him as a committer
2. if you trust one with shepherding the community: vote him a (P)PMC
member.
Usually there is some extra mentoring needed to jump from 1. to 2. In
your case, Daniel seems to be ready for PPMC, I believe both is best.
My $0.02,
Hadrian
On 03/06/2015 02:05 PM, David Nalley wrote:
Hi folks,
I wanted to bring up this discussion. It may have already been
discussed, but I couldn't find a record of it in a brief search.
Currently all committers are also PPMC members, but if/when we go
about adding contributors, do we want to make a distinction between
committers and PPMC members?
Many large projects do make a distinction; it allows them to give
commit access easier. For a podling the only real addition you get by
being a PPMC member is being added to the private list and having a
say on new committers/PPMC members. Once you graduate you get binding
votes on releases, as well as more certain control over the direction
of the project.
This project is relatively small in terms of numbers of committers at
this point, so I'd tend to lean towards committers being PPMC members
by default.
Thoughts, comments, flames?
--David
