Thanks Marvin, that helped me out quite a bit!

- Taylor


On Dec 11, 2013, at 12:24 AM, Marvin Humphrey <mar...@rectangular.com> wrote:

> On Tue, Dec 10, 2013 at 8:10 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> It's kind of interesting to see how this has changed over time and varies
>> from project to project.
> 
> Here's Roy Fielding in June 2008, saying exactly the same thing you'll hear
> from us now:
> 
>    http://s.apache.org/Y4v
> 
>    If the notices aren't required by the bits in the package, then they
>    don't belong in NOTICE.  That means there will be a different NOTICE file
>    required for each differently packaged set of bits.  We must do this by
>    hand.
> 
> Because the file is named "NOTICE", people tend to think it's for anything
> notice-ish.  This is a pernicious misconception which keeps coming back over
> and over like a weed, and it used to be that not a lot of people besides Roy
> were effective at combatting it.  Here's Roy in 2008 again:
> 
>    http://s.apache.org/ZIU
> 
>> Furthermore, I assume it is not problematic to have more stuff in the
>> NOTICE file(s) than is really required.
> 
>    Yes, it is problematic.  Consider it a tax on all downstream recipients.
> 
> Roy can't be everywhere, though, and there are a lot of TLPs who have messy
> licensing documentation because they didn't get proper guidance.
> 
> The Licensing How-To, added earlier this year, provides a cookbook approach
> which is supposed to yield appropriately sparse LICENSE and NOTICE files.
> 
>    http://www.apache.org/dev/licensing-howto.html
> 
> Hopefully the Incubator is now more consistently graduating projects whose
> licensing documentation approaches the unchanging minimalist ideal.
> 
> Marvin Humphrey
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to