On Fri, Apr 4, 2014 at 6:12 AM, Bertrand Delacretaz
wrote:
> Although I have a hard time understanding why people who deserve to
> accompany a podling on graduation do not deserve being on its PMC, the
> solution is simple: the newly established PMC just needs to
> re-establish those people as com
As a practical matter the tlp migration scripts seed the
committer group from the list in asf-authorization for svn.
The PMC is taken directly from the resolution, but if there
is no corresponding group in svn (say UCB applies to
the project) then the PMC chair has to seed the committer
group thems
Hi,
On Fri, Apr 4, 2014 at 12:29 PM, Edward J. Yoon wrote:
> ...When consider TLP graduation, all
> committers should be PPMC members?...
At the foundation level (i.e. in the board resolution that establishes
the project) we don't care about committers, it's only PMC members
which are relevant.
I always was curious about if podling has both a group of PPMC members
and a group of committers. When consider TLP graduation, all
committers should be PPMC members?
On Fri, Apr 4, 2014 at 6:59 PM, sebb wrote:
> There have been a couple of graduations recently where (I think) the
> podling expec
Hi,
On Fri, Apr 4, 2014 at 11:59 AM, sebb wrote:
> ...consider whether it is necessary to allow creation of a TLP with
> additional initial committers not on the PMC.
> If so, what is the process?...
Although I have a hard time understanding why people who deserve to
accompany a podling on gradu
There have been a couple of graduations recently where (I think) the
podling expected to be able to specify the initial list of committers
as different from the PMC. In at least one case the podling did not
realise that the names on the board resolution comprise the initial
PMC.
I think there are
