| <html xmlns:v="urn:schemas-microsoft-com:vml" |
| xmlns:o="urn:schemas-microsoft-com:office:office" |
| xmlns:w="urn:schemas-microsoft-com:office:word" |
| xmlns:st1="urn:schemas-microsoft-com:office:smarttags" |
| xmlns="http://www.w3.org/TR/REC-html40"> |
| |
| <head> |
| <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> |
| <meta name=ProgId content=Word.Document> |
| <meta name=Generator content="Microsoft Word 9"> |
| <meta name=Originator content="Microsoft Word 9"> |
| <!-- <link rel=File-List href="./technology-charter_files/filelist.xml"> --> |
| <title>Eclipse Technology Project Charter</title> |
| <!--[if gte mso 9]><xml> |
| <o:DocumentProperties> |
| <o:Author>Dave Thomson</o:Author> |
| <o:LastAuthor>DThomson</o:LastAuthor> |
| <o:Revision>7</o:Revision> |
| <o:TotalTime>108</o:TotalTime> |
| <o:Created>2003-11-20T12:30:00Z</o:Created> |
| <o:LastSaved>2003-11-27T00:09:00Z</o:LastSaved> |
| <o:Pages>3</o:Pages> |
| <o:Words>2423</o:Words> |
| <o:Characters>13812</o:Characters> |
| <o:Lines>115</o:Lines> |
| <o:Paragraphs>27</o:Paragraphs> |
| <o:CharactersWithSpaces>16962</o:CharactersWithSpaces> |
| <o:Version>9.4402</o:Version> |
| </o:DocumentProperties> |
| </xml><![endif]--><!--[if gte mso 9]><xml> |
| <w:WordDocument> |
| <w:Zoom>125</w:Zoom> |
| <w:Compatibility> |
| <w:ApplyBreakingRules/> |
| </w:Compatibility> |
| <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
| <w:SpellingState>Clean</w:SpellingState> |
| <w:GrammarState>Clean</w:GrammarState> |
| </w:WordDocument> |
| </xml><![endif]--> |
| <style> |
| <!-- |
| span.SPELLE |
| {mso-spl-e:yes;} |
| span.GRAME |
| {mso-gram-e:yes;} |
| /* Font Definitions */ |
| @font-face |
| {font-family:Verdana; |
| panose-1:2 11 6 4 3 5 4 4 2 4; |
| mso-font-charset:0; |
| mso-generic-font-family:swiss; |
| mso-font-pitch:variable; |
| mso-font-signature:536871559 0 0 0 415 0;} |
| /* Style Definitions */ |
| p.MsoNormal, li.MsoNormal, div.MsoNormal |
| {mso-style-parent:""; |
| margin:0in; |
| margin-bottom:.0001pt; |
| mso-pagination:widow-orphan; |
| font-size:12.0pt; |
| font-family:"Times New Roman"; |
| mso-fareast-font-family:"Times New Roman";} |
| h1 |
| {margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-pagination:widow-orphan; |
| mso-outline-level:1; |
| font-size:21.0pt; |
| font-family:Arial; |
| mso-font-kerning:18.0pt; |
| font-weight:bold;} |
| h2 |
| {margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-line-height-alt:10.5pt; |
| mso-pagination:widow-orphan; |
| mso-outline-level:2; |
| font-size:18.0pt; |
| font-family:Arial; |
| font-weight:bold;} |
| h3 |
| {margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-pagination:widow-orphan; |
| mso-outline-level:3; |
| font-size:14.0pt; |
| font-family:Arial; |
| font-weight:bold;} |
| a:link, span.MsoHyperlink |
| {color:blue; |
| text-decoration:underline; |
| text-underline:single;} |
| a:visited, span.MsoHyperlinkFollowed |
| {color:blue; |
| text-decoration:underline; |
| text-underline:single;} |
| p |
| {margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-pagination:widow-orphan; |
| font-size:10.0pt; |
| font-family:Arial; |
| mso-fareast-font-family:"Times New Roman";} |
| code |
| {mso-ascii-font-family:"Courier New"; |
| mso-fareast-font-family:"Courier New"; |
| mso-hansi-font-family:"Courier New"; |
| mso-bidi-font-family:"Courier New";} |
| pre |
| {margin:0in; |
| margin-bottom:.0001pt; |
| mso-pagination:widow-orphan; |
| tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt; |
| font-size:10.0pt; |
| font-family:"Courier New"; |
| mso-fareast-font-family:"Courier New";} |
| p.indextop, li.indextop, div.indextop |
| {mso-style-name:indextop; |
| margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-pagination:widow-orphan; |
| font-size:24.0pt; |
| font-family:Verdana; |
| mso-fareast-font-family:"Times New Roman"; |
| mso-bidi-font-family:Arial; |
| font-weight:bold;} |
| p.indexsub, li.indexsub, div.indexsub |
| {mso-style-name:indexsub; |
| margin-right:0in; |
| mso-margin-top-alt:auto; |
| mso-margin-bottom-alt:auto; |
| margin-left:0in; |
| mso-pagination:widow-orphan; |
| font-size:7.5pt; |
| font-family:Arial; |
| mso-fareast-font-family:"Times New Roman"; |
| color:#8080FF;} |
| @page Section1 |
| {size:8.5in 11.0in; |
| margin:1.0in 1.25in 1.0in 1.25in; |
| mso-header-margin:.5in; |
| mso-footer-margin:.5in; |
| mso-paper-source:0;} |
| div.Section1 |
| {page:Section1;} |
| /* List Definitions */ |
| @list l0 |
| {mso-list-id:97258917; |
| mso-list-type:hybrid; |
| mso-list-template-ids:938493464 -1722270466 1328035828 162058584 -1583577958 1708689942 358257648 -789267326 1364346306 1905806722;} |
| @list l0:level1 |
| {mso-level-number-format:bullet; |
| mso-level-text:\F0B7; |
| mso-level-tab-stop:.5in; |
| mso-level-number-position:left; |
| text-indent:-.25in; |
| mso-ansi-font-size:10.0pt; |
| font-family:Symbol;} |
| @list l1 |
| {mso-list-id:378939679; |
| mso-list-type:hybrid; |
| mso-list-template-ids:1794953454 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} |
| @list l1:level1 |
| {mso-level-number-format:bullet; |
| mso-level-text:\F0B7; |
| mso-level-tab-stop:.5in; |
| mso-level-number-position:left; |
| text-indent:-.25in; |
| font-family:Symbol;} |
| @list l2 |
| {mso-list-id:603197281; |
| mso-list-type:hybrid; |
| mso-list-template-ids:1659121326 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} |
| @list l2:level1 |
| {mso-level-number-format:bullet; |
| mso-level-text:\F0B7; |
| mso-level-tab-stop:.5in; |
| mso-level-number-position:left; |
| text-indent:-.25in; |
| font-family:Symbol;} |
| @list l3 |
| {mso-list-id:2083134086; |
| mso-list-type:hybrid; |
| mso-list-template-ids:-2080353412 1356621094 -131857262 -1447128774 -425566188 1893082798 1171154726 2031539886 1440021566 -1653822288;} |
| @list l3:level1 |
| {mso-level-number-format:bullet; |
| mso-level-text:\F0B7; |
| mso-level-tab-stop:.5in; |
| mso-level-number-position:left; |
| text-indent:-.25in; |
| mso-ansi-font-size:10.0pt; |
| font-family:Symbol;} |
| ol |
| {margin-bottom:0in;} |
| ul |
| {margin-bottom:0in;} |
| --> |
| </style> |
| <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> |
| </head> |
| |
| <body lang=EN-US link=blue vlink=blue style='tab-interval:.5in'> |
| |
| <div class=Section1> |
| |
| <table border=0 cellspacing=6 cellpadding=0 width="100%" style='width:100.0%; |
| mso-cellspacing:3.7pt;margin-left:8.5pt;mso-padding-alt:1.5pt 1.5pt 1.5pt 1.5pt'> |
| <tr style='mso-yfti-irow:0'> |
| <td colspan=2 valign=top style='background:#0080C0;padding:1.5pt 1.5pt 1.5pt 1.5pt'> |
| <p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Arial; |
| color:white'>The Eclipse Technology Project – Top Level Project Charter – The |
| Eclipse Foundation</span></b><span style='font-size:10.0pt;font-family:Arial'><o:p></o:p></span></p> |
| </td> |
| </tr> |
| <tr style='mso-yfti-irow:1;mso-yfti-lastrow:yes'> |
| <td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'> |
| <p><b>Overview</b><br> |
| The Eclipse Technology Top Level Project (the “Eclipse Technology Project”) |
| is an open source software research and development project, which encapsulates |
| three related activity streams, each of which is based on or uses the Eclipse |
| Platform and/or Eclipse Tools: </p> |
| <p>1.<span style='font-size:7.0pt'> </span>academic |
| research projects and other exploratory investigations (“Research Stream”);</p> |
| <p>2.<span style='font-size:7.0pt'> </span>development |
| of educational materials, teaching aids and courseware (“Education Stream”);</p> |
| <p>3.<span style='font-size:7.0pt'> </span>incubation |
| of small-scale, innovative platform and tools projects (“Incubators Stream”).<o:p></o:p></p> |
| <p><st1:place><b>Mission</b></st1:place><br> |
| The mission of the Eclipse Technology Project is to provide a home within the |
| Eclipse Foundation for small, informally structured Projects which add new |
| capabilities to the Eclipse software base (Incubators Stream), foster greater |
| community awareness and understanding of Eclipse (Education Stream), or |
| explore research issues in Eclipse-relevant domains such as programming |
| languages, tools, and development environments (Research Stream). The |
| Eclipse Technology Project is intended to: </p> |
| <p>1.<span style='font-size:7.0pt'> </span>provide |
| the open source community with a lighter weight alternative to the larger |
| scale, more structured development activities carried out by other PMCs, and </p> |
| <p>2.<span style='font-size:7.0pt'> </span>create |
| opportunities for researchers, academics and educators to play a significant |
| role within the Eclipse community. </p> |
| <p><b>Scope</b><br> |
| The scope of the Eclipse Technology Project will encompass a wide variety of |
| small Projects, rather than a few large ones. While anticipating |
| enormous diversity in the content of these activities, from a |
| process-oriented viewpoint they will all share important common |
| characteristics, which argues for a common management envelope:</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Focus on pre-competitive development and research</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Use of informal development processes</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Fluid Project tracking due to frequent plan changes</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Flexible milestones which adapt based on partial |
| results</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Small teams</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Resource commitments tentative, due to volunteer |
| labor or lack of sponsor funding</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>Development often cross-cuts the scope of several |
| other Eclipse Foundation Projects</p> |
| <p>The Eclipse Technology Project serves as a single point of focus for such |
| teams, and provides them with a home within the Eclipse community, to |
| encourage communication, and where appropriate, collaboration and |
| coordination. Providing common management for these Projects |
| facilitates maximum sharing and creation of common components, and avoids redundant |
| efforts. In many cases successful Research Projects will evolve into |
| Incubators, and Incubators in turn may migrate to other PMCs, either by |
| merging into an existing Project, or by forming the basis for a new one.</p> |
| <p>The Education Stream plays a vital role in promoting the use of the |
| Eclipse Platform. By making high quality educational materials freely |
| available, we both enable self-education by individual users, and facilitate |
| the incorporation of Eclipse-related materials into university courses and |
| commercial educational offerings.</p> |
| <p><b>Project Management Committee</b><a name=PMC></a><br> |
| The Projects under this Charter are managed by a group known as the Project |
| Management Committee (the “PMC”).</p> |
| <p>PMCs are expected to ensure that:</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo4; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>All Projects operate effectively by providing |
| leadership to guide the Project’s overall direction and by removing |
| obstacles, solving problems, and resolving conflicts.</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo4; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>All Project plans, technical documents and reports |
| are publicly available</p> |
| <p style='margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo4; |
| tab-stops:list .5in'><![if !supportLists]><span style='font-family:Symbol'>·<span |
| style='font:7.0pt "Times New Roman"'> |
| </span></span><![endif]>All Projects operate using open source rules of |
| engagement: meritocracy, transparency, and open participation.<span |
| style="mso-spacerun: yes"> </span>These principles work together.<span |
| style="mso-spacerun: yes"> </span>Anyone can participate in a |
| Project.<span style="mso-spacerun: yes"> </span>This open interaction, |
| from answering questions to reporting bugs to making code contributions to |
| creating designs, enables everyone to recognize and utilize the |
| contributions.</p> |
| <p>The PMC has the following responsibilities:</p> |
| <ul type=disc> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Providing the leadership and |
| vision to guide the Project's overall direction in a manner consistent |
| with the Eclipse Foundation Architectural Roadmap.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Providing assistance and |
| support to the developers and researchers working on the Project by |
| removing obstacles, solving problems, and resolving conflicts. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Ensuring that Project plans |
| are produced.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Working with the Eclipse |
| Management Organization (the “EMO”) to establish the development |
| processes and infrastructure needed for the development team to be |
| effective. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Recommending new Projects to |
| the EMO.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Recommending the initial set |
| of Project committers for each new Project overseen by the PMC, and |
| establishing the procedures consistent with this Charter for voting in |
| new committers. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Helping to ensure that the |
| Projects overseen by the PMC have enough contributors, and working to |
| fill vacancies in roles. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Producing “how to get |
| involved” guidelines to help new potential contributors get started.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Coordinating relationships |
| with other Eclipse Foundation Projects. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Facilitating code or other |
| donations by individuals or companies. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Making recommendations to the |
| Eclipse Foundation Board regarding contributions proposed under licenses |
| other than the EPL.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Working with the EMO and |
| Committers to ensure in-bound contributions are made in accordance with |
| the Eclipse Foundation IP Policy.<o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l0 level1 lfo7;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Acting as a focal point for |
| the community in representing the Projects it oversees.<o:p></o:p></span></li> |
| </ul> |
| <p>The PMC Lead is appointed by the Board. The initial PMC is selected by the |
| PMC Lead. Thereafter, to become a member of the PMC, an individual must be |
| nominated by another member of the PMC, and unanimously approved by all PMC |
| members.</p> |
| <p>In the unlikely event that a member of the PMC becomes disruptive to the |
| process or ceases to contribute for an extended period, the member may be |
| removed by unanimous vote of remaining PMC members.<span style="mso-spacerun: |
| yes"> </span>PMC members may resign at any time by delivering notice of |
| their resignation to the PMC Lead.</p> |
| <p>The PMC is responsible for producing and maintaining the Project Charter. |
| Development must conform to any rules or processes outlined in the Charter, |
| so a change to the development process may necessitate a change to the |
| Charter.<span style="mso-spacerun: yes"> </span>Changes to the Charter |
| are approved by the Board.</p> |
| <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.</p> |
| <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> |
| <p><b>Roles</b><br> |
| 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> |
| <p><b>Users</b><br> |
| Users are the people who use the output from the Project. Output will |
| typically consist of software and research. Software in this context means |
| intellectual property in electronic form, including source and binary code, |
| documentation, courseware, reports and papers.<span style="mso-spacerun: |
| yes"> </span></p> |
| <p><b>Developers</b><br> |
| Users who contribute software or research become developers.<span |
| style="mso-spacerun: yes"> </span>Developers are encouraged to |
| participate in the user newsgroup(s), and should monitor the developer |
| mailing list associated with their area of contribution. When appropriate, |
| developers may also contribute to development design discussions related to |
| their area of contribution. Developers are expected to be proactive in |
| reporting problems in the bug tracking system.</p> |
| <p><b>Committers</b><br> |
| Developers who give frequent and valuable contributions to a Project, or |
| component of a Project (in the case of large Projects), can have their status |
| promoted to that of a "Committer" for that Project or component |
| respectively. A Committer has write access to the source code repository for |
| the associated Project (or component), and gains voting rights allowing them |
| to affect the future of the Project (or component).</p> |
| <p>In order for a Developer to become a Committer on a particular Project |
| overseen by the PMC, another Committer for the same Project (or component as |
| appropriate) can nominate that Developer or the Developer can ask to be |
| nominated. Once a Developer is nominated, the Committers for the Project (or |
| component) will vote. If there are at least 3 positive votes and no negative |
| votes, the Developer is recommended to the PMC for commit privileges. If the |
| PMC also approves, the Developer is converted into a Committer and given |
| write access to the source code repository for that Project (or component). |
| Becoming a Committer is a privilege that is earned by contributing and |
| showing discipline and good judgement. It is a responsibility that should be |
| neither given nor taken lightly.</p> |
| <p>At times, Committers may go inactive for a variety of reasons. The |
| decision making process of the Project relies on active committers who |
| respond to discussions and votes in a constructive and timely manner. The PMC |
| is responsible for ensuring the smooth operation of the Project. A Committer |
| that is disruptive, does not participate actively, or has been inactive for |
| an extended period may have his or her commit status removed by the PMC.</p> |
| <p>Active participation in the user newsgroup 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 newsgroup.</p> |
| <p>Committers are required to monitor the developer mailing list associated |
| with all Projects and components for which they have commit privileges. This |
| is a condition of being granted commit rights to the Project or component. 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 |
| removed.</p> |
| <p>Committers are required to track, participate in, and vote on, relevant |
| discussions in their associated Projects and components. There are three |
| voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).</p> |
| <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> |
| <p><b>Projects</b><br> |
| 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 decision of the Board.</p> |
| <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.<span style="mso-spacerun: |
| yes"> </span>Project leads are accountable to the PMC for the success |
| of their Project.</p> |
| <p><b>Project Organization</b><br> |
| Given the fluid nature of Eclipse Technology 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 or from the PMC, but the PMC must |
| approve any change, and approval must be confirmed by the EMO.</p> |
| <p>If a Project wishes to divide into components, commit privileges are |
| normally granted at 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 a component lead to 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 in discussions |
| and votes pertaining to the Project as a whole. Component committers do not |
| participate in votes at the level of the Project as a whole, unless they are |
| also the component lead.</p> |
| <p>In cases where new Projects are being created, either by splitting or by |
| 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 the previous structure.</p> |
| <p><b>Infrastructure</b><br> |
| The PMC works with the EMO to ensure the required infrastructure for the |
| Project.<span style="mso-spacerun: yes"> </span>The Project |
| infrastructure will include, at minimum:</p> |
| <ul type=disc> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Bug Database - Bugzilla |
| database for tracking bugs and feature requests. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Source Repository -- One or |
| more CVS repositories containing all the software for the Projects. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Website - A website will |
| contain information about the Project, including documentation, reports |
| and papers, courseware, downloads of releases, and this Charter. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>General Mailing List - |
| Mailing list for development discussions pertaining to the Project as a |
| whole or that cross Projects. This mailing list is open to the public. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Project Mailing Lists - Development |
| mailing list for technical discussions related to the Project. This |
| mailing list is open to the public. <o:p></o:p></span></li> |
| <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt: |
| auto;mso-list:l3 level1 lfo10;tab-stops:list .5in'><span |
| style='font-size:10.0pt;font-family:Arial'>Component Mailing Lists -- |
| Development mailing list for technical discussions related to the |
| component. This mailing list is open to the public. <o:p></o:p></span></li> |
| </ul> |
| <p><b>The Development Process</b><br> |
| In this section the phrase “release cycle” will refer to a significant block |
| of Project activity, which corresponds to an actual release cycle in the case |
| of Incubators or Education Projects, or to a major stage of a phased Research |
| Project.</p> |
| <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 to the PMC for review.<span |
| style="mso-spacerun: yes"> </span>The PMC may provide feedback and |
| advice on the plan but approval rests with the Project Committers.</p> |
| <p>Each Project must identify, and make available on its web site, the |
| requirements and prioritizations 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> |
| <p>The Committers of a Project or component decide which changes may be |
| committed to the master code base of a Project or component respectively. |
| Three +1 ('yes' votes) with no -1 ('no' votes or vetoes) are needed to |
| approve a code change. 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 Project or component.</p> |
| <p>Special rules may be established by the PMC for Projects or components |
| with fewer than three Committers. 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 or component, as applicable.</p> |
| <p>The master copy of the code base must reside on the Project web site where |
| it is accessible to all users, developers 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> |
| <p>Each Project is responsible for establishing test plans and the level of |
| testing appropriate for the Project.</p> |
| <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 informed.</p> |
| <p><b>Licensing</b><br> |
| All contributions to Projects under this Charter must adhere to the Eclipse |
| Foundation Intellectual Property Policy.</p> |
| </td> |
| <td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'> |
| <p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span |
| style='font-size:10.0pt'> <o:p></o:p></span></p> |
| </td> |
| </tr> |
| </table> |
| |
| <p class=MsoNormal style='margin-top:14.2pt'><span lang=EN-CA style='mso-ansi-language: |
| EN-CA'> <o:p></o:p></span></p> |
| |
| </div> |
| |
| </body> |
| |
| </html> |
