Eclipse/PMC/Unix Groups
Contents
Overview
For historical reasons the Eclipse project has a large number of Unix groups used by its bundles and other content in CVS. This large number of groups is confusing, and creates more work for committers, the PMC, and Eclipse webmasters when performing votes for new committers. Also, we don't conform to the structure defined by the Eclipse Development Process (some components have multiple committer groups). This document describes an proposal to clean up this structure.
Current Structure
The following Unix ACLs are currently used by the Eclipse project:
Platform
(45 active committers, 51 ACLs)
| Unix group | Notes |
|---|---|
| ant-opt | org.eclipse.test, org.eclipse.ant.optional.junit |
| ant-test-ui | org.eclipse.ant.tests.ui |
| core-variables | org.eclipse.core.variables |
| eclipse-all | org.eclipse.releng |
| eclipse-home | Web site |
| eclipse.incubator.e4-dev | |
| forms-ui | org.eclipse.ui.forms.*, org.eclipse.ui.tests.forms |
| plat-ant | org.apache.ant, org.eclipse.ant.core, org.eclipse.ant.launching, org.eclipse.ant.tests.core, org.eclipse.ant.ui, org.eclipse.core.externaltools, platform-ant-home |
| plat-core | |
| plat-core-hpux | |
| plat-core-mac | |
| plat-core-photon | |
| plat-debug | |
| plat-doc | |
| plat-exp | org.eclipse.core.expressions.* |
| platform-feature | org.eclipse.platform-feature |
| plat-help | |
| plat-intro | |
| plat-ltk-ui | org.eclipse.ltk.ui |
| plat-rcp | org.eclipse.ui.tutorials.rcp.* |
| plat-rel-core | org.eclipse.platform, org.eclipse.sdk.tests-feature |
| plat-releng | All other features |
| plat-scripting | org.eclipse.scripting.*, platform-scripting-home |
| plat-search | org.eclipse.search.*, platform-search-home |
| plat-swt | |
| plat-test-perf | org.eclipse.test.performance.data |
| plat-testsboot | org.eclipse.core.tests.boot |
| plat-ua-browser | org.eclipse.ui.browser, org.eclipse.ui.tests.browser |
| plat-ua-cheatsheet | |
| plat-ua-universal | |
| plat-ui | |
| plat-ui-bindings | Data bindings |
| plat-ui-ext-tool | org.eclipse.ui.externaltools |
| plat-ui-home | |
| plat-ui-nav | Common navigator |
| plat-ui-present | R21 presentation support |
| plat-ui-tabbed | Tabbed properties view |
| plat-ui-team | org.eclipse.ui.examples.jog, org.eclipse.ui.examples.presentation |
| plat-update | |
| plat-update-home | |
| plat-vcm | |
| plat-vcm-ssh2 | |
| plat-vcm-team | |
| plat-webdav | |
| rt.equinox.bundles | |
| rt.equinox.framework | |
| rt.equinox.incubator | |
| swt-opengl | |
| swt-text | |
| test-perf | org.eclipse.test.performance, org.eclipse.test.performance.win32 |
JDT
(13 active committers, 9 ACLs)
| Unix group | Notes |
|---|---|
| jdt-apt | |
| jdt-compiler-apt | |
| jdt-core | |
| jdt-debug | |
| jdt-doc | |
| jdt-launching | |
| jdt-manipulation | |
| jdt-ui | |
| jdt-ui-debug |
PDE
(6 active committers, 10 ACLs)
| Unix group | Notes |
|---|---|
| eclipse.pde.api-dev | |
| eclipse.pde.ds-dev | |
| pde | |
| pde-build | |
| pde-core | |
| pde-doc | |
| pde-incubator | |
| pde-junit | |
| pde-ui | |
| pde-ui-tests |
e4
(18 active committers, 1 ACL)
| Unix group | Bundles |
|---|---|
| eclipse.e4 | org.eclipse.e4.* |
Proposed Structure
Guiding Principles
The proposed new ACL group structure has the following guiding principles:
- Each unique set of committers is technically a unique sub-project according to Eclipse development process.
- A sub-project needs at least three active committers to function (i.e., conduct elections, provide backup in case of sickness/vacation/departure of committers).
- Smaller groups with <3 active committers should be consolidated.
- Committers that have been inactive for many years may lose their commit rights as part of the cleanup process.
- All committers will get commit rights to documentation and web site for their project. This will be achieved by assigning the corresponding groups to the CVS projects.
- Projects (Platform, JDT, PDE) each have a group for features, project main web site and any obsolete content with few or no active committers. All sub-project leads would be in that group.
- We should conform to the Eclipse Foundation's normalized ACL structure: <TLP>.<ProjectName>[.<SubProject>]
Proposed new ACLs
The following ACLs for the Eclipse top-level project are proposed (19 ACLs):
eclipse.e4
eclipse.platform
eclipse.platform.debug
eclipse.platform.releng
eclipse.platform.resources
eclipse.platform.runtime
eclipse.platform.swt
eclipse.platform.team
eclipse.platform.text
eclipse.platform.ua
eclipse.platform.ui
eclipse.jdt
eclipse.jdt.core
eclipse.jdt.debug
eclipse.jdt.ui
eclipse.pde
eclipse.pde.build
eclipse.pde.incubator
eclipse.pde.ui
For a complete breakdown of which ACL will own each project in CVS, see Eclipse/PMC/Unix_Groups/New_ACLS_By_Project.
For a complete breakdown of what committer ids will belong to each ACL, see Eclipse/PMC/Unix_Groups/New ACLS By Committer.
Projects to Delete
The following projects in CVS were never included in any release and are completely obsolete. Can we just delete them?
- org.eclipse.core.applicationrunner