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-27) LICENSE/NOTICE content vs package content
Date Mon, 21 Jul 2008 20:25:31 GMT

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

Henri Yandell commented on LEGAL-27:
------------------------------------

Agreed with David on: "Released artifacts should include LICENSE and NOTICE files applying
exactly to their content."

On the 'it's better' - I think that while there's more risk in having missing stuff than noise
(I guess...), neither are acceptable. If we're going to consider noise as acceptable, then
we should be sticking: "This product may contain" in front of every line etc.

No idea on it being standard practice to copy and paste LICENSE/NOTICE out of context. I'm
used to projects that were modular from the start (Commons/Taglibs).

> LICENSE/NOTICE content vs package content
> -----------------------------------------
>
>                 Key: LEGAL-27
>                 URL: https://issues.apache.org/jira/browse/LEGAL-27
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Stefano Bagnara
>
> Most apache releases included a LICENSE/NOTICE tuple (I will refer to them as LICENSE/NOTICE
tuple to make it easier, even if they deserve different treatment sometimes) including references
to every 3rd party work in that svn tree. This LICENSE/NOTICE tuple was then added to every
package released from that tree even if some of the packages created didn't really include
all of the work referenced there.
> To my understand this was the standard accepted practice until a broader maven adoption.
Using maven most projects started releasing jar-packages (and not only the bin/src packages)
so the question about the LICENSE/NOTICE oversized content came out.
> If people agree that is good to have a NOTICE/LICENSE specific to each release I think
it should be written in a policy but I would hope this is not enforced because this would
probably be a cause for limiting the number of packages released (creating a new assembly
for the same work is much less work than mantaining a special NOTICE/LICENSE for it).
> Here is the "practice" as described by David Jencks to me:
> ----
> released artifacts should include LICENSE and NOTICE files applying exactly to their
content.   If this goal is not achieved, its better to have unnecessary stuff in the LICENSE/NOTICE
files than missing stuff.
> ----
> The introduction of the 1.4 version for org.apache:apache-jar-resource-bundle changed
the LICENSE/NOTICE added to jars to not include dependencies by default, so people upgrading
from 1.3 will ask this again and again.
> A clear policy IMHO is also a good way to let some smart people create/improve maven
plugins to better manage what the policy says. No written policy means that we all do what
the plugin developer prefererred ;-) (kudos to plugin developers)

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


Mime
View raw message