Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Swordfish:ProjectRules:IPComplianceProcess Internal"

Line 16: Line 16:
  
 
==About Swordfish's Internal IP Process==
 
==About Swordfish's Internal IP Process==
Swordfish has a number of complimentary steps introduced into its project life cycle which  should help to ensure IP compliance for third party components used in its project.
+
<p>Swordfish has a number of complimentary steps introduced into its project life cycle which  should help to ensure IP compliance for third party components used in its project.</p>
 
+
<p>The Swordfish Runtime project requires more non EPL 3rd Party software components than the average Eclipse IDE Project. Hence, we have included some additional steps to ensure full compliance to the Eclipse legal requirements. As long as Swordfish is on the release train of a common Eclipse release, the Swordfish team will ensure that all 3rd’party bundles which are committed are covered by approved Eclipse Contribution Questionnaire (CQs). All the events are generally triggered by events in the Eclipse Legal Process </p>
  
 
==Tasks for Commiters and Contributors==
 
==Tasks for Commiters and Contributors==
Line 23: Line 23:
  
  
==Release Manager==
+
==Tasks for the Release Manager==
 +
 
 +
 
 +
----
 +
 
 +
[[Swordfish|Swordfish Wiki Home]]

Revision as of 09:34, 27 July 2009

Swordfish Internal IP Compliance Process: An Extension to the Eclipse IP Legal Process

Intro

About the Eclipse IP Legal Process

The Eclipse Legal Process guidelines provide all Swordfish team members with all the information required on the subject of IP compliance. Here are a few links on the Eclipse IP Legal Process

There is also an audio presentation worth listening to you at: [Campbell, Legal Counsel & Manager, IP]

In addition to this, in our team we have a short process work flow that all team members can use as a frame of reference.

NOTE: This is a draft process guideline. It will be subject to review and improvement throughout the project life-cycle.

About Swordfish's Internal IP Process

Swordfish has a number of complimentary steps introduced into its project life cycle which should help to ensure IP compliance for third party components used in its project.

The Swordfish Runtime project requires more non EPL 3rd Party software components than the average Eclipse IDE Project. Hence, we have included some additional steps to ensure full compliance to the Eclipse legal requirements. As long as Swordfish is on the release train of a common Eclipse release, the Swordfish team will ensure that all 3rd’party bundles which are committed are covered by approved Eclipse Contribution Questionnaire (CQs). All the events are generally triggered by events in the Eclipse Legal Process

Tasks for Commiters and Contributors

Tasks for the Release Manager


Swordfish Wiki Home

Back to the top