| <html><head> |
| <link rel="stylesheet" href="../default_style.css"><title>Changes to Project Provisioning</title> |
| |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head> |
| <body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b"> |
| <table border="0" cellpadding="2" cellspacing="5" height="129" width="100%"> |
| <tbody><tr> |
| <td align="left" width="60%"><font class="indextop">changes to project provisioning</font><br> |
| <font class="indexsub">infrastructure for projects </font></td> |
| <td width="40%"> </td> |
| </tr> |
| </tbody></table> |
| <table width="100%" cellspacing="3" cellpadding="2"> |
| <tr> |
| <td align="center" valign="top" colspan="2"> |
| <p style="border-style: dashed"><b><font face="Arial,Helvetica" size="+1">These |
| pages are out-of-date. <br> |
| Revised and corrected versions of these pages are being developed. <br> |
| Please verify with all information on these pages with the <a href="mailto:emo@eclipse.org">EMO</a>.</font></b></p> |
| </td> |
| </tr> |
| </table> |
| <table align="center" cellpadding="3" cellspacing="0" width="100%"> |
| <tbody><tr> |
| <td> |
| <p><br> |
| This document describes the infrastructure for projects and that are in |
| the validation or implementation phase of their project at eclipse.org. It |
| describes the process for ongoing provisioning activities such as changes |
| to committer lists and updates to Bugzilla components.<br> |
| <br> |
| In general all inquiries related to project provisioning can be sent to |
| the <a href="mailto:emo@eclipse.org">Eclipse Management Organization</a> |
| (EMO). <br> |
| </p> |
| </td> </tr> |
| </tbody></table> |
| <table align="center" cellpadding="3" cellspacing="0" width="100%"> |
| <tbody><tr bgcolor="#999999"> |
| |
| <td align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"> |
| Eclipse project implementation phase infrastructure</font></b></td> |
| </tr> |
| </tbody> |
| </table> |
| <table align="top" border="0" cellpadding="3" cellspacing="0" width="100%"> |
| <tr> |
| <td> <img src="implementation.jpg"></td> |
| |
| <td colspan="4" width="100%"> |
| <p>If you need changes to your infrastructure, you'll need to send the requests |
| to the webmaster or the EMO. <br> |
| <br> |
| The <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a> should |
| be contacted for:</p> |
| <ul> |
| <li> password reset</li> |
| <li> creating new components</li> |
| <li> changes to Bugzilla components</li> |
| <li> changes to committer component access</li> |
| <li>adding or archiving (read-only) mailing lists</li> |
| <li>adding or archiving (read-only) newsgroups</li> |
| </ul> |
| <p>The <a href="mailto:emo@eclipse.org">emo@eclipse.org</a> should be contacted |
| for: </p> |
| <ul> |
| <li> content related changes such as changes to web elements on www.eclipse.org |
| </li> |
| <li>adding new committers</li> |
| <li>removing committers</li> |
| </ul> |
| <p>When sending requests, please clearly identify the Top-Level Project |
| and Project you are working on so that requests that require PMC approval |
| or clarification can be properly routed to the correct PMC by the infrastructure |
| team. Please consult the checklist below for items required for implementing |
| provisioning changes. </p> |
| </td> |
| </tr> |
| </table> |
| <table align="center" cellpadding="3" cellspacing="0" width="100%"> |
| <tbody><tr bgcolor="#999999"> |
| |
| <td align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"> |
| Implementation phase provisioning checklist</font></b></td> |
| </tr> |
| </tbody> |
| </table> |
| <table align="top" border="1" cellpadding="3" cellspacing="0" width="100%"> |
| <tr> |
| <td width="19%"> |
| <p><b>Item</b></p> |
| </td> |
| <td width="32%"><b> Description</b></td> |
| <td width="34%"><b>Project team deliverable</b></td> |
| <td width="15%"><b>Review by</b></td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Adding new committers</td> |
| <td width="32%"> |
| <p>Once a new committer is voted in (see<b> </b>the individual Top-Level |
| Project Charters for details about voting for new committers) the process |
| is the same as for the initial set of committers. <br> |
| </p> |
| </td> |
| |
| <td width="34%"> |
| <p>Email <a href="mailto:emo@eclipse.og">emo@eclipse.og</a>, along with the relevant Top-Level PMC approval, |
| the name(s) of the new committers with the following information:<br> |
| - name of the project and hosting top-level project<br> |
| - full name of the committer<br> |
| - email address of the committer<br> |
| - the list of CVS packages to which the committer will have update privileges</p> |
| </td> |
| |
| <td width="15%"> |
| <p>- voted in by relevant project committers<br> |
| - approved by PMC<br> |
| - agreements and information validated by EMO </p> |
| </td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Committer Guidelines, Agreement, Questionnaire and Employer |
| Consent </td> |
| |
| <td width="32%"> |
| <p>The EMO is responsible for ensuring that documentation is in place for |
| new committers. <br> |
| <br> |
| Once the documentation is in place, the EMO will contact the webmaster |
| to provide the appropriate accesses to the new committers. </p> |
| </td> |
| <td width="34%"> |
| <p>- the project team may appoint a single contact to assist the new |
| committers in completing the required documentation</p> |
| <p> </p> |
| </td> |
| <td width="15%"> </td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Removing committers</td> |
| |
| <td width="32%">Removing a committer requires the approval of the PMC.<br> |
| </td> |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:emo@eclipse.org">emo@eclipse.org</a><br> |
| - name of the project and hosting top-level project<br> |
| - full name of the committer<br> |
| - email address of the committer<br> |
| - the list of CVS packages to which commit accesses will be removed</td> |
| <td width="15%">approved by PMC and review by EMO</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Changing access privileges on a specific component</td> |
| |
| <td width="32%">A committer needs commit-access to a component, or no longer |
| needs commit-access to a component.</td> |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a><br> |
| - name of the project and hosting top-level project<br> |
| - full name of the committer<br> |
| - email address of the committer<br> |
| - the list of CVS packages to which commit accesses will change</td> |
| |
| <td width="15%">review by PMC</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Adding a new component to CVS </td> |
| |
| <td width="32%">CVS components, or modules, are created as subdirectories |
| in the project's CVS repository location, in the HEAD branch. Component |
| names follow the<i> org.eclipse.component.name</i> naming convention.<br> |
| <p> </p> |
| </td> |
| <td width="34%">Email to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a><br> |
| - a list of the new components along with a list of committers who will |
| have access to which component<br> |
| - suggested formats:<br> |
| [module x] "same committers as [module y]<br> |
| or <br> |
| <i>module:userid1,iserid2,userid3,userid4...</i><br> |
| <i>module:e@mail,e@mail,e@mail<br> |
| module:Name Surname,Name Surname, Name Surname</i> </td> |
| <td width="15%">review by PMC</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Changing access rights to download.eclipse.org</td> |
| |
| <td width="32%">Any access rights changes to the downloads area.</td> |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:webmaster@eclipse.or">webmaster@eclipse.or</a>g<br> |
| - names of committers to be granted update rights to the download site</td> |
| |
| <td width="15%">review by PMC</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Changes to content on www.eclipse.org</td> |
| |
| <td width="32%">Newsgroup and mailing list main pages, Tools or Technology |
| top-level project pages, and other non-project specific pages</td> |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a><br> |
| - email requested changes to <a href="mailto:emo@eclipse.org">emo@eclipse.rog</a></td> |
| <td width="15%">review by PMC</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Adding a new newsgroup</td> |
| |
| <td width="32%">One newsgroup is created per project. Newsgroup names follow |
| the convention: eclipse.toplevelname.projectshortname </td> |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a><br> |
| - newsgroup name in format news://news.eclipse.org/<br> |
| eclipse.[top-level project].[shortname}<br> |
| - newsgroup description/invitation to participate </td> |
| |
| <td width="15%">review by PMC </td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Adding a new mailing list</td> |
| |
| <td width="32%">Mailing lists are resources used by committers to facilitate |
| group communication. Mail posted to a mailing list is archived and searchable |
| from the website. Normally, a single mailing list is created for a project; |
| however, projects with several components can have several mailing lists. |
| The main project mailing list is normally called projectname-dev, and component |
| lists are called projectname-component. A list of mailing lists can be found |
| here: <a href="https://dev.eclipse.org/mailman/listinfo/">https://dev.eclipse.org/mailman/listinfo/</a></td> |
| |
| <td width="34%">Email the following information, along with the relevant Top-Level |
| PMC approval to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a><br> |
| - long description based on the example shown here <a href="http://dev.eclipse.org/mailman/listinfo/platform-dev" target="_blank">http://dev.eclipse.org/mailman/<br> |
| listinfo/platform-dev</a><br> |
| - short description based on the examples here <a href="http://www.eclipse.org/mail/index.html" target="_blank">http://www.eclipse.org/mail/index.html</a></td> |
| |
| <td width="15%">review by PMC</td> |
| </tr> |
| <tr> |
| |
| <td width="19%">Archiving a newsgroup or mailing list </td> |
| <td width="32%">Newsgroup content, as well as e-mails sent to a mailing list |
| are archived and searchable from the eclipse.org website. The newsgroup |
| or mailing list becomes read-only. </td> |
| <td width="34%">- request to <a href="mailto:webmaster@eclipse.org">webmaster@eclipse.org</a></td> |
| |
| <td width="15%">review by PMC</td> |
| </table> |
| <table align="top" border="0" cellpadding="3" cellspacing="0" width="100%"> |
| <tr> |
| <td > |
| <p><b>Send us updates to your committers list!</b><br> |
| The committer lists are used to determine the developer's voting rights |
| on eclipse.org, so please help us to keep them up to date! Information |
| includes the committer's address and contact information. Send any |
| changes or updates to the committers list, including adding new committers, |
| to the <a href="mailto:emo@eclipse.org">EMO</a>. <br> |
| <br> |
| </p> |
| </td> |
| </tr> |
| </table> |
| <p></p> |
| <p></p> |
| </body></html> |
