incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes" <>
Subject RE: roles and responsibilities
Date Mon, 22 Sep 2003 03:20:17 GMT
> From: Berin Lautenbach []
> Sent: Sunday, September 21, 2003 6:35 PM
> > From: Stephen McConnell <>
> >
> Steve,
> Had a read.  Great stuff :>.
> One question to all that I have been trying to
> get clear in my head.  What is the break up of
> responsibility between the Incubator PMC and the
> Sponsoring PMC in cases such as XMLBeans.  In
> these cases, the Sponsoring PMC seems to take on
> much of the role that is discussed in the
> document.
> Are people OK with that concept?  If so, I will
> go in and add it to the musings document.
> I would also suggest we create a list of document
> names and possible content for each that we can
> use as the next step to turning this into an
> approved and documented set of policies and
> procedures.
> Thoughts?

If the expected exit is as a sub-project, then the parent project's PMC
should be involved in the incubation; this could be as simple as having the
Sponsor be a Member from that project's PMC. The Podling would be expected
to behave just like any other sub-project of the parent TLP.

On the other hand, if the expected exit is as a TLP, then one of the goals
of incubation should be for the Podling to establish the body that would
become the new project's PMC on exit. This would provide the forum for the
Podling's community to establish its policies and procedures under the
supervision of the Incubator PMC. I would suggest the initial membership
comprise the Sponsor, Shepherd and all initial committers, with additional
members being added according to the policies the Podling defines for adding
members to its PMC once it is a TLP.

In other words, the body behaves as the ultimate PMC would but with the
Incubator PMC responsible for the actual legal oversite. This should smooth
the transition on exit.


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

View raw message