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 Tue, 29 Jan 2013 00:59:13 GMT


Marvin Humphrey commented on INCUBATOR-125:

> I think it will also be useful to mention about the DISCLAIMER file
> requirement [1] for the incubator podlings.

The DISCLAIMER file is already documented here:

In my view, it would not be appropriate to mention DISCLAIMER in the
LICENSE/NOTICE how-to.  LICENSE and NOTICE are tightly intertwined, but
DISCLAIMER is only related to them insofar as they are all required to be
present in incubating releases.

What we need is a page under which enumerates the
requirements for incubating releases, and which ought to link to *both* the
licensing how-to and the DISCLAIMER documentation along with many other

In fact, such a page already exists -- it's our infamous

Unfortunately, that page is monumentally bloated because everything including
the kitchen sink has been thrown into it, regardless of whether the additions
duplicate information found elsewhere -- or even right there on the page itself.

Rather than add material to the licensing how-to because
releasemanagement.html fails to serve its purpose, we should work to improve
releasemanagement.html itself.
> 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
For more information on JIRA, see:

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

View raw message