[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564925#comment-13564925 ] 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: http://incubator.apache.org/guides/branding.html#disclaimers 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 incubator.apache.org/ 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 documents. In fact, such a page already exists -- it's our infamous [http://incubator.apache.org/guides/releasemanagement.html]. 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: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563830#comment-13563830 ] Suresh Marru commented on INCUBATOR-125: Marvin, great job in putting together this short and concise document. I think it will also be useful to mention about the DISCLAIMER file requirement [1] for the incubator podlings. [1] - http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561341#comment-13561341 ] Marvin Humphrey commented on INCUBATOR-125: --- The page has now been published: http://www.apache.org/dev/licensing-howto.html I chose www.apache.org/dev rather than the Incubator or Legal sites because Legal did not express a desire to own the document and the Incubator docs should in general be shrunk down and should point at the main dev site more often. Please review. Once we have lazy consensus, I'll add a link from the dev index page. > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552464#comment-13552464 ] Marvin Humphrey commented on INCUBATOR-125: --- > 1. I want to start by noting that ** Apache Releases Are Source Releases **. >So I'm somewhat unclear on how convenience binaries fit in. I regret opening that can of worms by mentioning binaries at all. I hope that by deleting everything the document has to say on the subject we can save it from being talked to death. > 2. This document would benefit from a brief definition of what the files are >at the top. I've added an svn branch to track mods to the document: https://svn.apache.org/repos/asf/incubator/public/branches/license_howto/ Thanks for the suggestion, which I implemented here: https://svn.apache.org/viewvc/incubator/public/branches/license_howto/licensing_howto.mdtext?r1=1432804&r2=1432812 > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552284#comment-13552284 ] Benson Margulies commented on INCUBATOR-125: I have some questions / suggestion here. 1. I want to start by noting that ** Apache Releases Are Source Releases **. So I'm somewhat unclear on how convenience binaries fit in. 2. This document would benefit from a brief definition of what the files are at the top. I am going to try to stir up assistance from legal. > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440619#comment-13440619 ] 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 clause. 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: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440563#comment-13440563 ] Sebb commented on INCUBATOR-125: Very useful. compiled package => binary package would be clearer. I don't think it's advisable to incorporate the list of license types; just link to where the official list is found. > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > 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: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
