| <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
| <html> |
| <head> |
| <title>Project Provisioning</title> |
| <link rel="stylesheet" href="../default_style.css"> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| </head> |
| |
| <body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000"> |
| <table border=0 cellspacing=3 cellpadding=2 width="100%" > |
| <tr> |
| <td ALIGN=LEFT colspan="3"><font class=indextop>eclipse project |
| <br> |
| provisioning |
| </font> </td> |
| <td align=left rowspan="2" width="30%" > </td> |
| </tr> |
| <tr> |
| <td align=left width="21%"><a href="#Overview" class=jump> overview |
| of project lifecycle</a></td> |
| <td align=left width="23%"><a href="#Starting" class=jump>starting |
| a project</a></td> |
| <td align=left width="26%"><a href="#validation" class=jump>validation |
| and implementation phase</a></td> |
| </tr> |
| </table> |
| <table width="100%" cellspacing=3 cellpadding=2> |
| <tr> |
| <td align="left" valign="top" colspan="2" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"><a name="Overview"></a> |
| Overview of eclipseproject lifecycle</font></b></td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <p>Eclipse has a well defined development process based on a specific project |
| lifecycle made up of <em>phases</em> and <em>reviews</em>. Each phase |
| is a period of time where work gets done. Reviews are events.<br> |
| <br> |
| Throughout the Project Provisioning documents, we refer to a "reviewer" |
| for the deliverables, that is either the Eclipse Management Organization |
| (EMO) or the Top-Level Project Management Committee (PMC). Project provisioning |
| is a cooperative and iterative process, where you'll find that your 'reviewers' |
| will help you to work your way through the details of the things you need |
| to provide (or find someone who can help you). This section is meant to |
| clarify the steps in the process and we invite you to send your feedback |
| on both the process and the description to <a href="mailto:emo@eclipse.org">emo@eclipse.org</a>. |
| <br> |
| <br> |
| The following diagram shows a high-level view of the Eclipse development |
| process. For complete details on our process, you need to read the <a href="../org/documents/Eclipse Development Process 2003_11_09 FINAL.pdf">Eclipse |
| Development Process document</a>. <br> |
| </p> |
| </td> </tr> |
| <tr> |
| <td width="51%"> |
| <p> </p> |
| <p align="center"><img src="devproc.jpg" width="254" height="331"><br> |
| </p> |
| </td> <br> |
| <td width="49%"> |
| <p>Related Documents</p> |
| <ul> |
| <li><a href="../org/documents/Eclipse Development Process 2003_11_09 FINAL.pdf">Eclipse |
| Development Process</a></li> |
| </ul> |
| <p>Proposal Phase</p> |
| <ul> |
| <li><a href="projectproposal.html">Project Proposal Provisioning</a></li> |
| </ul> |
| <p>Validation Phase</p> |
| <ul> |
| <li><a href="projectvalidation.html">Project Validation Phase Provisioning</a></li> |
| </ul> |
| <p>Implementation Phase</p> |
| <ul> |
| <li><a href="changes.html">Changes to Project Provisioning</a></li> |
| </ul> |
| </td> |
| <br> |
| </tr> |
| </table> |
| <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" > |
| |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"><a name="Starting"></a> |
| Starting an eclipse project </font></b></td> |
| </TR> |
| <tr colspan="2"> |
| <td> |
| <p>The first step in establishing a new project at Eclipse is to contact |
| the <a href="mailto:emo@eclipse.org">Eclipse Management Organization</a> |
| (<b>EMO</b>), to work towards issuing a Project Declaration. Basically, |
| a declaration is a short email which is distributed to the Eclipse membership-at-large |
| stating that someone wants to start a project at Eclipse. Before a declaration |
| is sent, the EMO will want to talk about the technology areas you are |
| planning on working on, which Project Management Committee (PMC) the new |
| project would best fit in, who you think will be working on the project, |
| etc. In other words, we need to believe that the proposed project is a |
| reasonably good fit with Eclipse.</p> |
| <p>In many cases we start new projects off under the Technology Top-Level |
| Project. In some cases we decide together that it makes sense to propose |
| the creation of a new top-level project with its own PMC. Note that establishing |
| a new top-level project is a somewhat more heavy-weight operation. For |
| example, top-level projects have charters which are approved by the Board |
| of Directors.</p> |
| <p>Once the declaration has been sent, the EMO works with the proponents |
| of the project on their proposal. The length and level of detail of proposals |
| can vary, but the intent is to provide a document which will allow the |
| broad Eclipse community to get an idea of the scope and focus of the proposed |
| project. Once the document is ready, it will be put on our website on |
| the <a href="../proposals/main.html">Proposals</a> page, and a newsgroup |
| will be created for feedback. </p> |
| <p>You'll find a description of what needs to be done to launch a project |
| proposal on the <a href="projectproposal.html">Project Proposal Phase |
| Provisioning</a> page..</p> |
| <p>The proposal phase ends with a creation review, which is an evaluation of the proposal and the community feedback. The two key criteria in successfully passing the creation review are: </p> |
| <ol> |
| <li>does the project have a community of contributors and committers who are willing to work towards making this a success? <br> |
| </li> |
| <li>does the project have a technology scope and focus which will have a reasonable likelihood of success?</li> |
| </ol> |
| |
| </td> |
| </tr> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"><a name="validation"></a> |
| Eclipse project validation and implementation phases</font></b></td> |
| </TR> |
| <tr colspan="2"> |
| <td> |
| <p>After the creation review, the project is set up for development. The |
| CVS repositories, Bugzilla database, the developer mailing lists, etc. |
| are all set up at the beginning of the <i>validation phase</i><b>.</b> |
| It is during the validation phase the the real work of building some working |
| software starts. During this phase, the initial code contributions are |
| gathered, designs and prototypes are created and a project plan is formulated. |
| </p> |
| <p>For a description of the work that goes into setting up a project, take |
| a look at the <a href="projectvalidation.html">Project Validation Phase |
| provisioning</a> page.</p> |
| <p>For the rest of the life of the project, there are numerous administrative |
| items that the project leaders need to be aware of. The <a href="changes.html">Changes |
| to Project Provisioning</a> document has information on how and when the |
| project can set up new committers, add new components to CVS, maintain |
| their web pages, etc.</p> |
| </td> |
| </tr> |
| <tr colspan="2"> |
| <td> </td> |
| </tr> |
| </table> |
| |
| <p align="right"></p> |
| <p></p> |
| </body> |
| </html> |
