Hi Sakari, I understand your preference and looks also reasonable. However, IoTivity has the single repository concept as of now. Only for the different licensed project, we place the other repository specially.
Anyway, I don't agree with your opinion clearly yet. The concept of existing .so could bring discrepancy between the latest protocol and so on. Whenever update from somewhere in the iotivit core stack, it will be better to be verified from node.js perspective. Could you explain the what kind of different API and implementation the node.js has? If you think about the soletta integration, let keep it later. I'm a little doubtful to put the whole soletta code into IoTivity because layer is a different. Anyway, IoTivity gets bigger and bigger, so we need to think about the separating repository also. But it need to be done for whole module and block together. BR, Uze Choi -----Original Message----- From: Poussa, Sakari [mailto:[email protected]] Sent: Wednesday, March 30, 2016 5:11 PM To: ???(Uze Choi); Macieira, Thiago Cc: iotivity-dev at lists.iotivity.org; 'Trevor Bramwell' Subject: Re: [dev] Requesting a repository for the IoTivity JavaScript bindings On 3/30/16, 04:28, "???(Uze Choi)" <uzchoi at samsung.com> wrote: >Hi Sakari, Sorry for late response. > >Could you clarify that node.js repo refers to iotivity.git repo as >external dependent library for base layer, [sakari] iotivity-node refers to iotivity git as an external repo. During the iotivity-node build, the developer can choose if he downloads the iotivity-node as part of the build OR uses an already existing .so and headers from the iotivity repo. > >Otherwise you want to keep the separate base layer code on new git repo? [sakari] I want to have a separate repo for the iotivity-node. No all the people want to download the Node.JS bindings for iotivity. Making a separate repo makes it possible. >I assumed that iotivity-node.js is same as language port such as Android, iOS >and Windows. [sakari] The concept is the same but totally different API and implementation >With the different platform build option, we can set up the build system. >I still cannot find any difference from other language port. [sakari] I think it would be cleaner this way. Sakari > >BR, Uze Choi >-----Original Message----- >From: Poussa, Sakari [mailto:sakari.poussa at intel.com] >Sent: Wednesday, March 30, 2016 4:53 AM >To: Macieira, Thiago; ???(Uze Choi) >Cc: iotivity-dev at lists.iotivity.org; Trevor Bramwell >Subject: Re: [dev] Requesting a repository for the IoTivity JavaScript >bindings > >Hi, > >I want a separate repo for the iotivity-node. Dont want to merge it to the >existing one. You can think it as an extension to iotivity. > >I think quite a lot of other current iotivity directories should be separate >repos instead of inside one. > >Can you create a repo? iotivity-node is the name. > >Sakari > > > > >On 3/25/16, 18:12, "Macieira, Thiago" <thiago.macieira at intel.com> wrote: > >>Hello Uze >> >>I don't think merging the code inside of iotivity.git is a good idea >>for the node.js support. The buildsystem is completely different and >>won't integrate with IoTivity's. Besides, I believe Sakari's plans >>also include making the API work on top of Soletta, not just main IoTivity. >> >>On sexta-feira, 25 de mar?o de 2016 17:22:30 PDT ???(Uze Choi) wrote: >>> Hi Sakari, >>> >>> Do you want the new repo in IoTivity? >>> I think it will be better to include it into iotivity.git repo. >>> Create the appropriate directory to push over there. >>> Anyway, new branch looks required. >>> Let me create the branch first ?iotivity-node? branch? (done) >>> >>> Clarify who should have the maintainer permission?so that Trevor can >>> include him as maintainer-group. >>> >>> BR, Uze Choi >>> -----Original Message----- >>> From: iotivity-dev-bounces at lists.iotivity.org >>> [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of >>> Poussa, Sakari Sent: Thursday, March 24, 2016 9:00 PM >>> To: Macieira, Thiago; iotivity-dev at lists.iotivity.org >>> Subject: Re: [dev] Requesting a repository for the IoTivity >>> JavaScript bindings >>> >>> Hi, >>> >>> Can we create the repo so we can move the iotivity-node code under >>> iotivity.org ? >>> >>> Who should I ping to get this moving? >>> >>> Sakari >>> >>> On 3/1/16, 17:04, "iotivity-dev-bounces at lists.iotivity.org on behalf >>> of >>Thiago Macieira" <iotivity-dev-bounces at lists.iotivity.org on behalf of >>thiago.macieira at intel.com> wrote: >>> >Hello >>> > >>> >The bindings were relicensed. >>> > >>> >Are there any further requests or objections to the project? >>> > >>> >On ter?a-feira, 23 de fevereiro de 2016 08:05:07 PST Thiago Macieira wrote: >>> >> Hello Jinguk >>> >> >>> >> Let me check if that is possible. >>> >> >>> >> On ter?a-feira, 23 de fevereiro de 2016 09:07:06 PST ??? wrote: >>> >> > Thiago, >>> >> > >>> >> > Could you or sakari upload IoTivity JS source codes with Apache v2.0? >>> >> > >>> >> > BR >>> >> > >>> >> > Jinguk Jeong >>> >> > >>> >> > ------- Original Message ------- Sender : Thiago >>> >> > Macieira<thiago.macieira at intel.com> >>> >> > Date : 2016-02-23 01:20 (GMT+09:00) Title : Re: [dev] >>> >> > Requesting a repository for the IoTivity JavaScript bindings >>> >> > >>> >> > On segunda-feira, 22 de fevereiro de 2016 16:01:57 PST Brian >>> >> > Warner >>wrote: >>> >> > > Hi Thiago, >>> >> > > >>> >> > > Could you please provide a little more info? For example, >>> >> > > the link to the repo and the license under which it will be >>> >> > > contributed? >>> >> > >>> >> > It's currently at >>> >> > >>> >> > https://github.com/otcshare/iotivity-node >>> >> > >>> >> > and has been developed using the MIT licence. >>> > >>> >-- >>> >Thiago Macieira - thiago.macieira (AT) intel.com >>> > >>> > Software Architect - Intel Open Source Technology Center >>> > >>> >_______________________________________________ >>> >iotivity-dev mailing list >>> >iotivity-dev at lists.iotivity.org >>> >https://lists.iotivity.org/mailman/listinfo/iotivity-dev >>> >>> _______________________________________________ >>> iotivity-dev mailing list >>> iotivity-dev at lists.iotivity.org >>> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> >> >>-- >>Thiago Macieira - thiago.macieira (AT) intel.com >> Software Architect - Intel Open Source Technology Center >> >
