You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Marvin Humphrey (JIRA)" <ji...@apache.org> on 2013/03/02 23:23:13 UTC

[jira] [Commented] (LEGAL-155) Please help us educate projects about LICENSE and NOTICE

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

Marvin Humphrey commented on LEGAL-155:
---------------------------------------

The dev/ link has been added.

The how-to recipe may need to be updated over time as we discover whether people find it easy to follow and achieve predictable success.  As far as I'm concerned, though, this issue can be closed.
                
> 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