www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-155) Please help us educate projects about LICENSE and NOTICE
Date Tue, 29 Jan 2013 06:39:13 GMT

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

Roy T. Fielding commented on LEGAL-155:
---------------------------------------

By pointers, I mean a relative path reference to the license file within some subdirectory
of the package being redistributed.  It used to be quite common for such license files to
be alongside the respective jar in a "lib" or "srclib" directory, or inside the third party
directory containing the source.  The top-level LICENSE can simply point to those files (with
a simple description like "under the MIT license") rather than include all of the text verbatim,
particularly when the same license is repeated for many optional libraries.

In any case, the intention is to allow use of whatever form seems most appropriate for the
given distribution form, while still satisfying the legal requirements for each licensed work.
Some projects will want to include all the text in one file.  Others may not.

Yes, binaries are important to discuss as well, but not because we need any policy for them.
The relevant discussion is simply that any redistribution must obey the licensing requirements
of the contents. The best way to do that will likely depend on the binary packaging form.
                
> Please help us educate projects about LICENSE and NOTICE
> --------------------------------------------------------
>
>                 Key: LEGAL-155
>                 URL: https://issues.apache.org/jira/browse/LEGAL-155
>             Project: Legal Discuss
>          Issue Type: Task
>            Reporter: Benson Margulies
>
> Dear Legal,
> The incubator continues to struggle to educate projects in the proper construction and
maintenance of LICENSE and NOTICE files. INCUBATOR-125 is an attempt to write some documentation.
This document suffers from its authors' inability to even find a single point of reference
on the ASF website for theory of these files. 
> Since podlings are unusual only in their need to set up initial versions, it seems to
me that most of this documentation should be produced and maintained at the foundation level,
and the incubator should be pointing to it, instead of maintain detailed alternatives with
risk of divergence.
> If there is existing documentation, please comment and point me to it. If there is not,
can we collaborate to write it?
> In this area, I have a particular curiosity and concern about convenience binaries.
> A typical Apache project has very limited needs for complexity in these files for its
*releases*. Only sources with external provenance (e.g., results of an SGA) or bundled dependencies
trigger it. Far more dependencies get bundled in convenience binaries. But convenience binaries
are, merely, conveniences, not legally, releases from the foundation. I've never seen any
discussion of this; does the foundation's liability umbrella even extend over them? I doubt
it, for all the usual reasons given in emphasizing that the real release is the source release.
So I wonder about what policies or guidelines should exist for their legal boilerplate.

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message