[mdt.dev] IP Issues

[Kenneth Hussey <khussey@xxxxxxxxxx>]

Team,

Please help me ensure that we have no
outstanding IP issues heading into next week's Europa simultaneous release
review. For your reference, here are the steps that we as a project team
need to take to adhere to the Eclipse
IP Policy:

1.        The
project leadership verifies that:

• ... that the about files and use licenses are in place as per the Guidelines to Legal Documentation.
• ... all contributions (code, documentation, images, etc) has been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
• ... that all significant contributions have been reviewed by the Foundation's legal staff. Include references to the IPZilla numbers of all clearances.
• ... that all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff. Include references to the IPZilla numbers of all clearances.
• ... that all Contribution Questionnaires have been completed
• ... the "provider" field of each plug-in is set to "Eclipse.org"
• ... the "copyright" field of each plug-in is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
• ... that any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
• ... that any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.

2.  
     The PMC provides
a Project
Log that enumerates: 
a.        every
piece of third party software including information on the license 
b.        every
major contribution 
c.        the
name of every contributor including non-committer contributions via bug
fixes with bug #'s 
d.        the
About files which contain any non-standard terms (e.g., a reference to
a license other than the EPL, etc) 
3.        The
EMO will validate for (a) and (b) that Contribution Questionnaires have
been properly submitted and EMO approvals have been completed. 
4.        A
frozen copy of the reviewed-and-approved-by-Eclipse-legal Project Log is
part of the Release Review documentation. It can be included in the docuware
or as a separate document. 
(Reference [5])


To this end, component leads please
help me by do the following for your component (in particular):

+ send me references to the IPZilla
numbers of all clearances for significant contributions or third party
libraries

+ ensure that your IP log (see previous
email) is up to date to that I can roll the contents into a combined project
log for MDT that can be reviewed by the Foundation

I'll also be going through all of the
about.html and license.html files for the MDT components this week to ensure
that they are present/correct, so please be prepared to take corrective
action should I discover any problems.

Thanks, 

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912