Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 38: Line 38:
 
<br>  
 
<br>  
  
| You need a 3rd party software component to complete a feature in Swordfis
+
| You need a 3rd party software component to complete a feature in Swordfish
 
|  
 
|  
 
#Identify downstream dependencies  
 
#Identify downstream dependencies  
Line 81: Line 81:
 
|  
 
|  
 
|}
 
|}
 
<br> <br> <br> <br>
 

Revision as of 10:04, 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 and Workflow for Commiters and Contributors
1    Role Trigger for Action Actions

Committers/Contributor  


You need a 3rd party software component to complete a feature in Swordfish
  1. Identify downstream dependencies
  2. Inform the team about your choice including dependencies via the SOPERA mailing list
  3. Follow the discussion
  4. Vote with other team members to determine if this third-party component is a “must-have” item.
  5. If it is, then start with the CQ process.
2.
Committers/Contributor
Committers do not object on mailing list.
  1. No objections? Continue with step 3
  2. You are not a committer? Approach one to submit on your behalf.
  3. Objections raised? Search for an alternative

3
Committer


4
Committer


5



6



7

Back to the top