Eclipse Foundation Committer Training
The rules of engagement defined in the Eclipse Foundation Development Process are the foundational principles that underpin how we believe that open source should be done.
Eclipse projects must be transparent. To operate in a transparent manner, Eclipse project teams need to ensure that the community has the ability to understand what the project team is doing. This means that all development plans, issues tracking and resolution, discussion, and more happens on open channels where people who are not a part of the project team can follow along.
Eclipse projects must be open. Transparency is concerned with letting people know what you’re doing, openness is concerned with letting them participate as an equal player. As an Eclipse project committer, you have to be open to new ideas and work with contributors to ensure that their contributions have an equal chance of becoming part of the project. Project teams should have well-defined rules for participating that apply to everybody regardless of who they work for or factors other than the quality of their contributions.
Eclipse projects must be meritocratic. Project participants earn their way to additional responsibility. A regular contributor of quality code should be invited to become a committer themselves. A committer who shows leadership may one day become a project lead. We have a well-defined process for turning somebody into a committer that requires a statement of merit; very often that statement of merit is just a bunch of pointers to contributions that the individual has made to the project.
In these videos, we discuss certain key elements of life as a committer on an Eclipse Project.
For Eclipse projects, and the open source world in general, committers are the folks who have the real power. Committers decide what code goes into the code base, they decide how a project builds, and they ultimately decide what gets delivered to the adopter community.
Committer elections are the means by which new committers are added to the project.
Like every process that we have at the Eclipse Foundation, the committer election process has been defined, and tools have been created, to support important underlying principles.
The Eclipse Foundation Intellectual Property Policy
The Eclipse Foundation has a well-defined Intellectual Property Policy, corresponding IP Due Diligence Process, and a dedicated team of professional IP specialists who perform the heavy lifting in the due diligence process. Eclipse Committers, the software developers who ultimately decide what will become Project Code and how an Eclipse open source project will leverage Third Party Content, are responsible for bringing IP issues to the attention of the Eclipse IP Team.
The Eclipse Dash License Tool
The Eclipse Dash License Tool is a tool that is intended to help Eclipse Committers assess the license status of the content that their project leverages.
The tool really only knows what you tell it. While it does have some rudimentary functionality for rooting out content, we very much depend on committers -- who form the first line of defense in our intellectual property due diligence process -- to understand the content that their project contains and leverages and to ensure that all content is identified and fully vetted.