Swordfish Internal IP Compliance Process: An Extension to the Eclipse IP Legal Process
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
- This link provides you with excellent background information.
- The Eclipse IP Compliance Process in cartoon format!
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 Committers, Contributors and the Project Lead
This table lists all the tasks for commiters, contributors and the project lead.
|1||Role||Trigger for Action||Actions|
|You need a 3rd party software component to complete a feature in Swordfish||
| 2. || Committers/Contributor|| Committers do not object on mailing list.||
| 3|| Committer|| Starting and monitoring the CQ|| 1. Before filing a CQ, check: Is there an existing CQ?
| 4|| Committer|| Team or Project Lead have identified 3rd party as critical ‘must have’ component||
| 5|| Eclipse Project Lead|| Team has identified 3rd party as critical ‘must have’ component|| Set a deadline for CQ approval (consent form EMC to use the third-party component).|
| 6|| Eclipse Project Lead|| Before deadline is reached||
| 7|| Commiter|| Status of CQ is ‘CheckIntoCvs’||
The next topic covers tasks that need to be performed by the release manager.
Tasks for Release Managers
These tasks are for the release manager in the Swordfish team.
|Role||Trigger for Action||Actions|
| || Release Manager|| Each Sprint End ||
Based on Last Build Results:
NOTE: If points 1-3 are negative consult with committer about alternatives.
| CQ denied||
| || Release Candidate 1||