Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Technology"
| Line 7: | Line 7: | ||
==What does the Technology Project Management Committee (PMC) Do?== | ==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: | 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: | ||
| Line 14: | Line 14: | ||
*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. | ||
| + | |||
| + | ===Approve new committers=== | ||
| + | |||
| + | When a project's committer election has completed, we give the final approval. | ||
| + | |||
| + | ===Find New 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 | ||
| + | |||
| + | ===Help Projects Develop a Community=== | ||
Revision as of 12:23, 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.
- In particular, we check that the code has proper copyright and license notices.
- 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
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