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.
Development Resources
Revision as of 14:13, 2 September 2008 by Unnamed Poltroon (Talk) (→Users: Contributing To A Project)
Contents
Users: Contributing To A Project
- Reporting Bugs. All Eclipse projects use Bugzilla to track bugs and features. Please read the Bug Reporting FAQ and then sign up for a bugzilla account to join in the fun.
- Getting Answers. Mailing lists are for development team conversations; news groups and IRC are for the larger user and adopter community and thus are the correct place to ask for help.
- Downloads. Get binaries from the main downloads page. Click through to the project pages for integration, milestone, and nightly builds.
- Source Code. Get the source code from either CVS or SVN (each project makes their own choice).
- Large Contributions. Small contributions to Eclipse projects should be made through Bugzilla, but larger contributions require a separate process.
Committers: Being A Committer
- Portal. The portal is designed to be your single point of contact with the Foundation and to guide you through the various Foundation processes.
- Coding Guidelines. Coding standards, naming conventions, etc.
Your Project On The Eclipse.Org Website
- /projects - List of Projects. Your project is listed on the /projects page automatically. MORE-EXPLANATION-TO-BE-ADDED
- Standard Project Summary. Your project has a standard format project summary page (e.g., [1]). MORE-EXPLANATION-TO-BE-ADDED
Leads: Managing A Project
- IP Log. The IP log is a big part of the official release process, so we encourage you to keep your IP log current rather than rushing at the end. The automatic IP log extracts most information from bugzilla and IPzilla, but it requires you to use the 'iplog+' flag.
- Project Plan. The project plan is how projects communicate their future intent to the rest of the Eclipse community.
- Development Process. Official description of the meta-process for Eclipse projects. [2]
Everyone: IP Cleanliness
- The Official Story. The guide to legal documents describes what legal documents to include with code and deliverable software.
- Committer Guidelines. [3] issues to be aware of, and the processes one should follow, when working as a committer on Eclipse.org projects.
- The Poster. The famous IP process poster [4].
- The Policy. The official written word version of the due diligence process for contributing code [5].
- The Legal Department. Licenses, IP policies, agreements, etc.
- Logos & Trademarks. Documents about the Eclipse logos and trademarks. The Eclipse Foundation owns the trademarks on all the Eclipse Project names. The Foundation holds these trademarks on behalf of, and for the benefit of, the projects.
FAQs and Guidelines
- Guidelines for the Archived Phase
- Guidelines for Creation Reviews
- Guideliens for Graduation Reviews
- User Interface Guidelines
- Eclipse Quality
HOWTOs and Help
Information and Miscellany
This page is moderated by Anne Jacko and Bjorn Freeman-Benson (Eclipse Foundation)