Difference between revisions of "Technology"

From Eclipsepedia

Jump to: navigation, search
Line 12: Line 12:
  
 
*An initial license check
 
*An initial license check
*Check that code provided by an Eclipse committer conforms to the [http://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf Eclipse IP Policy] (the short version of the [http://www.eclipse.org/legal/guidetolegaldoc2.php guidelines for developers] is helpful in this regard.
+
*Check that code provided by an Eclipse committer conforms to the [http://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf Eclipse IP Policy] (the short version of the [http://www.eclipse.org/legal/guidetolegaldoc2.php guidelines for developers] is helpful in this regard).
 
**In particular, we check that the code has proper [http://www.eclipse.org/legal/copyrightandlicensenotice.php copyright and license notices].
 
**In particular, we check that the code has proper [http://www.eclipse.org/legal/copyrightandlicensenotice.php copyright and license notices].
 
*Try to reduce bloat, challenge the submitter to use alternative similar technology when already available.
 
*Try to reduce bloat, challenge the submitter to use alternative similar technology when already available.
  
===Approve new committers===
+
===Approve New Committers===
  
 
When a project's committer election has completed, we give the final approval.  
 
When a project's committer election has completed, we give the final approval.  
  
 
===Find New Projects===
 
===Find New Projects===
 +
We identify new project opportunities and invite interesting work to become Eclipse Technology Projects.
  
 
===Help New Projects with their Proposals===
 
===Help New Projects with their Proposals===
All new Eclipse projects start with a proposal. We guide new projects get through the proposal process by (a) helping them assemble the proposal document, and (b) attend the creation review call with them. As part of assembling the proposal document, we will aid a new project in identifying [[Architecture Council]] mentors and
+
All new Eclipse projects start with a proposal. We guide new projects get through the proposal process by (a) helping them assemble the proposal document, and (b) attend the creation review call with them. As part of assembling the proposal document, we will aid a new project in identifying [[Architecture Council]] mentors and "Interested Parties".
  
 
===Help Projects Develop a Community===
 
===Help Projects Develop a Community===
 +
Most of the work here falls more into the category of "teaching a committer to fish". We don't develop the community for a project, we encourage the project to do the sorts of things that need to be done to develop a community. We will blog or deliver presentations about a project when an opportunity presents itself.
 +
 +
===Review Projects on an Ongoing Basis===
 +
We periodically review projects to ensure that they're doing the right sorts of things to progress. We ensure, for example, that projects are making reasonable effort to develop community. We ensure that they're following the Eclipse IP Policy.
 +
 +
===Help Technology Projects to Stop being Technology Projects===
 +
Some Technology projects just go on forever. And this fine for projects of a research nature. However, over time, projects will mature and a more appropriate permanent home may need to be identified (e.g. a different top-level project). Alternatively, some projects run their course and reach a natural end. We help these projects terminate as gracefully as possible.

Revision as of 12:38, 12 November 2008

This is a landing page for the Technology Project.

Contents

Useful Links

What does the Technology Project Management Committee (PMC) Do?

Approve Intellectual Property (IP) Contribution Questionnaires (CQ)

When projects take contributions and make use of third-party libraries, they are required to enter a CQ. A CQ will not be processed by the IP team until it has been approved by the PMC. When we are informed of a new CQ (via email), we do the following:

  • An initial license check
  • Check that code provided by an Eclipse committer conforms to the Eclipse IP Policy (the short version of the guidelines for developers is helpful in this regard).
  • Try to reduce bloat, challenge the submitter to use alternative similar technology when already available.

Approve New Committers

When a project's committer election has completed, we give the final approval.

Find New Projects

We identify new project opportunities and invite interesting work to become Eclipse Technology Projects.

Help New Projects with their Proposals

All new Eclipse projects start with a proposal. We guide new projects get through the proposal process by (a) helping them assemble the proposal document, and (b) attend the creation review call with them. As part of assembling the proposal document, we will aid a new project in identifying Architecture Council mentors and "Interested Parties".

Help Projects Develop a Community

Most of the work here falls more into the category of "teaching a committer to fish". We don't develop the community for a project, we encourage the project to do the sorts of things that need to be done to develop a community. We will blog or deliver presentations about a project when an opportunity presents itself.

Review Projects on an Ongoing Basis

We periodically review projects to ensure that they're doing the right sorts of things to progress. We ensure, for example, that projects are making reasonable effort to develop community. We ensure that they're following the Eclipse IP Policy.

Help Technology Projects to Stop being Technology Projects

Some Technology projects just go on forever. And this fine for projects of a research nature. However, over time, projects will mature and a more appropriate permanent home may need to be identified (e.g. a different top-level project). Alternatively, some projects run their course and reach a natural end. We help these projects terminate as gracefully as possible.