Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] New Component Leads in the Eclipse Project

I've noticed that Pawel is not listed as a committer on eclipse.platform.debug. This will be fixed as we continue the alignment process (so that our database matches the group assignments indicated in the bug).

I have turned eclipse.platform.debug and eclipse.jdt.debug into proper projects in the database. At some point, the two new project leads should go to the portal and make sure that the "inherit" bit is on.


On 12/03/2010 01:00 PM, John Arthorne wrote:
That's exactly right Wayne. What we called "components" were always really third-level sub-projects in EDP terms. Each of our new ACLs should represent a sub-project in your database. That alignment is underway now under bug 324772. So, Platform Debug and JDT Debug are sub-projects of Platform and JDT respectively (I thought this was actually already the case for these two). Platform Ant no longer exists as a distinct sub-project.

We will want to keep the metadata minimal for projects at that level to avoid the extra overhead. I expect most or all third-level projects will use the "inherit" flag to avoid having to maintain separate metadata from their parent project.

Wayne Beaton <emo@xxxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

12/03/2010 11:38 AM

Please respond to

Daniel Megert <daniel_megert@xxxxxxxxxx>
"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>, pawel.piech@xxxxxxxxxxxxx
Re: [eclipse-pmc] New Component Leads in the Eclipse Project

We don't formally track component leads. In fact, we don't really have
any notion of "component" in the EDP any more. Components tend to be
more of a concept within a project and tend to be managed via social
convention. Component leadership is therefore also more of a social
convention. Everything that was a "component" is really now a "project"
(or "subproject" if you prefer).

With Bug 324772 [1], we have managed to clean up the UNIX groups for the
Eclipse project. Now, we have started a process of aligning the projects
with these changes.

Platform Ant (eclipse.platform.ant) was flagged as a candidate for
retirement. The project itself is meaningless as it existed only to
provide a distinct UNIX group for committers; those committers (and the
directories they have access to) have been moved (I'm not sure how, but
I believe that information is available in one of the attachments on the

Since Platform Debug and JDT Debug still exist in the new scheme, I'd
like to suggest that we turn them into proper projects and assign the
named committers as PLs. This change should really only mean that these
"projects" will need to have a little portal metadata specified for them
(set the "inherit" flag to true at a minimum). Let me know if this needs
any more 'splainin'.

Please take a look at the list of projects that John has identified in
the bug as retirement candidates and comment appropriately. Note that
none of the listed projects have any actual meaning with regard to
commit rights after the group cleanup.



On 12/03/2010 10:50 AM, Daniel Megert wrote:
> Dear EMO,
> the Eclipse PMC has ratified the following new component leads:
> Michael Rennie for Platform Ant
> Pawel Piech for Platform Debug
> Michael Rennie for JDT Debug
> Not sure whether you need to approve this since this is below the
> (sub-project) level.
> Dani
eclipse-pmc mailing list

Back to the top