| <!DOCTYPE html> |
| <ht> |
| <he> |
| <meta charset="UTF-8"> |
| <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]--> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| <meta name="generator" content="Asciidoctor 1.5.2"> |
| <title>Eclipse Standard Top-Level <strike>Charter v1.2</title></strike> <font color="green">Charter</title></font> |
| <style> |
| |
| </style> |
| </head> |
| <body class="book"> |
| <div id="header"> |
| <h1>Eclipse Standard Top-Level <strike>Charter v1.2</h1></strike> <font color="green">Charter</h1></font> |
| </div> |
| <div id="content"> |
| <div id="preamble"> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p><em>This document defines standard terms for Eclipse Top Level Project |
| Charters. It is intended that the Charters for Top Level Projects |
| reference this document rather than inheriting by copy-and-paste.</em></p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Overview</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p><em>To be defined in the individual Top Level Project Charter.</em></p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Mission</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p><em>To be defined in the individual Top Level Project Charter.</em></p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Scope</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p><em>To be defined in the individual Top Level Project Charter.</em></p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Project Management Committee</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>The Projects under this Charter are managed by a group known as the |
| Project Management Committee (the "PMC"). The PMC’s duties are described |
| in <strike>"<a href="/projects/dev_process/development_process.php#4_6_Leaders">4.6 |
| Leaders</a>"</strike> <font color="green"><a href="https://www.eclipse.org/projects/dev_process/#4_6_Leaders">4.6 Leaders</a> of the Eclipse Development Process.</p> |
| </div> |
| <div class="paragraph"> |
| <p>It is the PMC’s responsibility to ensure the projects within its |
| umbrella operate as active and viable open source projects, and to take |
| steps to reboot, archive, or restructure projects if they become |
| inactive or otherwise fail to meet the requirements</font> of the Eclipse |
| Development Process.</p> |
| </div> |
| <div class="paragraph"> |
| <p>The work of the PMC is shared by the PMC members. All PMC members are |
| expected to contribute actively. In particular, PMC members are expected |
| to take responsibility for overseeing certain areas of work in the |
| Project, and reporting to the PMC on these areas. Because of the |
| diversity amongst individual projects, PMC members are not expected to |
| maintain anything other than general currency with projects outside |
| their assigned technical areas.</p> |
| </div> |
| <strike><div class="paragraph"> |
| <p>Active participation in the user newsgroups and the appropriate |
| developer mailing lists is a responsibility of all PMC members, and is |
| critical to the success of the Project. PMC members are required to |
| monitor the main Project mailing list, and the developer mailing lists |
| for all Projects and components they are overseeing.</p> |
| </div></strike> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Roles</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>The Projects under this Charter are operated as meritocracies — the |
| more you contribute, and the higher the quality of your contribution, |
| the more you are allowed to do. However with this comes increased |
| responsibility.</p> |
| </div> |
| <div class="sect2"> |
| <h3>Users</h3> |
| <div class="paragraph"> |
| <p>Users are the people who use the output from the Project. Output <strike>will</strike> |
| typically <strike>consist</strike> <font color="green">consists</font> of software in form of extensible frameworks and |
| exemplary tools. Software in this context means intellectual property in |
| electronic form, including source and binary code, documentation, |
| courseware, reports and whitepapers.</p> |
| </div> |
| </div> |
| <div class="sect2"> |
| <strike><h3>Developers</h3></strike> |
| <font color="green"><h3>Contributors</h3></font> |
| <div class="paragraph"> |
| <p>Users who contribute software, documentation, or other materially useful |
| content become <strike>developers. Developers</strike> <font color="green">contributors. Contributors</font> are encouraged to participate in |
| the user <strike>newsgroup(s),</strike> <font color="green">forums,</font> and should monitor the developer mailing list |
| associated with their area of contribution. When appropriate, <strike>developers</strike> <font color="green">contributors</font> |
| may also contribute to development design discussions related to their |
| area of contribution. <strike>Developers</strike> <font color="green">Contributors</font> are expected to be proactive in |
| reporting problems in the bug tracking system.</p> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3>Committers</h3> |
| <div class="paragraph"> |
| <strike><p>Developers</strike> |
| <font color="green"><p>Contributors</font> who give frequent and valuable contributions to a <strike>Project, or |
| component of a</strike> Project <strike>(in the case of large Projects),</strike> |
| can have their |
| status promoted to that of a "Committer" for that Project <strike>or component</strike> |
| respectively. See |
| <strike>"<a href="/projects/dev_process/development_process.php#4_7_Committers_and_Contributors">4.7</strike> |
| <font color="green"><a href="https://www.eclipse.org/projects/dev_process/#4_7_Committers_and_Contributors">4.7</font> |
| Committers and <strike>Contributors</a>"</strike> <font color="green">Contributors</a></font> of the Eclipse Development Process for the |
| process and responsibilities that entails.</p> |
| </div> |
| <div class="paragraph"> |
| <p>At times, Committers may become inactive for a variety of reasons. The |
| decision making process of the Project relies on active committers who |
| respond to discussions and vote in a constructive and timely manner. <strike>The |
| PMC is responsible for ensuring the smooth operation of the Project.</strike> A |
| Committer who is disruptive, does not participate actively, or has been |
| inactive for an extended period may have his or her commit status |
| revoked by the PMC.</p> |
| </div> |
| <div class="paragraph"> |
| <p>Active participation in the user <strike>newsgroup</strike> <font color="green">forums</font> and the appropriate developer |
| mailing lists is a responsibility of all Committers, and is critical to |
| the success of the Project. Committers are required to monitor and |
| contribute to the user <strike>newsgroup.</p></strike> <font color="green">forums.</p></font> |
| </div> |
| <div class="paragraph"> |
| <p>Committers are required to monitor the mailing lists associated with all |
| Projects <strike>and components</strike> for which they have commit privileges. This is a |
| condition of being granted commit rights to the <strike>Project or component.</strike> <font color="green">Project.</font> It |
| is mandatory because committers must participate in votes (which in some |
| cases require a certain minimum number of votes) and must respond to the |
| mailing list in a timely fashion in order to facilitate the smooth |
| operation of the Project. When a Committer is granted commit rights they |
| will be added to the appropriate mailing lists. A Committer must not be |
| unsubscribed from a developer mailing list unless their associated |
| commit privileges are also revoked.</p> |
| </div> |
| <div class="paragraph"> |
| <p>Committers are required to track, participate in, and vote on, relevant |
| discussions in their associated <strike>Projects and components.</strike> <font color="green">Projects.</font> There are three |
| voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).</p> |
| </div> |
| <div class="paragraph"> |
| <p>Committers are responsible for proactively reporting problems in the bug |
| tracking system, and annotating problem reports with status information, |
| explanations, clarifications, or requests for more information from the |
| submitter. Committers are responsible for updating problem reports when |
| they have done work related to the problem.</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Projects</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>The work under this Top Level Project is further organized into |
| Projects. New Projects must be consistent with the mission of the Top |
| Level Project, be recommended by the PMC, and confirmed by the EMO. |
| Projects can be discontinued by recommendation of the PMC, and confirmed |
| by the EMO.</p> |
| </div> |
| <div class="paragraph"> |
| <p>When a new Project is created, the PMC nominates a Project lead to act |
| as the technical leader and nominates the initial set of Committers for |
| the Project, and these nominations are approved by the EMO. Project |
| leads are accountable to the PMC for the success of their Project.</p> |
| </div> |
| <div class="sect2"> |
| <strike><h3>Project Organization</h3></strike> |
| <font color="green"><h3>Components</h3></font> |
| <div class="paragraph"> |
| <strike><p>Given the fluid nature</strike> |
| <font color="green"><p>The Eclipse Development Process has no formal notion</font> of <font color="green">component. As |
| such</font> Eclipse <strike>Projects, organizational changes are |
| possible, in particular: dividing a Project into components; dividing a |
| Project into two or more independent Projects; and merging two or more |
| Projects into a single Project. In each case, the initiative for the |
| change may come either from within the Project</strike> <font color="green">Foundation infrastructure provides no formal means of |
| managing membership</font> or <strike>from the PMC, but the |
| PMC must approve any change, and approval must be confirmed by the EMO.</p> |
| </div> |
| <div class="paragraph"> |
| <p>If a Project wishes to divide into components, commit</strike> privileges <strike>are |
| normally granted</strike> at <strike>the component level, and the committers for a given |
| component vote on issues specific to that component. Components are |
| established and discontinued by the PMC. When the PMC creates a |
| component, it appoints</strike> a component <strike>lead</strike> <font color="green">level. Projects may |
| opt</font> to <strike>act as the technical leader |
| and names the initial set of Committers for the component. The component |
| lead is designated as a committer for the Project and represents the |
| component</strike> <font color="green">informally designate different functional areas</font> in <strike>discussions and votes pertaining to the Project as</strike> a <strike>whole. |
| Component committers do not participate in votes at the level of the</strike> project as <strike>a whole, unless they are also the component lead.</p> |
| </div> |
| <div class="paragraph"> |
| <p>In cases where new Projects are being created, either by splitting or</strike> |
| <font color="green">de facto components, but access to resources associated with those |
| functional areas must be managed</font> by |
| <strike>merging, the usual procedures as set forth in this Charter are followed. |
| In particular, developers will not necessarily have the same rights |
| after an organizational change that they enjoyed in</strike> <font color="green">social convention with oversight |
| from</font> the <strike>previous |
| structure.</p></strike> <font color="green">project leadership.</p></font> |
| </div> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Infrastructure</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>The PMC works with the EMO to ensure the required infrastructure <font color="green">is provided</font> for the |
| Project. The Project infrastructure <strike>will include,</strike> <font color="green">includes,</font> at minimum:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <strike><p>Bug Database - Bugzilla database for tracking bugs and feature |
| requests.</p></strike> |
| <font color="green"><p>An issue tracker;</p></font> |
| </li> |
| <li> |
| <strike><p>Source Repository — One</strike> |
| <font color="green"><p>One</font> or more <font color="green">source</font> repositories <strike>containing</strike> <font color="green">that must collectively include</font> all |
| <font color="green">of</font> the |
| <strike>software</strike> <font color="green">source code</font> for the <strike>Projects.</p></strike> <font color="green">Project’s software;</p></font> |
| </li> |
| <li> |
| <strike><p>Website - A</strike> |
| <font color="green"><p>A</font> website <strike>will</strike> <font color="green">to</font> contain information about the Project, |
| including documentation, reports and papers, courseware, downloads of |
| releases, and this <strike>Charter.</p></strike> <font color="green">Charter;</p></font> |
| </li> |
| <li> |
| <strike><p>General Mailing List -</strike> |
| <font color="green"><p>A download server (or space on a server);</p> |
| </li> |
| <li> |
| <p>A developer</font> mailing list <font color="green">("dev-list")</font> for discussions pertaining to the |
| Project as a whole or that cross <strike>Projects. This mailing list is open to |
| the public.</p></strike> <font color="green">Projects;</p></font> |
| </li> |
| <li> |
| <strike><p>Project</strike> |
| <font color="green"><p>Additional project</font> mailing lists <strike>- Mailing list</strike> <font color="green">(as needed)</font> for technical discussions |
| related to the <strike>Project. This mailing list is open to the public.</p></strike> <font color="green">Project; and</p></font> |
| </li> |
| <li> |
| <strike><p>Component Mailing Lists - Mailing list for technical discussions |
| related to the component. This mailing list is open to the public.</p> |
| </li> |
| <li> |
| <p>Newsgroups - Newsgroups</strike> |
| <font color="green"><p>A forum</font> where users, <strike>developers,</strike> <font color="green">contributors,</font> and Committers can interact regarding |
| general questions and issues about the <strike>project.</strike> <font color="green">Project.</p> |
| </li> |
| </ul> |
| </div> |
| <div class="paragraph"> |
| <p>All services are open for public participation (with archives where appropriate). |
| Project Committers have special access to some resources (e.g. write access to |
| source code repositories and</font> the |
| <strike>newsgroup</strike> <font color="green">download server). |
| The Project team</font> is <strike>open</strike> <font color="green">obligated</font> to <font color="green">use</font> the <strike>public.</p> |
| </li> |
| </ul></strike> <font color="green">issue tracker provided by the EMO for all issues |
| related to the project. |
| The provided download server must be used as the primary means to distribute |
| all milestone and release builds produced by the Project.</p></font> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>The Development Process</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <strike><p>Each Project lead must produce a development plan for the release cycle, |
| and the development plan must be approved by a majority of Committers of |
| the Project. The plan must be submitted</strike> |
| <font color="green"><p>All projects are required to operate according</font> to the <strike>PMC for review. The PMC |
| may provide feedback and advice on the plan but approval rests with</strike> <font color="green">rules established |
| by</font> the |
| <strike>Project Committers.</p></strike> <font color="green">most current version <a href="https://www.eclipse.org/projects/dev_process/">Eclipse Development Process</a>.</p></font> |
| </div> |
| <div class="paragraph"> |
| <p>Each Project must identify, and make available on its web site, the |
| requirements and <strike>prioritizations</strike> <font color="green">priorities</font> it is working against in the current |
| release cycle. In addition, each Project must post a release plan |
| showing the date and content of the next major release, including any |
| major milestones, and must keep this plan up to date.</p> |
| </div> |
| <div class="paragraph"> |
| <p>The Committers of a Project <strike>or component</strike> decide which changes may be |
| committed to the master code base of a Project <strike>or component</strike> |
| respectively. The PMC defines the decision process, but that process |
| must include the ability for Committers to veto the change. The decision |
| process employed may change with the phase of development. Common |
| decision processes include:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>Retroactive - changes are proactively made by Committers but can be |
| vetoed by a single Committer. </p> |
| </li> |
| <li> |
| <p>Proactive - for efficiency, some code changes from some contributors |
| (e.g. feature additions, bug fixes) may be approved in advance, or |
| approved in principle based on an outline of the work, in which case |
| they may be committed first and changed as needed, with conflicts |
| resolved by majority vote of the Committers of the Project <strike>or component,</strike> |
| as applicable.</p> |
| </li> |
| <li> |
| <p>Three Positive - No code is committed without a vote; three +1 ('yes' |
| votes) with no -1 ('no' votes or vetoes) are needed to approve a code |
| change. </p> |
| </li> |
| </ul> |
| </div> |
| <div class="paragraph"> |
| <p>Vetoes must be followed by an explanation for the veto within 24 hours |
| or the veto becomes invalid. All votes are conducted via the developer |
| mailing list associated with the <strike>Project or component.</strike> <font color="green">Project.</font> Special rules may |
| be established by the PMC for Projects <strike>or components</strike> with fewer than |
| three Committers. </p> |
| </div> |
| <div class="paragraph"> |
| <p>The master copy of the code base must reside on the Project web site |
| where it is accessible to all users, <strike>developers</strike> <font color="green">contributors,</font> and committers. |
| Committers must check their changes and new work into the master code |
| base as promptly as possible (subject to any check-in voting rules that |
| may be in effect) in order to foster collaboration among widely |
| distributed groups and so that the latest work is always available to |
| everyone. The PMC is responsible for working with the Eclipse Foundation |
| to establish a release engineering and build process to ensure that |
| builds can be reliably produced on a regular and frequent basis from the |
| master code base and made available for download from the Project web |
| site. Builds in this context are intended to include not only code but |
| also reports, documentation, and courseware.</p> |
| </div> |
| <div class="paragraph"> |
| <p>Each Project is responsible for establishing test plans and the level of |
| testing appropriate for the Project.</p> |
| </div> |
| <div class="paragraph"> |
| <p>All development technical discussions are conducted using the |
| development mailing lists. If discussions are held offline, then a |
| summary must be posted to the mailing list to keep the other committers, |
| and any other interested parties,</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2>Licensing</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>All contributions to Projects under this Charter must adhere to the |
| <a href="/org/documents/Eclipse_IP_Policy.pdf">Eclipse Foundation |
| Intellectual Property Policy</a>.</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <div id="footer"> |
| <div id="footer-text"> |
| Last updated <strike>2016-02-04 15:51:32</strike> <font color="green">2016-02-26 09:12:23</font> -05:00 |
| </div> |
| </div> |
| </body> |
| </html> |
