You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2012/08/08 04:17:09 UTC
[jira] [Created] (CRUNCH-37) Update LICENSE to reflect Scala
licensing of scrunch script
Josh Wills created CRUNCH-37:
--------------------------------
Summary: Update LICENSE to reflect Scala licensing of scrunch script
Key: CRUNCH-37
URL: https://issues.apache.org/jira/browse/CRUNCH-37
Project: Crunch
Issue Type: Task
Affects Versions: 0.3.0
Reporter: Josh Wills
Assignee: Josh Wills
The scrunch script that can be used to kick off an interpreted Scrunch session is substantially derived from similar code developed by the Scala team at EPFL for starting the Scala interpreter.
Fortunately, the Scala folks license their code under a generous, BSD-style license, so based on my reading of:
https://issues.apache.org/jira/browse/LEGAL-142
http://www.apache.org/legal/src-headers.html
and
http://apache.org/legal/resolved.html#required-third-party-notices
we need to update the LICENSE file to indicate that the scrunch script is licensed under the Scala license and include a copy of it there prior to release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CRUNCH-37) Update LICENSE to reflect Scala
licensing of scrunch script
Posted by "Josh Wills (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills resolved CRUNCH-37.
------------------------------
Resolution: Fixed
Committed.
> Update LICENSE to reflect Scala licensing of scrunch script
> -----------------------------------------------------------
>
> Key: CRUNCH-37
> URL: https://issues.apache.org/jira/browse/CRUNCH-37
> Project: Crunch
> Issue Type: Task
> Affects Versions: 0.3.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-37.patch
>
>
> The scrunch script that can be used to kick off an interpreted Scrunch session is substantially derived from similar code developed by the Scala team at EPFL for starting the Scala interpreter.
> Fortunately, the Scala folks license their code under a generous, BSD-style license, so based on my reading of:
> https://issues.apache.org/jira/browse/LEGAL-142
> http://www.apache.org/legal/src-headers.html
> and
> http://apache.org/legal/resolved.html#required-third-party-notices
> we need to update the LICENSE file to indicate that the scrunch script is licensed under the Scala license and include a copy of it there prior to release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CRUNCH-37) Update LICENSE to reflect Scala
licensing of scrunch script
Posted by "Matthias Friedrich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Friedrich updated CRUNCH-37:
-------------------------------------
Fix Version/s: 0.3.0
> Update LICENSE to reflect Scala licensing of scrunch script
> -----------------------------------------------------------
>
> Key: CRUNCH-37
> URL: https://issues.apache.org/jira/browse/CRUNCH-37
> Project: Crunch
> Issue Type: Task
> Affects Versions: 0.3.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Fix For: 0.3.0
>
> Attachments: CRUNCH-37.patch
>
>
> The scrunch script that can be used to kick off an interpreted Scrunch session is substantially derived from similar code developed by the Scala team at EPFL for starting the Scala interpreter.
> Fortunately, the Scala folks license their code under a generous, BSD-style license, so based on my reading of:
> https://issues.apache.org/jira/browse/LEGAL-142
> http://www.apache.org/legal/src-headers.html
> and
> http://apache.org/legal/resolved.html#required-third-party-notices
> we need to update the LICENSE file to indicate that the scrunch script is licensed under the Scala license and include a copy of it there prior to release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CRUNCH-37) Update LICENSE to reflect Scala
licensing of scrunch script
Posted by "Matthias Friedrich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431279#comment-13431279 ]
Matthias Friedrich commented on CRUNCH-37:
------------------------------------------
+1. Reading the links above I come to the same conclusion. Thanks a lot for taking care of this, another issue solved before release :)
> Update LICENSE to reflect Scala licensing of scrunch script
> -----------------------------------------------------------
>
> Key: CRUNCH-37
> URL: https://issues.apache.org/jira/browse/CRUNCH-37
> Project: Crunch
> Issue Type: Task
> Affects Versions: 0.3.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-37.patch
>
>
> The scrunch script that can be used to kick off an interpreted Scrunch session is substantially derived from similar code developed by the Scala team at EPFL for starting the Scala interpreter.
> Fortunately, the Scala folks license their code under a generous, BSD-style license, so based on my reading of:
> https://issues.apache.org/jira/browse/LEGAL-142
> http://www.apache.org/legal/src-headers.html
> and
> http://apache.org/legal/resolved.html#required-third-party-notices
> we need to update the LICENSE file to indicate that the scrunch script is licensed under the Scala license and include a copy of it there prior to release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CRUNCH-37) Update LICENSE to reflect Scala
licensing of scrunch script
Posted by "Josh Wills (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CRUNCH-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills updated CRUNCH-37:
-----------------------------
Attachment: CRUNCH-37.patch
Update to the LICENSE file included. It seems somewhat ambiguous as to when you have to update the NOTICE file as well-- the Kafka guys updated NOTICE too when they included SBT, but the LEGAL JIRA indicates that it isn't required.
> Update LICENSE to reflect Scala licensing of scrunch script
> -----------------------------------------------------------
>
> Key: CRUNCH-37
> URL: https://issues.apache.org/jira/browse/CRUNCH-37
> Project: Crunch
> Issue Type: Task
> Affects Versions: 0.3.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-37.patch
>
>
> The scrunch script that can be used to kick off an interpreted Scrunch session is substantially derived from similar code developed by the Scala team at EPFL for starting the Scala interpreter.
> Fortunately, the Scala folks license their code under a generous, BSD-style license, so based on my reading of:
> https://issues.apache.org/jira/browse/LEGAL-142
> http://www.apache.org/legal/src-headers.html
> and
> http://apache.org/legal/resolved.html#required-third-party-notices
> we need to update the LICENSE file to indicate that the scrunch script is licensed under the Scala license and include a copy of it there prior to release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira