|  | {Copyright:Copyright © 2011 The Eclipse Foundation. All Rights Reserved.} | 
|  | =The Eclipse Development Process= | 
|  | Made available under the terms of the EPL | 
|  |  | 
|  | ==The Eclipse Development Process== | 
|  |  | 
|  | ==Who's Who: EMO== | 
|  | * The Eclipse Management Organization (EMO) | 
|  | ** The Foundation Staff and the Architecture and Planning Councils | 
|  | * EMO(ED) | 
|  | ** The Executive Director and their delegates | 
|  |  | 
|  | ==Rules of Engagement: Openness== | 
|  | * Eclipse is open to all | 
|  | * Eclipse provides the same opportunity to all | 
|  | * Everyone participates with the same rules | 
|  | * There are no rules to exclude any potential contributors which include, of course, direct competitors in the marketplace. | 
|  |  | 
|  | ==Rules of Engagement: Transparency== | 
|  | * Project artifacts are open, public, and easily accessible | 
|  | * Discussions, minutes, deliberations, project plans, plans for new features, ... | 
|  |  | 
|  | ==Rules of Engagement: Meritocracy== | 
|  | * Eclipse is a meritocracy | 
|  | *The more you contribute the more responsibility you earn | 
|  | * Leadership roles in Eclipse are also merit-based and earned by peer acclaim. | 
|  |  | 
|  | ==Ecosystem== | 
|  | The Eclipse Foundation has the responsibility to ''...cultivate...an ecosystem of complementary products, capabilities, and services...'' | 
|  | * Projects are managed for the benefit of both the open source community and the ecosystem members | 
|  | ** Communicate project plans and plans for new features (major and minor) in a timely, open and transparent manner | 
|  | ** Create platform quality frameworks capable of supporting the building of commercial grade products | 
|  | ** Ship extensible, exemplary tools which help enable a broad community of users | 
|  |  | 
|  | ==Three Communities== | 
|  | [[Image:images/community.png]] | 
|  |  | 
|  | ==Three Communities: Contributors and Committers== | 
|  | * Open, transparent, inclusive, and diverse community of Committers and (non-Committer) Contributors | 
|  | * Attracting new Contributors and Committers | 
|  | ** Active recruiting | 
|  | ** Encourage and nurture promising new Contributors | 
|  | * Diversity goals | 
|  | ** Ensure diversity of thought | 
|  | ** Avoid relying on any one company or organization | 
|  | * Projects are required to explain their diversity efforts and accomplishments during Reviews. | 
|  |  | 
|  | ==Three Communities: Users== | 
|  | * Proof-positive that the Project's exemplary tools are useful and needed | 
|  | * Key factor in creating a viable ecosystem | 
|  | ** Source of contribution, committers | 
|  | ** Encouraging open source and commercial organizations to participate | 
|  | *Takes time and effort to bring to fruition | 
|  | **Once established is typically self-sustaining. | 
|  |  | 
|  | ==Three Communities: Adopters== | 
|  | * Project code adopted by other projects and products | 
|  | * Takes time, energy, and creativity | 
|  | ** Essential to the Project's long-term open source success. | 
|  |  | 
|  | ==Projects (1/2)== | 
|  | * Main operational unit at Eclipse | 
|  | ** All open source software development at Eclipse occurs within the context of a Project | 
|  | * Projects have leaders, developers, code, builds, downloads, websites, and more | 
|  | * More than just the sum of their many parts | 
|  | ** The means by which work is organized when presented to the communities | 
|  |  | 
|  | ==Projects (2/2)== | 
|  | * Projects are the unit entity for: | 
|  | ** Committers | 
|  | ** Code and Releases | 
|  | ** IP Records | 
|  | ** Community Awareness | 
|  |  | 
|  | ==Hierarchy== | 
|  | [[Image:images/projectLayers.png]] | 
|  |  | 
|  | * Top-Level Projects, sit at the top of the hierarchy | 
|  | * Each Top-Level Project contains one or more (Sub)Projects | 
|  | * Each Project may itself contain zero or more (Sub)Projects | 
|  |  | 
|  | ==Committers== | 
|  | [[Image:images/subprojects-resources.png]] | 
|  | * Each project has exactly one set of committers | 
|  | ** All Project Committers have equal rights and responsibilities | 
|  | * Elect new Committers to their Project | 
|  | *In practical terms... | 
|  | ** Single UNIX group that provides write-access to Project resources | 
|  |  | 
|  | ==Resources== | 
|  | * Each Project owns and maintains a collection of resources | 
|  | ** Project website | 
|  | ** Space on the downloads server | 
|  | ** Access to build resources | 
|  | ** Other services provided by the Eclipse Foundation infrastructure | 
|  | * Single Bugzilla component for its bugs. | 
|  | * Single IPZilla component for contribution records | 
|  |  | 
|  | ==Releases== | 
|  | * Any Project in the Mature Phase may make a Release | 
|  | ** A Project in the Incubation Phase with two Mentors may make a pre-1.0 Release. | 
|  | * A Release may include the code from any subset of the Project's descendants. | 
|  |  | 
|  | ==Intellectual Property (IP) Logs== | 
|  |  | 
|  | ==Nested Projects== | 
|  | [[Image:images/nestedprojectsandcqs.png]] |