Re: [cross-project-issues-dev] Reminder to update your feature "licenses

[David M Williams <david_williams@xxxxxxxxxx>]

That sound about right, Scott. 
If you ever need to check in extreme
detail, the authoritative guide is 
http://www.eclipse.org/legal/guidetolegaldoc.php

According to it, even though document
and content is the same, "notice.html" is what should be at the
root of zip files. 
and in the features themselves, it is
called "license.html" (even though it is "not really a license").


So beside having have the two files
in root of each feature (license.html  and
 epl-v10.html [unchanged, frm previous])
the 
feature.properties has two properties, 
licenseURL=license.html [which likely doesn't have to
change, if name of file stays the same], 
and then 
license=<plain text of license.html>

When adding the "plain text" version to properties,
be sure to maintain the tabs and "end of lines" (Linux form)
as they are ... which if you pull from git, should be easy, if you get
from website, such as from 
http://www.eclipse.org/legal/epl/feature.properties.txt
when be sure to use something like 
wget http://www.eclipse.org/legal/epl/feature.properties.txt
Using the browsers "save as" function may change
characters in ways you wouldn't want them changed!. 

HTH




From:      
 Scott Lewis <slewis@xxxxxxxxxxxxx>
To:      
 cross-project-issues-dev@xxxxxxxxxxx,

Date:      
 04/25/2014 12:26 PM
Subject:    
   Re: [cross-project-issues-dev]
Reminder to update your feature "licenses" for Luna
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Hi,

Sorry in advance if this is covered ground somewhere...but I can't seem
to find it.

For those projects that are still using the 'old way'...and therefore need
to update the files by hand...I want to clarify what actually needs to
be updated to meet these requirements...please correct if wrong/missing,
etc:

In the features:

notice.html  (the SUA in it's own content)
feature.properties   (the SUA in the feature.properties file)

That's it, right?  I've got the new content from the legal git repo,
but want to verify that this is the extent of the necessary changes.

Has anyone created and shared among EF projects a script to do this?  
Not that I'll actually use it :), but useful to ask. 

Thanks,

Scott

On 4/24/2014 1:41 AM, David M Williams wrote:
I'm sure everyone is aware of the "new
license" requirement: 
Bug
431255 - Need to update the SUA (Software
User Agreement) 

And now that we in Platform (and MPC) have updated -- which demonstrated
my updated "repo report" appears to be working correctly -- I
thought it'd be a good time to send a reminder. 

http://build.eclipse.org/simrel/luna/reporeports/reports/licenseConsistency.html

It'd be nice to get as many updated as possible for M7, and certainly by
RC1. It really does give a much better "user experience" and
better "first impression" to those updating/installing to get
that simpler, more meaningful license dialog. 

Thanks, 



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev