Hi Wouter, U+ code is proprietary for now, and only APIs are open. So we don’t have any licenses or agreements for the codes. The codes of U+ bridge will be open and follow IoTivity licence.
Regards, Betty Zhao Haier Group -----Original Message----- From: Wouter van der Beek (wovander) [mailto:[email protected]] Sent: 2017年7月13日 17:39 To: Betty Zhao; 'Thiago Macieira' Cc: [email protected] Subject: RE: [dev] New project for approval What about the code of the bridge on the U+ slide? Will that have the same licence agreement? I am expecting that the U+ code will be existing open source code somewhere. And the U+ code is being compiled in an client/server as an library or as an link to an src repo that gets compiled during the build. Thiago, what are the license rules to use an existing open source library? Kind Regards, Wouter -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Betty Zhao Sent: 13 July 2017 09:31 To: 'Thiago Macieira' <[email protected]> Cc: [email protected] Subject: Re: [dev] New project for approval Hi Thiago, Thank you for clarification. I was a bit confused at the beginning. U+ bridge can be a plug-in in the main repository, and it will follow the licenses of IoTivity. So what I should do next is to create a U+ plug-in sub-repository in the main bridging repository, right? Regards, Betty Zhao Haier Group -----Original Message----- From: Thiago Macieira [mailto:[email protected]] Sent: 2017年7月11日 22:47 To: Betty Zhao Cc: [email protected]; '최우제 (Uze Choi)' Subject: Re: [dev] New project for approval On terça-feira, 11 de julho de 2017 00:04:58 PDT Betty Zhao wrote: > Hi Thiago, > > I’m not sure I can explain it in purely technical terms, because I > don’t know and didn’t find the criteria for creating a new IoTivity > project. And I’m not aware of the pros and cons of creating a new one either. > > Both UPnP-Bridge and AllJoyn-Bridge have separate Git repository if I > understand correctly. U+ Bridge is peers with them, although it may be > much simpler in the implementation. The two bridges do, but for two different reasons: * the UPnP bridge uses a library whose licence is not compatible with the main IoTivty licence, so it cannot live in the same repository * the AllJoyn bridge is an application (a large one), not a plugin and is not meant to be loaded into regular server applications At the same time, the Nest bridge is a plugin and lives in the main repository. I'm simply asking you what part of your design requires it to be a separate repository. Or, put it separately, why can't it be a plugin in the main repository? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
