| <?xml version='1.0'?> |
| <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> |
| <article lang="en"> |
| <articleinfo id="articleinfo"> |
| <title id="articleinfo-title">Title Project Proposal</title> |
| <date /> |
| <author> |
| <firstname>FirstName</firstname> |
| <surname>LastName</surname> |
| <affiliation> |
| <address> |
| <email>email@address.com</email> |
| </address> |
| </affiliation> |
| </author> |
| <abstract id="abstract"> |
| <para>The [NewProjectName] project is a proposed open source |
| project under the |
| <ulink url="http://www.eclipse.org/projects/project_summary.php?projectid=[ContainerProjectId]"> |
| [ContainerProjectName] Container Project</ulink></para> |
| <para>This proposal is in the Project Proposal Phase (as defined |
| in the Eclipse Development Process) and is written to declare its |
| intent and scope. We solicit additional participation and input |
| from the Eclipse community. Please send all feedback to the Vex |
| Forum.</para> |
| </abstract> |
| <revhistory> |
| <revision> |
| <revnumber>1.0</revnumber> |
| <date>Date</date> |
| <revdescription> |
| <para>Description of Change</para> |
| </revdescription> |
| </revision> |
| </revhistory> |
| </articleinfo> |
| <section id="some-id"> |
| <title>Title Project Proposal</title> |
| <para>The [NewProjectName] project is a proposed open source |
| project under the |
| <ulink url="http://www.eclipse.org/projects/project_summary.php?projectid=[ContainerProjectId]"> |
| [ContainerProjectName] Container Project</ulink></para> |
| <para>This proposal is in the Project Proposal Phase (as defined in |
| the Eclipse Development Process) and is written to declare its |
| intent and scope. We solicit additional participation and input |
| from the Eclipse community. Please send all feedback to the Vex |
| Forum.</para> |
| <section> |
| <title>Background</title> |
| <para>Optionally provide the background that has lead you to |
| creating this project.</para> |
| </section> |
| <section> |
| <title>Scope</title> |
| <para>All projects must have a well-defined scope. Describe, |
| concisely, what is in-scope and (optionally) what is |
| out-of-scope. An Eclipse project cannot have an open-ended |
| scope.</para> |
| </section> |
| <section> |
| <title>Description</title> |
| <para>Describe the project here. Be concise, but provide enough |
| information that somebody who doesn't already know very much |
| about your project idea or domain has at least a fighting chance |
| of understanding its purpose.</para> |
| </section> |
| <section> |
| <title>Initial Contribution</title> |
| <para>Describe any existing code that will be contributed to the |
| project.</para> |
| </section> |
| <section> |
| <title>Legal Issues</title> |
| <para>Please describe any potential legal issues in this section. |
| Does somebody else own the trademark to the project name? Is |
| there some issue that prevents you from licensing the project |
| under the Eclipse Public License? Are parts of the code available |
| under some other license? Are there any LGPL/GPL bits that you |
| absolutely require?</para> |
| </section> |
| <section> |
| <title>Committers</title> |
| <para>List any inital committers that should be provisioned along |
| with the new project. Include affiliiation, but do not include |
| email addresses at this point.</para> |
| <para>The following individuals are proposed as initial |
| committers to the project:</para> |
| <variablelist> |
| <varlistentry> |
| <term>Committer 1, Affiliation</term> |
| <listitem> |
| <para>Committer 1, is a committer on the *** project where |
| blah blah.</para> |
| </listitem> |
| </varlistentry> |
| <varlistentry> |
| <term>Committer 2, Affiliation</term> |
| <listitem> |
| <para>Committer 2, is a committer on the *** project where |
| blah blah.</para> |
| </listitem> |
| </varlistentry> |
| </variablelist> |
| <para>We welcome additional committers and contributions.</para> |
| </section> |
| <section> |
| <title>Mentors</title> |
| <para>New Eclipse projects require a minimum of two mentors from |
| the Architecture Council. You need to identify two mentors before |
| the project is created. The proposal can be posted before this |
| section is filled in (it's a little easier to find a mentor |
| when the proposal itself is public).</para> |
| <para>The following Architecture Council members will mentor this |
| project:</para> |
| <itemizedlist> |
| <listitem> |
| <para>Mentor 1</para> |
| </listitem> |
| <listitem> |
| <para>Mentor 2</para> |
| </listitem> |
| </itemizedlist> |
| </section> |
| <section> |
| <title>Interested Parties</title> |
| <para>Provide a list of individuals, organisations, companies, |
| and other Eclipse projects that are interested in this project. |
| This list will provide some insight into who your project's |
| community will ultimately include. Where possible, include |
| affiliations. Do not include email addresses.</para> |
| <para>The following individuals, organisations, companies and |
| projects have expressed interest in this project:</para> |
| <itemizedlist> |
| <listitem> |
| <para>PI-Mod Project</para> |
| </listitem> |
| </itemizedlist> |
| </section> |
| <section> |
| <title>Project Scheduling</title> |
| <para>Describe, in rough terms, what the basic scheduling of the |
| project will be. You might, for example, include an indication of |
| when an initial contribution should be expected, when your first |
| build will be ready, etc. Exact dates are not required.</para> |
| </section> |
| </section> |
| </article> |