All, for some context on this discussion (for those that aren't subscribed to 
gene...@incubator.a.o - and BTW, if you aren't, I'd recommend sending an email 
to general-subscr...@incubator.a.o, just for the fun of it!), see here [1]. The 
jist of it is that Joe Schaefer and others like Greg Stein have been proposing 
ideas ranging from incremental shakeup of the current Incubator process, all 
the way to Greg's email thread titled "Radical Revamp"). The idea behind this 
"Radical Revamp" would be that instead of having the Incubator PMC (IPMC) as 
the sole responsible binding VOTEs for the OODT podling (until we graduate), we 
would undergo something like the process I threw in steps 1-7 below (Justin 
correct me if I'm wrong). What's different about that than our existing 
process? Very little, other than, right if we get 3 binding IPMC VOTEs as part 
of our OODT incubator podling (e.g., if Justin, myself and Ian vote +1), we 
still have to check in with the "Incubator PMC" and acknowledge that we as the 
OODT community (PPMC + mentors) voted for a release or a new committer. What 
this proposes is removing the step of "checking in" with the IPMC on releases 
and new committers, and leaving it to the OODT community (PPMC + mentors) to 
decide ourselves, and self-govern.

Maybe it's too radical, or something that's a risk as Justin puts it, and maybe 
having the IPMC come in and bless our podling community decisions is the 
correct thing to do, but I'm open to ideas, and open to participating in this 
"experiment". I don't see that we have a lot to lose. The Incubator isn't going 
away anytime soon, but it might be a good learning experience for us to try out 
some different options as we move towards our goal of TLP.

I'm interested in what others think, of course, after checking the existing 
context (recall [1]).

Thanks!

Cheers,
Chris


[1] http://s.apache.org/ld



On 8/16/10 9:21 PM, "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov> 
wrote:

(moving to oodt-...@incubator.a.o, context coming in separate email FWD)

Hey Justin,

>> +1 from me with my OODT hat on.
>>
>> Also, I like Greg's proposal b/c it puts the onus on those (proposed)
>> $podling.apache.org PMC members who are active, without external "peanut
>> gallery" oversight.
>
> However, I think we should probably have a discussion on the OODT list
> as we should think through what this means and how it'd affect the
> nascent community.  With Subversion, it already had a very vibrant,
> diverse, and self-governing community - OODT isn't quite there so
> there's a bit of a risk there.  Perhaps this will act as a prod to
> promote the self-governance - which is ideally what we want anyway.

+1

>
> At the moment, I probably don't have the time necessary to sit down
> and lead the conversation within OODT.  That alone does give me a bit
> of a reservation about what exactly we're signing up for.  =)  --

To me, all we are signing up for with Greg's proposal is basically to have
something like:

1. oodt.apache.org exists today
2. Ian, Chris, Justin and Jean Frederic are OODT PMC members + committers
3. OODT committers continue as-is
5. There is no more IPMC oversight
5. VOTEs on releases are approved by 3 +1s of OODT PMC members
   - OODT committers weigh in on releases and their weigh in is taken into
consideration by OODT PMC members (as is done today even with PPMC and IPMC)
6. VOTEs on new committers are approved by 3 +1s of OODT PMC members
   - OODT committers weigh in on new committers and their weigh in is taken
into consideration by OODT PMC members (as is done today even with PPMC and
IPMC)
7. When we're ready (we can even keep the same Incubator checklist), we put
up a board resolution to "graduate" into *true* oodt.apache.org TLP. To me,
ready =
   - we've made at least 1 release (we're close!)
   - we've VOTE'd in a couple new committers (keep those patches coming
people!) hopefully with some diversity in mind, but if we don't get there,
and the committers are still vibrant and healthy, then we move forward.

OODT already has a pretty vast user community and healthy community that I'm
slowing working to get signed up over here in the Incubator. We've had
contributions from folks from Children's Hospital (thanks guys!), interest
from other NASA centers (welcome Mark and others!), and some new folks from
JPL stepping up and earning merit (welcome Cameron, and thanks for popping
up Rishi!).

Is that your take too?

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.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++





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

Reply via email to