But the 'License:' header already represents a 'family'. That's why 
MIT-validator should not exist in nbbuild/licenses: it's just the plain MIT 
license with a particular author.

--emi

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On 17 June 2018 9:14 PM, Matthias Bläsing <[email protected]> wrote:

> Hi Emilian,
> 
> Am Samstag, den 16.06.2018, 02:38 -0400 schrieb Emilian Bold:
> 
> > I think we are starting to have too many files in nbbuild/licenses/
> > 
> > The way I understand it, inside $module/external/$somelib-license.txt
> > 
> > we have the actual license of the external dependency and we add a
> > 
> > header 'License: $licenseID' which is there to help us group the
> > 
> > licenses.
> > 
> > Then we find the 'generic' license in nbbuild/licenses/$licenseID,
> > 
> > for example nbbuild/licenses/MIT
> > 
> > I see we have duplicates in nbbuild/licenses.
> > 
> > For example MIT and MIT-validator are basically identical except for
> > 
> > some different way word-wrap was used. (Same with BSD and BSD-
> > 
> > postgresql).
> > 
> > Different files in nbbuild/licenses/ should only reflect different
> > 
> > licenses, not different authors.
> > 
> > So MIT-validator would only make sense if it's a new license, based
> > 
> > on MIT, but with some changed paragraphs.
> > 
> > Is my understanding correct?
> 
> I see a difference between MIT and MIT-validator. The difference is
> 
> subtle, but present:
> 
> --- a/MIT
> 
> +++ b/MIT-validator
> 
> @@ -1,7 +1,6 @@
> 
> -The MIT License
> 
> +Copyright (c) 2005, 2006 Henri Sivonen
> 
> +Copyright (c) 2007-2010 Mozilla Foundation
> 
> -Copyright (c) YEARS, NAMES
> 
> 
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
>     Permission is hereby granted, free of charge, to any person obtaining a 
> copy
>     of this software and associated documentation files (the "Software"), to 
> deal
>     in the Software without restriction, including without limitation the 
> rights
>     
> 
> Other licenses don't vary, but here the header changes. What we could
> 
> do from my perspective is to add a new attribute "license-family" (MIT,
> 
> BSD-2 Clause, ...) to the "-license.txt" files to get a generalunderstanding 
> and use the full license text from "-license.txt" to
> 
> build the distribution licenses. This way the license text would not be
> 
> duplicated.
> 
> As I see it, each instance of the MIT license (differing by copyright
> 
> year + holder) forms its own license file.
> 
> Greetings
> 
> Matthias
> 
> 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> To unsubscribe, e-mail: [email protected]
> 
> For additional commands, e-mail: [email protected]
> 
> For further information about the NetBeans mailing lists, visit:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to