Jump to: navigation, search

Development Resources/HOWTO/Parallel IP Process

... Parallel IP approvals for Incubating Projects at Eclipse. This process will clearly benefit Incubating Projects in that they will now be able to proceed with development activity while due diligence is completed in parallel.

(1) Is My Project Eligible (i.e., Conforming)?

  1. All conforming Incubation phase Eclipse projects are eligible to participate in the Parallel IP process.
    A conforming project:
    • Is in the Incubation phase.
    • Correctly displays the incubation logo on their project home page.
    • Correctly displays the same incubation logo on their project's primary download page.
    • All downloadable zip files for builds (including release builds) and milestones must include the word "incubation" in the filename. For example, DSF-SDK-incubation-N20070413-0200.zip
      • The jar files in the download zip file are not required to contain the word "incubation" in the filename. (See bug 178944 for the explanation.)
    • All "Bundle-Name"s must include the word "incubation". Note that "Bundle-SymbolicName"s should not include "incubation" because the Bundle-SymbolicName is a technical namespace, not a user namespace. For example, Bundle-Name: Foo Plug-in (Incubation)
    • Similarly, the names for update manager features must include the word "incubation". For example, Eclipse Platform (Incubation)
    • Projects are listed as conforming or non-conforming on the main /projects page by the egg (conforming) and egg-with-red-slash (non-conforming) icons. If you believe your project is conforming (i.e., 1-5 above) but is listed on the main projects page as non-conforming, send email to the EMO and ask us to update the database.
  2. Mature projects may use parallel ip if the contribution represents a minor change to a previously approved packaged.

(2) How It Works

If your project is "incubating (conforming)", then:

  1. Submit a fully formed Contribution Questionnaire (CQ) for your code or the third-party code that you want to use. A fully formed CQ:
    • Explains where this code or third-party library came from. For example, if this code was developed by the author with the express intent of contributing it to the Eclipse project as soon as the project was provisioned, that should be noted. Or, for example, if this code was part of a commercial product and the company is contributing it to the Eclipse Project, that should be noted (along with documentation proving that the contribution is approved). Etc.
    • Includes all nested jar files - a separate IPBug with attached source code must be completed for each nested jar file
    • Identifies all applicable licenses
    • Includes references (ipzilla urls) to all existing IPZilla entries for the same jar files (same name and exact version) -or-
    • Attaches related source code for the jar files if there is no existing IPZilla for those jar files (same name and exact version) yet.
  2. Add a comment to the CQ (or its resulting IPZilla) that you are requesting the Parallel IP process for this contribution. Note that the Parallel IP process does not eliminate the requirement on either yourself or on the Foundation to complete the due diligence review of the contribution - it merely rearranges the deadlines and check points.
    • The normal IP due diligence process requires that the legal review be completed before the code is checked into the source code repository. Normal-ip-flow.gif
    • The parallel IP process allows the check-in to occur before the legal review is complete (but after the preliminary legal approval) - the legal review must be completed before the code is included in a release. Parallel-ip-flow.gif
  3. Eclipse Legal will review the IPZilla. If it is fully formed and the licenses are compatible with the EPL, Eclipse Legal will mark the IPZilla with the checkintocvs keyword.
  4. Once the checkintocvs keyword appears on the IPZilla (IPZilla, of course, will notify you by email when there are changes to your "IP bug"), you may then check the related code into CVS/SVN.
  5. Eclipse Legal will continue their due diligence review in parallel.
  6. Important: if, after a period of time, the code related to this IP bug is no longer needed, please let the Eclipse Legal team know so that the Foundation can focus its limited resources on other due diligence requests.

(3) Explanations and Documents

This page is moderated by the EMO