Development Resources/Contribution Questionnaire

From Eclipsepedia

Jump to: navigation, search

Many contributions to a project must be checked by the Eclipse Intellectual Property (IP) Team prior to their inclusion by an Eclipse Project or distribution from an eclipse.org property. Contribution questionnaires (CQ) are the main interface between the Eclipse community and the Eclipse IP Team.

Contributions that require the completion of a CQ are identified by the Eclipse IP Due Diligence Process. Committers should be familiar with this document.

The term "contribution questionnaire" has become synonymous with the notion of a record that tracks the ongoing inclusion of IP in a project. That is, the "questionnaire" part is only the initial aspect, and individual CQs persist indefinitely.

If you are not sure whether or not you need a CQ, ask your project leadership (Project Lead, or PMC members), project mentors, or the EMO for guidance.

Eclipse committers should be familiar with the following documents:

Contents

Initial Contribution

All new projects are required to make an initial contribution before any code can be committed into an eclipse.org version control system (VCS). The Eclipse IP Team will review your initial contribution and tell you (via comments on the CQ) when you can commit the contribution into your project's VCS.

Note that the Eclipse IP Team cannot validate the history initial contribution; the initial contribution must be provided in the form of a snapshot of the project code and must be committed as it is reviewed (i.e. old history must, unfortunately, be left behind).

Initial contribution CQs are created using the Eclipse Developer Portal. Please see Submit initial contribution questionnaire for an overview of the process.

Significant Contributions

Significant contributions, as defined by the Eclipse IP Due Diligence Process require a CQ.

Contribution CQs are created using the Eclipse Developer Portal.

Third Party Libraries

Projects require a CQ for every third-party library that project code makes direct use of. If your code makes indirect use of a third party library through another Eclipse project's code, you do not require a CQ for that library. This tends to boil down to this: if the manifest for one of your bundles makes a direct reference to a third-party library (either the library bundle or a package from the library), then you need a CQ for that library.

Note that CQs for third-party libraries are version-specific. That is, a separate CQ is required for different versions of the same library.

Nested projects that are distributed as part of a parent project's aggregated distribution can leave their CQs on the parent project. If an nested chooses independent distribution (either separately, or in addition to the aggregation), the CQs corresponding to that project will need to be realigned. Note that the IP Log for an aggregated distribution can be combined (this is supported by tools).

There are some special cases in the form of "except prerequisite" and "works with" CQs. For more information, please see the Eclipse Policy and Procedures for Third-Party Dependencies.

Piggyback CQs

Many third party libraries have already been approved for use in Eclipse projects. Many of those are immediately available via the Orbit Project. While these libraries have already been cleared for use by all Eclipse projects, their use must be tracked. Usage is tracked so that--in the event that a issue is uncovered following the due diligence process--we can mitigate the impact of that issue.

In this case, a "piggyback" CQ can be created on top of an existing CQ. Piggyback CQs are generally approved very quickly as the due diligence work has already been completed.