| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| <html> |
| <head> |
| <title>Eclipse Technology Project Top-Level Charter</title> |
| <link type="text/css" rel="stylesheet" href=" |
| http://www.eclipse.org/default_style.css"> |
| <title>Eclipse Research Project Top-Level</title> |
| </head> |
| <body text="#000000" bgcolor="#ffffff" link="#0000EE" vlink=" |
| #551A8B" alink="#ff0000"> |
| |
| <table cellspacing="5" cellpadding="2" width="100%" border="0"> |
| |
| <tbody> |
| <tr> |
| <td valign="top" align="left" bgcolor="#0080C0" colspan="3"> |
| <b><span style="font-size:10.0pt;font-family:Arial; |
| mso-fareast-font-family:"Times New Roman";color:white;mso-ansi-language:EN-US; |
| mso-fareast-language:KO;mso-bidi-language:AR-SA">The Eclipse Technology Project |
| Top-Level Project Charter The Eclipse Foundation</span></b></td> |
| </tr> |
| |
| <tr> |
| <td colspan="3"> |
| <p><b>Overview<br> |
| </b>The Eclipse Technology Top Level Project (the "Eclipse Technology |
| Project") is an open source software project for the incubation of |
| small-scale, innovative platform and tools projects.</p> |
| <p><b>Mission</b><br> |
| The mission of the Eclipse Technology Project is to provide a temporary home |
| within the Eclipse Foundation for small, newer, early adopter-type Projects |
| which add new capabilities to the Eclipse software base. The Eclipse Technology |
| Project is intended to provide the open source community with a lighter weight |
| alternative to the larger scale, more structured development activities carried |
| out by other PMCs until the new projects are ready to join their destination PMC.</p> |
| <p><b>Scope</b><br> |
| The scope of the Eclipse Technology Project will encompass a wide variety of |
| small early-stage 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> |
| <ul> |
| <li>Use of lighter weight, but still formal development processes </li> |
| <li>Fluid Project tracking due to frequent plan changes </li> |
| <li>Flexible milestones which adapt based on partial results </li> |
| <li>Small teams, relatively inexperienced in open-source software |
| development </li> |
| <li>Definitive plans to move to mature the project and then move it to the |
| appropriate Top-Level Project.</li> |
| </ul> |
| <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. The goal of successful projects |
| is to migrate to other PMCs, either by merging into an existing Project, or by |
| forming the basis for a new one.</p> |
| <p><b>Other Terms<br> |
| </b>This Charter inherits all terms not otherwise defined herein from the "<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse |
| Standard Charter v1.0</a>". This includes, but is not limited to, sections |
| on the Program Management Committee, Roles, Project Organization, The |
| Development Process, and Licensing.</p> |
| <p><b>Project Management Committee <br> |
| </b>Changes from the "<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse |
| Standard Charter v1.0</a>" are:</p> |
| <ul> |
| <li>Providing the leadership and vision to guide the Project's overall |
| direction in a manner consistent with the <strike>Eclipse Foundation |
| Architectural Roadmap</strike> Eclipse Foundation's goals. </li> |
| </ul> |
| <p><b>Projects <br> |
| </b>Changes from the "<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse |
| Standard Charter v1.0</a>" are: </p> |
| <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, <b>have |
| an explicit plan for reaching their destination top-level project, </b>be |
| recommended by the PMC, and confirmed by the EMO. Projects can be discontinued |
| by decision of the Board. |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| |
| </body> |
| </html> |
| |
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
