I'm forwarding this to the groovy developer-mailing list:
-------- Weitergeleitete Nachricht --------
Betreff: Re: [Apache Creadur/RAT-206] Request to add support for
Creative Commons Attribution-Share Alike / what LICENSE snippet to scan
for?
Datum: Thu, 11 Jun 2015 23:15:48 -0700
Von: Henri Yandell <[email protected]>
An: [email protected]
Kopie (CC): ASF Legal Discuss <[email protected]>,
[email protected]
resolved.html says "Unmodified media", which was intended to mean images
(audio, video etc).
https://issues.apache.org/jira/browse/LEGAL-4
I wouldn't expect any of those to have a file header (and would question
whether resolved.html says Groovy docs can be CC-BY SA).
On the more general question - I doubt there is a default file header. I
don't see anything suggested here: https://wiki.creativecommons.org/FAQ
Presumably RAT has to be aware of the variants in general use and
support them all as it discovers them.
Hen
On Thu, Jun 11, 2015 at 12:25 PM, P. Ottlinger <[email protected]
<mailto:[email protected]>> wrote:
Hi *,
we've received a request to add a new license to Apache Creadur/RAT
(release audit tool). We are not sure which text needs to be included in
files to be properly CC-licensed?
The page
https://www.apache.org/legal/resolved.html#cc-sa
says that CC-SA is a valid license for Apache projects.
What is a valid file header we need to scan for to properly mark it as
CC-licensed during RAT runs?
Is it
'
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS
CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS
PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE
WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS
PROHIBITED.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND
AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS
YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF
SUCH TERMS AND CONDITIONS.
'
?
Thanks for any feedback before we start implementing this feature.
Cheers,
Phil
PS: Links for details:
https://issues.apache.org/jira/browse/RAT-206
