Hi,
Am Sonntag, den 17.06.2018, 14:57 -0400 schrieb Emilian Bold:
> 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.
beware! The file from licenses is used for the
1. The files in external/*-license.txt have everything we need. They also have
the 'License:' header. I don't know why the files from nbbuild/licenses are
used for the summary when we could use the files from external dependencies
-license.txt.
2. MIT might be special, but nbbuild/licenses/BSD-
> The way I see it nbbuild/licenses are 'families'. And the 'License:'
> header in external/*-license.txt points to a family. A changing author line
> doesn't change the license itself / the license family.
> You and I are not the target audience for it - lawyers are. If that's what
gets combined
There is a mix of concerns here and we are talking about different things.
It's quite possible that we end up doing mistakes during our IP clearance so if
a super-defensive company wants to use NetBeans they might as well decide to
re-do the IP clearance themselves.
If our template license file
Hi Emilian,
Am Sonntag, den 17.06.2018, 15:24 -0400 schrieb Emilian Bold:
> 1. The files in external/*-license.txt have everything we need. They
> also have the 'License:' header. I don't know why the files from
> nbbuild/licenses are used for the summary when we could use the files
> from externa
My main point is that I assumed that nbbuild/licenses files are licenses of
license *variants*.
For example, if we see a variation of MIT that has one extra clause we invent
some MIT-example file with the clause.
So, the files is nbbuild/licenses are not about authors but about plain
licenses
