airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (398J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: [DISCUSS] Lowering the barrier: Committter != PMC
Date Tue, 06 Aug 2013 15:16:15 GMT
Hey Suresh,

Can you cite an example of someone that you haven't given the PMC
bit to, because you are weary that doing so would add them to
the PMC even though they don't have interest in the project? I
realize talking about specific people on the public list is not
desirable, so maybe you can give me a count or something or some
indication like "I would have nominated 5 people for the PMC, but
b/c I think they will only code and not e.g., VOTE, *and* because
we are PMC==C, then I didn't nominate them?"

Another way to put it -- can you cite an example of someone who
is on the PMC but who doesn't participate in e.g., VOTE'ing, etc.,
as being a problem with a specific e.g., release VOTE, committer
VOTE, etc., that having someone on the PMC but who didn't participate
hindered in any way? Again, don't have to name names, just examples.

Without such an example, I'm not sure what you are trying to accomplish
here besides introduce a new level in-between (e.g., PMC != C) which
IMO doesn't reduce anything it simply adds (# of emails to send; # results
to tally; length of board ACK waiting period, because it's now x2, etc.)

Just trying to flush out the thing to accomplish here not trying to
be difficult at all.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Suresh Marru <smarru@apache.org>
Reply-To: "dev@airavata.apache.org" <dev@airavata.apache.org>
Date: Tuesday, August 6, 2013 8:12 AM
To: "dev@airavata.apache.org" <dev@airavata.apache.org>
Subject: Re: [DISCUSS] Lowering the barrier: Committter != PMC

>Hi Chris,
>
>Right now to get some one onboard PMC needs a very small demonstration of
>interest in the project. I think introducing a committer only role in
>between removes even this barrier and we can give out commit bit's much
>more easy and rapidly.
>
>Suresh
>
>On Aug 6, 2013, at 10:47 AM, "Mattmann, Chris A (398J)"
><chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> If PMC == C, how will introducing a committer role lower the
>> barrier? Instead it would increase it, no, by making PMC != C.
>> 
>> Sorry just my 2cŠ
>> 
>> Cheers,
>> Chris
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:  http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: Suresh Marru <smarru@apache.org>
>> Reply-To: "dev@airavata.apache.org" <dev@airavata.apache.org>
>> Date: Monday, August 5, 2013 1:03 PM
>> To: Airavata Dev <dev@airavata.apache.org>
>> Subject: [DISCUSS] Lowering the barrier: Committter != PMC
>> 
>>> Hi All,
>>> 
>>> Airavata currently follows Committer == PMC, I am still a supporter of
>>> this model. I think this is the right thing to do and more over we want
>>> all the "doers" to be the ones guiding the project. I am also a
>>>supporter
>>> of the Mattman's law of Open Source which famously quotes we are in
>>> recruiting business. So nothing changes on these, but I am looking to
>>> mitigate some limbo's.
>>> 
>>> I am increasingly noticing contributors who are just caring about their
>>> code contributions and not caring enough to lean the "Apache Way".
>>>While
>>> this is not ideal, I am trying to think on sustainable ways instead of
>>> one-off nudges.
>>> 
>>> This thread is to re-vist this topic and see if introducing a
>>>commmitter
>>> only role and much more lowering the barrier in giving committership
>>>will
>>> reward and motivate few more contributors. The only advantage is we can
>>> safely recruit commmitters based on the signs for potential to
>>> contribute. When they make actual contributions and are thinking for
>>>the
>>> project entirely, assisting users and release process and in other
>>> project activities, we make them PMC members.  This will essentially
>>>make
>>> Airavata PMC != Committters. The roles are clearly defined at -
>>> http://www.apache.org/foundation/how-it-works.html#roles This
>>> 
>>> Thoughts?
>>> 
>>> This is a discussion thread only, so every one (not just current PMC)
>>> please voice your  opinion on this topic.
>>> 
>>> Suresh
>>> 
>> 
>


Mime
View raw message