[#GALAXY-68] Review license files text and source headers.

Galaxy

Created: 28/Jan/08 07:07 PM Updated: 22/May/08 11:14 AM

Component/s:

Build

Affects Version/s:

None

Fix Version/s:

1.0

Time Tracking:

Not Specified

Labels:
User impact:	High

Description

« Hide

Points of interest:

LICENSE.txt name for a file is not ideal, we may bundle both CPAL and GPL pieces together (the file is referenced from the source header, so we should distinguish between the 2. Maybe LICENSE-CPAL and LICENSE-GPL?
Review CPAL license text for reference to product names and attribution section (closer to the end of the text)
Advise on the GPLv2 text, as it may also contain company and product names and people.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Also, could you (or Dan) specify which modules exactly fall under CPAL so I can configure source header checks for those?

[ Permlink | « Hide ]

#1: Sounds good
#3: I'm not sure what exactly you're looking for, but here is the GPLv2 license http://www.mulesource.org/display/GALAXY/GPLv2+License

Any module under integration/ is CPAL. All others are GPL for now.

[ Permlink | « Hide ]

Dan, the license ends somewhere before this line:

How to Apply These Terms to Your New Programs

Next go the instructions where one has to substitute the values, maybe it helps understand my question.

[ Permlink | « Hide ]

Ross Mason added a comment - 17/Feb/08 05:20 PM

To answer which modules are CPAL licensed it's anything under 'integration' and 'server'

[ Permlink | « Hide ]

Ross Mason added a comment - 18/Feb/08 05:02 PM

Guys, I've put the file header templates here: http://www.mulesource.org/display/GALAXY/File+Headers
Let me know if you see anything amiss.

We'll need to have LICENSE-GPL.txt and LICENSE-CPAL.txt in the distribution