Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Development Resources"

(Committers and The Eclipse.Org Website)
(Committers and The Eclipse.Org Website)
Line 15: Line 15:
 
* '''Standard Project Plan.''' Your project has a standard format project plan page (e.g., [http://www.eclipse.org/projects/project-plan.php?projectid=technology.dash] for Project Dash). The project plan page is driven by your project's meta-data (see below).
 
* '''Standard Project Plan.''' Your project has a standard format project plan page (e.g., [http://www.eclipse.org/projects/project-plan.php?projectid=technology.dash] for Project Dash). The project plan page is driven by your project's meta-data (see below).
 
* '''IP Log.''' Your project has a standard format IP log (e.g., [http://www.eclipse.org/projects/ip_log.php?projectid=technology.dash] for Project Dash). The IP log is driven by your project's meta-data (see below) and also has an entire page of documentation of its own [http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log].
 
* '''IP Log.''' Your project has a standard format IP log (e.g., [http://www.eclipse.org/projects/ip_log.php?projectid=technology.dash] for Project Dash). The IP log is driven by your project's meta-data (see below) and also has an entire page of documentation of its own [http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log].
 +
* '''Project Meta-Data.''' Many pieces of the eclipse.org infrastructure are driven by the project meta-data, thus it is important to keep the meta-data current and correct. Use /www.eclipse.org/projects/dev_process/project-status-infrastructure.php the instructions] and [http://portal.eclipse.org the portal] to update the meta-data.
  
 
====New Committers====
 
====New Committers====

Revision as of 14:38, 2 September 2008

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

Committers and The Eclipse.Org Website

  • /projects - List of Projects. Your project is listed on the /projects page automatically based on your project's meta-data (see below).
  • Standard Project Summary. Your project has a standard format project summary page (e.g., [1] for Project Dash). The summary page is driven by your project's meta-data (see below).
  • Standard Project Plan. Your project has a standard format project plan page (e.g., [2] for Project Dash). The project plan page is driven by your project's meta-data (see below).
  • IP Log. Your project has a standard format IP log (e.g., [3] for Project Dash). The IP log is driven by your project's meta-data (see below) and also has an entire page of documentation of its own [4].
  • Project Meta-Data. Many pieces of the eclipse.org infrastructure are driven by the project meta-data, thus it is important to keep the meta-data current and correct. Use /www.eclipse.org/projects/dev_process/project-status-infrastructure.php the instructions] and the portal to update the meta-data.

New Committers

  • Legal Paperwork. Becoming a new committer involves some legal paperwork. Here's what and why [5]
  • Development Process. For the overall smooth flow of the Eclipse eco-system, committers agree to follow a few process rules Here's what they are [6]. There's also a more humorous summary version [7].
  • Parallel IP Process. Many new committers join with a block of code that they'd like to include right away. The Parallel IP process is designed to speed that inclusion. Here's the what, why, and how of that process [8].

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. [9]

Everyone: IP Cleanliness

  • The Official Story. The guide to legal documents describes what legal documents to include with code and deliverable software.
  • Committer Guidelines. [10] 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 [11].
  • The Policy. The official written word version of the due diligence process for contributing code [12].
  • 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

HOWTOs and Help

Information and Miscellany

This page is moderated by Anne Jacko and Bjorn Freeman-Benson (Eclipse Foundation)

Back to the top