crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Friedrich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-110) a few licensing nits
Date Sat, 10 Nov 2012 10:25:12 GMT

    [ https://issues.apache.org/jira/browse/CRUNCH-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494602#comment-13494602
] 

Matthias Friedrich commented on CRUNCH-110:
-------------------------------------------

The current state of affairs is the result of CRUNCH-28 and CRUNCH-37, meaning we tried but
we didn't know better :)

What can we do? Copy the full license from our LICENSE file to the scrunch script? Regarding
the Gutenberg books I have no idea how to proceed. A patch would be very much appreciated!
                
> a few licensing nits
> --------------------
>
>                 Key: CRUNCH-110
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-110
>             Project: Crunch
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Roman Shaposhnik
>
> It would be nice to add a more clearly identifiable licensing header to the scrunch launcher
script and also make it explicit which resource files have a Project Gutenberg license instead
of simply excluding these file in the rat configuration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message