Ok, thanks - in any way, it is a clear +1 from me! I’ll make use of this myself I guess :-)
Btw, I just noticed that usb4java changed the license from LGPL to MIT 16 days ago only - I assume you were involved in that decision making process…?
Mike, regarding a) i. and ii.: Imho the definition of „requires 3rd party software“ is a bit fuzzy. What does it mean? It is enough to be able to start up without an exception to claim that one does not require it? "where the Eclipse code works“ - well, it does not work in this case if you try to access the USB functionality, you will see exceptions. That’s why I prefer to talk about „optional functionality“, which means that no fundamental functionality is concerned by such a dependency and that the product is still usable in general and you simply must not use certain features.
Best regards, Kai
On 10/06/2015 12:51 PM, Kai Kreuzer
wrote:
Works-with usually means that the product has an
equivalent other option - is this the case for USB or do we follow
the argument that Kura will only use it in an optional bundle and
thus Kura can work without it?
Just to add to this a little bit. David's reply on this point was
correct. That is only one half of the definition of works-with. They
can also be optional dependencies where the Eclipse code works even
if that dependency is not available.
From
https://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf
(emphasis added)
a) Works-with Dependencies:
i. The Eclipse software does not require the third
party software to be present. If the third party software
happens to be present, the Eclipse software may call or invoke
it. Example: If a web browser is present, clicking on
URL's in Eclipse will cause the user's configured web browser to
open the URL.
or
ii. The Eclipse software is designed to work with multiple third
party software choices that provide similar functionality - the
choice of which to use is up to the user. At least one of those
must be a prerequisite (see below) or approved by the EMO for
distribution by the project. Example: If a project requires a
persistence mechanism, it can allow the user to select from
several different implementations.
Hope that helps!
_______________________________________________ iot-pmc mailing list iot-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/iot-pmc
|