Hi,
Thx Kai.
We faced some issue with some _javascript_ library mainly for
demo, as it's possible I prefer to avoid this.
I also think it's not a bad thing to not overload the IP team
with checks we don't really need.
So let's go for Type A.
Simon
Le 31/07/2017 à 10:47, Hudalla Kai
(INST/ECS4) a écrit :
Hi Simon,
we have been conferring regarding leshan's switch to the Type A
IP process and we are ok with the change.
However, it is still unclear to me, what you expect to get out
of it for leshan, given that we do not have many dependencies
that we need to keep current. We still need to create CQs for
dependencies, regardless of whether we use Type A or B ...
Mit freundlichen Grüßen /
Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court:
Amtsgericht Charlottenburg, HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach,
Michael Hahn
Just for information : "By default all new projects at the
Eclipse Foundation now start configured to use
Type A by default."
Le 04/07/2017 à 19:06, Kai a écrit :
Hi Simon,
Achim and I will need to confer with our open
source governance team in order to determine if this poses
a problem for us. We'll come back with the results as soon
as we have a better understanding of the implications. My
gut feeling currently is that Bosch would have a problem
with this but as I said, we need to check. Sorry for
delaying things but we take these kinds of things pretty
seriously. Hope you understand.
Kai
So, Achim ok to go for Type A ? :)
Le 04/07/2017 à 16:19, Simon Bernard a écrit :
> Type B means more IP constraints especially when we
want to integrate
> new dependency, but "theoretically" this bring more
legal warranty.
>
> If nobodies needs this legal warranty, I prefer to
not add unnecessary
> process/constraints.
>
> If one day someone needs/ask for a Type B release
we could consider to
> launch the fat IP check process at this time. If
problems will be
> detected we will try to resolve it by using
alternative dependency or
> just removing not absolutely needed dependency.
(e.g. remove a
> problematic _javascript_ library in leshan server
demo)
>
> This does not mean that we should not pay attention
to future
> dependencies we integrate in Leshan.
>
> Le 04/07/2017 à 15:07, Kraus Achim (INST/ECS4) a
écrit :
>
>> Hi Simon,
>>
>> I'm not sure, if I understand Type A and B
well enough.
>> So my impression is, that A would make it
easier to introduce new
>> dependencies.
>> Are there any planned extension in that
direction?
>>
>>> (knowing that it should possible to make a
Type B release if it's
>>> really needed)
>> I would guess, that the way, how it is decided,
when a Type B release
>> is really needed, would be the real issue :-).
>>
>> Mit freundlichen Grüßen / Best regards
>>
>> Achim Kraus
>>
>> (INST/ECS4)
>> Bosch Software Innovations GmbH | Stuttgarter
Straße 130 | 71332
>> Waiblingen | GERMANY |
www.bosch-si.com
>>
>> Sitz: Berlin, Registergericht: Amtsgericht
Charlottenburg; HRB 148411 B
>> Geschäftsführung: Dr.-Ing. Rainer Kallenbach,
Michael Hahn
>>
>>
>>
>> -----Original Message-----
>> From: leshan-dev-bounces@xxxxxxxxxxx
>> [mailto:leshan-dev-bounces@xxxxxxxxxxx] On
Behalf Of Simon Bernard
>> Sent: Mittwoch, 28. Juni 2017 17:18
>> To: leshan developer discussions <leshan-dev@xxxxxxxxxxx>
>> Subject: [leshan-dev] Change Leshan IP Type
from Type B to Type A
>>
>> Hi all,
>>
>> Ok ok, the mail subject is a bit
mysterious.
>> For people we don't really know what is
Type B/A, here[1] is a
>> good explanation.
>> So the question is : Are you ok if Leshan
go for Type A (knowing
>> that it should possible to make a Type B
release if it's really needed)
>>
>> Simon
>>
>> [1]https://waynebeaton.wordpress.com/2017/01/16/eclipse-infrastructure-support-for-ip-due-due-diligence-type/
>>
>>
>> _______________________________________________
>> leshan-dev mailing list
>> leshan-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your
password, or
>> unsubscribe from this list, visit
>>
https://dev.eclipse.org/mailman/listinfo/leshan-dev
>> _______________________________________________
>> leshan-dev mailing list
>> leshan-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your
password, or
>> unsubscribe from this list, visit
>>
https://dev.eclipse.org/mailman/listinfo/leshan-dev
>
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your
password, or
> unsubscribe from this list, visit
>
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
|