On 5 Oct 2016, at 19:03, Nick Boldt wrote:
* There was also much discussion around the new Type A (only the
license is checked) vs. Type B (old school full due diligence, with
code provenance checked too) licensing. Decision was to only include
type B stuff in release train for now, and wait for projects to
complain they should be included, or perform more due diligence to be
upgraded to Type B. Including Type A stuff opens a lot of trickle-down
problems that no one wants to deal with unless we have to, such as
"will end users still be allowed by their employer to use Eclipse, if
there's no longer a guarantee of provenance check in the bundles?".
More:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=501014
gah - thats annoying.
Do they even have a Type A project yet to exclude ?
Why not be open by default and handle it if there are issues ?
/max
http://about.me/maxandersen