|Re: [eclipse-pmc] Fw: New Component Leads in the Eclipse Project|
The end result should be that the Eclipse project "components" that we still actually require will all become "projects".
Last year's workaround for the metadata inheritance was to just paste the top-level project plan into the projectplanurl field for all subprojects. That said, I'll see if we can move the metadata-related bugs along in time for Indigo (I've already done a lot of work to make the metadata management a lot more flexible, so we can start to entertain doing things like automatically inheriting fields from parent projects).
Wayne On 12/06/2010 04:09 AM, Daniel Megert wrote:
We don't formally track component leads.Yes I do know that and I was in fact not in favor of disturbing the emowith this but the rest of the pmc felt it's noteworthy ;-) And that was actually a good idea! It surfaced that we also have to clean up (or rather: activate) the portal information so that we can conduct the correct votes in the future. As you can see from http://www.eclipse.org/projects/listofprojects.php most of our third-level sub-projects (e.g. Platform UI, SWT, or JDT UI) are not showing up. To be complete we have to populate these with the right set of committers (taken from the ACL) and project lead(s). As John, pointed out, all other information should be inherited to reduce overhead. Unfortunately one has to inherit all or nothing, see https://bugs.eclipse.org/282199. Dani
Back to the top