| <html> |
| <head> |
| <link rel="stylesheet" href="../default_style.css"> |
| <title>Top-Level Project Proposal Provisioning</title> |
| <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=5 CELLPADDING=2 WIDTH="100%" height="129" > |
| <tr> |
| <td ALIGN=LEFT width="60%"><font class=indextop>top-level project proposal |
| provisioning</font><br> |
| <font class=indexsub>infrastructure for projects </font></td> |
| <td WIDTH="40%"> </td> |
| </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr> |
| <td> |
| <p><br> |
| This document describes the infrastructure for Top-Level Project proposals |
| (projects that propose a new PMC) at eclipse.org. The <a href="projectproposal.html">Project |
| Proposal Provisioning</a> document describes the infrastructure for new |
| projects under an existing Top-Level Project. These documents follow the |
| Eclipse Project Lifecyle as described in the <a href="../org/documents/Eclipse%20Development%20Process%202003_11_09%20FINAL.pdf">Eclipse |
| Development Process</a> and are intended to complement the information |
| provided there. In general all inquiries related to project provisioning |
| can be sent to the <a href="mailto:emo@eclipse.org">EMO</a> .<br> |
| </p> |
| </td> </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr bgcolor="#999999"> |
| <td colspan="2" align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"> |
| Eclipse top-level project proposal review infrastructure</font></b></td> |
| </TR> |
| <tr> |
| <td> <img src="proposal.jpg"></td> |
| <td> When a declaration is made to the EMO, the initiating individual works |
| with a PMC to create a proposal which begins the proposal phase. See the |
| <a href="main.html">Project Provisioning</a> document and review archives |
| of previous successful proposals on the <a href="../proposals/main.html">Proposals</a> |
| page for more details about this process. During the proposal phase the |
| project is provisioned with two items:<br> |
| <br> |
| 1 - a website in the proposals directory on eclipse.org, and <br> |
| 2 - a <a href="#newsgroups">newsgroup</a> to open discussions. <br> |
| <br> |
| Please consult the <a href="#checklist">checklist</a> below for items required |
| to create the proposal website and the newsgroup. Each of the deliverables |
| can be emailed to the <a href="mailto:emo@eclipse.org">EMO</a>. <br> |
| <br> |
| At the end of the Proposal Phase is the <a href="#creationreview">Creation |
| Review</a>. During the proposal phase you may consider an <a href="#pr">Announcment |
| Press Release</a>, or you may decide to do the release after the Creation |
| Review and as part of the launch of the <a href="toplevelvalidation.html">Top-Level |
| Project Validation</a> phase. <br> |
| </td> </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"> |
| <a name="newsgroups"></a>Proposal newsgroups </font></b></td> |
| </TR> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr> |
| <td colspan "4"> In this phase, the newsgroup is created last for several |
| reasons. Many newsreaders actively inform their users of the existance of |
| a new newsgroup so when we first created all the infrastructure in a single |
| big bang, the project leaders didn't have enough time to populate the main |
| web page of the proposal before it was "pre-announced" by the |
| newsreader software. We now wait for the main web page to be complete before |
| the newsgroups are created. We then post an initial message, inviting people |
| to visit the newly created project page to learn more about the project. |
| <br> |
| </td> |
| </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"> |
| <a name="pr"></a>Announcement press release </font></b></td> |
| </TR> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=top border="0"> |
| <tr> |
| <td colspan="4" width="100%"> |
| <p>The press release is optional. The release could be issued by the Foundation, |
| or it could be a joint release with the project's stakeholders, and includes |
| Q&A's, messages and preparation of the stakeholder spokespeople. The |
| discipline of creating a press release ensures that all stakeholders have |
| agreed on messages, positioning and have identified spokepersons.<br> |
| <br> |
| If you do decide to issue a press release, the Eclipse Foundation Marketing |
| Director can help you coordinate the announcement. (Email the <a href="mailto:emo@eclipse.org">EMO</a> |
| for further information.)<br> |
| </p> |
| </td> </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"> |
| <a name="creationreview"></a>Creation review </font></b></td> |
| </TR> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=top border="0"> |
| <tr> |
| <td colspan="4" width="100%"> |
| <p>The creation review is scheduled roughly one to two months after the |
| proposal is made public to ensure sufficient time to receive and respond |
| to feedback received from the community. The creation review meeting will |
| include members of the proposed Top-Level Project PMC, representatives |
| from the existing eclipse PMCs and the Eclipse Foundation. The review |
| format is teleconference, and is open to the eclipse membership at large. |
| Notifications of creation review meetings are sent to the eclipse membership |
| mailing list by the EMO. <br> |
| <br> |
| The two key criteria in successfully passing the creation review are: |
| <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> |
| <p> Although the creation review is a relatively informal meeting, the proposed |
| top-level PMC lead will be expected to make a brief presentation to the |
| review committee. The presentation should include a brief summary of the |
| project proposal, in addition to comments about the community response |
| to the proposal, current project participants, initial implementation |
| focus and future directions. The presentation slides will be posted to |
| the proposal site before the review. You can view previous sucessful creation |
| review slide presentations in the <a href="../proposals/main.html">Proposal |
| Archives</a>. <br> |
| <br> |
| Upon a successful review the EMO will recommend creation of the project |
| for the Eclipse Foundation Board of Director's final approval. |
| </td> </tr> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=center> |
| <tr bgcolor="#999999"> |
| <td align="left" valign="top" bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF"> |
| <a name="checklist"></a>Top-Level project proposal provisioning checklist |
| </font></b></td> |
| </TR> |
| </table> |
| <table width="100%" cellspacing=0 cellpadding=3 align=top border="1"> |
| <tr> |
| <td width="21%"> |
| <p><b>Item</b></p> |
| </td> |
| <td width="23%"><b> Description</b></td> |
| <td width="43%"><b>Project team deliverable</b></td> |
| <td width="13%"><b>Review by</b></td> |
| </tr> |
| <tr> |
| <td width="21%" >Proposal published on static web pages </td> |
| <td width="23%">pages published in eclipse.org/proposals directory, linked |
| from proposals main page</td> |
| <td width="43%">-HTML documents (where possible) <br> |
| - in this stage no access is granted to the static webpages, therefore an |
| approved draft for posting should be delivered 48 hours before launch date. |
| The project team then has a one-day cycle to review the proposal as it will |
| be published. </td> |
| <td width="13%">EMO</td> |
| </tr> |
| <tr> |
| <td width="21%" >Project Short Name</td> |
| <td width="23%">The name for the proposal subdirectory on which the newsgroup, |
| mailing list, and CVS addresses will be based </td> |
| <td width="43%">- a 3-6 character short name or acronym for the project title |
| </td> |
| <td width="13%">EMO </td> |
| </tr> |
| <tr> |
| <td width="21%" >Project Description</td> |
| <td width="23%">a brief description of the project (1 paragraph) for the proposals |
| page </td> |
| <td width="43%">- a one paragraph description of the proposed project</td> |
| <td width="13%">EMO </td> |
| </tr> |
| <tr> |
| <td width="21%" >Newsgroup</td> |
| <td width="23%">the initial newsgroup for soliciting feedback on the proposal</td> |
| <td width="43%">- confirmation of newsgroup name in format news://news.eclipse.org/<br> |
| eclipse.[top-level project].[shortname}<br> |
| - the newsgroup is the last item to be released on launch day<br> |
| - the preparation cycle is 3-6 hours, therefore a confirmed name 24 hours |
| before the launch is preferred. </td> |
| <td width="13%">EMO </td> |
| </tr> |
| <tr> |
| <td width="21%" >Newsgroup description </td> |
| <td width="23%">3 line newsgroup description that appears on the <a href="../newsgroups/index.html" target="_top">Newsgroups |
| main page </a></td> |
| <td width="43%">- newsgroup description/invitation to participate</td> |
| <td width="13%">EMO</td> |
| </tr> |
| |
| </table> |
| |
| |
| </body> |
| </html> |
