www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LEGAL-24) Scripts, source, and Reciprocal Licenses
Date Mon, 21 Jul 2008 17:33:31 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615318#action_12615318

Henri Yandell commented on LEGAL-24:

I think the main reason for this was that there is less likelyhood of a binary being modified,
therefore much less times in which we'd have to be concerned about how much of our code was
under another license. The manifests in category B licenses is a good example; they are under
the copyleft license but *shrug* we didn't care.

So for a javascript MPL file, I think we would be happy for any modifications to that file
to remain under MPL. No big deal imo. As long as things are very well described, and we avoid
building a new product on that MPL library, tis good. So I think we want to discourage forking,
even more than usual, and that every file under a category B should be listed in the README.

Questions from the above for brevity:

* What reasons do we have to say no to Category B source?
* Any value in strongly discouraging forking/modifications?
* Do we need any higher level of documentation in the project to point out the licensing of
the file?

> Scripts, source, and Reciprocal Licenses
> ----------------------------------------
>                 Key: LEGAL-24
>                 URL: https://issues.apache.org/jira/browse/LEGAL-24
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sam Ruby
> The current draft of the Third Party Licensing Policy (0.53) contains the following text
under the section concerning Reciprocal Licenses:
> Note that works written in a scripting language without a binary form cannot be included
in any ASF product under one of these licenses (see Transition and Exceptions).
> We need to decide if this truly is necessary.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message