| {Copyright:Copyright © 2011 The Eclipse Foundation. All Rights Reserved.} |
| =The Project Creation Process= |
| Made available under the terms of the EPL |
| |
| ==The Project Creation Process== |
| |
| [[Image:images/simmons.png]] |
| |
| ==Project Creation Process (1/3)== |
| * Optionally contact the EMO via email to state your intention to propose a new project. |
| * Write a draft based on the Proposal document Template |
| ** http://www.eclipse.org/proposals/templates/proposal-template.zip |
| * Send the completed draft of the proposal to the EMO |
| ** emo@eclipse.org |
| * The EMO will review the document and provide feedback |
| |
| ==Project Creation Process (2/3)== |
| * The EMO will post a draft copy and request your feedback on the "live" version |
| ** EMO will open a bug against "Community/Proposals and Reviews" |
| * Proposal is posted on the "Projects Gateway" page |
| ** http://www.eclipse.org/projects |
| * Mentors are solicited from the Architecture Council |
| * Proposal document is updated as needed |
| |
| ==Project Creation Process (3/3)== |
| * Proposal open for a minimum of two- to three-weeks for community review |
| * Proposers request a creation review |
| ** Reviews run (Thursday to Wednesday) period |
| * Proposal is declared successful |
| * Provide provisioning information |
| ** Space on our servers, create committer records, etc. |
| * Submit your initial contribution |
| ** The IP team must give you approval before anything can be committed to any Eclipse VCS or download server |
| |
| ==Initial Contribution== |
| * Project must be provisioned |
| * Namespace in your contribution should align with Eclipse naming conventions |
| ** i.e. org.eclipse.<project-name>.* |
| * Ensure that Eclipse copyright and license notice(s) applied to source content |
| ** about.html, license files etc.; |
| * Attach source code to a Bugzilla record as "Initial Contribution" |
| * Open a "Contribution Questionnaire" (CQ) |
| * Attach the same file to the CQ |
| |
| ==Ongoing Responsibilities== |
| * Community development is a big part of life at Eclipse |
| ** It is strongly recommended that you identify somebody on your team to be responsible for community development activities |
| * Projects must conform to the legal documentation requirements, naming conventions, and version numbering rules. |
| * Projects must maintain their metadata |
| **This information is used to drive our automated processes |
| *Before an Eclipse project can release any software, they must undergo a release review |
| ** Projects in the incubation phase can only do pre-1.0 releases (e.g. 0.7). |
| ** Before creating a >=1.0 release, a project must undergo a graduation review and enter the mature phase |
| *If you have any questions, or are unsure of your responsibilities as a project lead or committer, please contact the project mentors or EMO |
