[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-architecture-council] [Bug 301065] New: EDP Does not make clear the role of a container project
- From: bugzilla-daemon@xxxxxxxxxxx
- Date: Wed, 27 Jan 2010 15:50:51 -0500 (EST)
- Auto-submitted: auto-generated
- Delivered-to: email@example.com
Product/Component: Community / Architecture Council
Summary: EDP Does not make clear the role of a container
Classification: Eclipse Foundation
Component: Architecture Council
Container projects are little more than organizational units according to the
EDP. Many container projects do have websites. Some provide consolidated builds
Are container projects more than this. Currently, for example, there is no
requirement that a container project's leadership authorize the creation of a
new operating (sub) project. That authorization comes from the PMC. In fact, a
container project's leadership plays no explicit role in any milestone for its
Does it need to? Do we really need more process here?
If all the authority for operating projects comes from the PMC, what is the
role of a container project's leadership? Project leadership can, for example,
have authority over which operating projects will participate in a consolidated
build/download. They likely have authority over the content of the website.
Is the leadership of a container project a "mini-PMC"?
Or is the container project really just an organizational unit?
Some container projects, for historical reasons, have code repositories. The
leadership of these projects have the same responsibilities as those of
operating projects. The EDP currently prevents container projects from having
code repositories. Is there some good reason why they can't have one?
Organizationally, so long as the container project's directory structure is
separate from that of the contained operating projects, I don't see how this is
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.