incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <>
Subject [jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
Date Thu, 23 Aug 2012 20:24:42 GMT


Marvin Humphrey commented on INCUBATOR-125:

Hi, Sebb,

Thanks for the review!

> compiled package => binary package
> would be clearer.

+1, sounds good.

> I don't think it's advisable to incorporate the list of license types; just
> link to where the official list is found.

That list and the list of license types from the ASF legal FAQ are not the
same.  While most (?) licenses in "category A" do not include "required third
party notices" that may have to go into NOTICE, there are at least 3
exceptions: ALv1.0, ALv1.1, ALv2.

The reason that the ALv2 is broken out is because it must be treated
differently from BSD, MIT, etc, what with its NOTICE file.

ALv1.1 will require an additional special section because of its advertising

It's possible that other licenses in "category A" also have special
requirements.  There's a TODO item in the draft document to perform that
research (presumably via legal-discuss) before the page goes live.

In my view, it's essential to do this work in advance so that PMCs don't wind
up poring over the text of licenses trying to figure out whether something
needs to go into NOTICE or whatever.  That's what leads to people deciding
that the copyright notice in a BSD license has to go into NOTICE -- because
that sure sounds like a "required third party notice", right?  (see LEGAL-59.)
> How-to guide for "Assembling LICENSE and NOTICE"
> ------------------------------------------------
>                 Key: INCUBATOR-125
>                 URL:
>             Project: Incubator
>          Issue Type: Improvement
>          Components: site
>            Reporter: Marvin Humphrey
>         Attachments: licensing_howto.mdtext
> While the ASF provides reference documentation for LICENSE and NOTICE,
> confusion persists and existing versions vary widely in quality.
> To address these problems, we should augment the reference documentation with
> a "how-to" guide which provides formulaic instructions for assembling LICENSE
> and NOTICE under common conditions.
> One key feature of this how-to should be a mapping of approved licenses to
> what they require as far as NOTICE.  This mapping will help PMCs determine
> when the licensing information of a dependency contains a "required third
> party notice" which must be added to NOTICE.
> There are at least four possible locations where this how-to might live:
> * -- probably the best location,
>     considering the intended audience.
> * -- if legal wants it.
> * -- probably not ideal,
>     because the information applies to TLPs as well as podlings and we have a
>     problem with duplication.
> *   Somewhere on -- in theory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message