incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: an experiment
Date Thu, 12 Aug 2010 07:33:17 GMT
Big +1 to all Greg's comments below. Let's just try it - I don't see a huge effort/loss ratio
- I think we'd all be surprised at how well folks are at responding to requests if we just
ask them to.


On 8/11/10 10:15 PM, "Greg Stein" <> wrote:

On Wed, Aug 11, 2010 at 19:24, Joe Schaefer <> wrote:
>> From: Davanum Srinivas <>
>> To:
>> Sent: Wed, August 11, 2010 6:28:17 PM
>> Subject: Re: an experiment
>> Ant,
>> My personal opinion (and i am hoping!) was that such individuals
>> from ppmc's who end up in ipmc would help build bridges
>> between podlings and  will help get lessons learned (when any ppmc
>> has issues/problems/roadblocks)  back to their ppmc.
>> This is one area where i've seen people struggle, folks  from
>> different projects learning the same lessons the hard way.
> Good point.

Yup. Goodness.

>> I am not  too worried about "binding" vote one podling ppmc
>> member have over another  podling's release. the "binding" is
>> for me a legal thing (as in we need 3  binding ipmc votes for a release).
> I think ant is more concerned about graduation votes.  We
> could simply write a new rule that podling committers on
> the IPMC brought in through my initiative MUST ABSTAIN from
> graduation votes.  I don't think the board would be the
> least bit upset if we did that.

Nah. Don't impose more rules.

In Subversion, we vote in committers and we tell them "only commit to
/some/path". And they do that. We don't need technical measures. We
simply *ask*.

Let new IPMC members know that they should be wary of voting on issues
outside of their "domain of expertise." If they *do* vote, then let
them. If they are out of line, then let them discuss why they
voted/thought that way. It can be a learning exercise. Maybe they'll
change their vote. If you find somebody that just never "gets it" and
is "obstructionist", *then* you can deal with it.

Be optimistic and give them rights. What is the true failure mode
here? What is the full exposure? Is it really a problem? Is it such a
problem that rules are required? [beyond simple social requests]


To unsubscribe, e-mail:
For additional commands, e-mail:

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message