Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Architecture Council/Things Committers Should Know

On a bi-weekly basis, the Architecture Council sends a short note out to Eclipse Committers (via the committers mailing list) describing some aspect of the Eclipse Development Process. The idea is to provide very short (i.e. one paragraph) reminders of important information in a form that committers are able to quickly digest. This page serves as an archive for these notices. Future notices are under development on the staging page.

December 2008

Committers Should Know: Eclipse Intellectual Property Due Diligence

Hello Eclipse Committer. This is a first note in a new series of "Things Committers Should Know". Each month, the Architecture Council sends out a short note describing some important aspect of life as an Eclipse committer. We hope that these notes are valuable and informative. These mailings are also archived on the Architecture Council Wiki [1]. This month, we touch briefly on Intellectual Property (IP) Due Diligence.

As an Eclipse Committer, you certainly know about IP Due diligence. But did you know that the "Eclipse Legal Process" Poster [2], the definitive guide to the Eclipse IP Process, has been updated several times in the past year to pick up new special cases? In fact, the document is currently under review [3] for its next iteration. You are also required to take 3rd party dependencies [4]—whether or not they are to be included in your project's CVS/SVN repository or made accessible for download—through the IP Process.

In the coming months, we'll talk more specifically about these important resources. In the meantime, if you have any questions about the IP Due Diligence process, please ask your project leader, your PMC, or one of your project's Architecture Council mentors.


Back to the top