Nice! But why is this info living outside the IOTivity documentation? e.g. how can one know these kind of things? Hence can we have at least links from IOTivity to this documentation and then an set of repos that will act as
The whole idea that I have is that this code is useful but not necessary, and it will be tight to an specific release. e.g. it will become stale if api changes.... Which is ok.. Hence maintenance is limited, it will be checked that it works under certain conditions.. and the conditions should be documented (e.g. the used release version etc..). e.g. see it as reference code for an particular solution. Maybe we should even go that far to make an new github organisation something like "IOTivity-code-snippets" Kind Regards, Wouter From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Philippe Coval Sent: 22 February 2018 18:00 To: iotivity-dev@lists.iotivity.org Subject: Re: [dev] clear distinction of what is below and above the APIs On 02/22/18 16:19, Wouter van der Beek (wovander) wrote: Hi All, Hi Wouter ! Related to this, I am will be working on application level code, e.g. using the IOTivity API. I like to contribute this code to IOTivity or other open source project. of course you can create your own repo I will not be maintaining it for long, e.g. if the IOTivity API changes it will be broken... So you expect someone else to fix it ? I guess that means that is it should not be in the main tree of IOTivity... yea I am not sure it makes sense to push in iotivity if there is no maintenance on examples, we had several ones that are no more tested, at least bug can be reported (and fixed) hence we need an solution to store this kind of code. I agrea on need of having some apps of iotivity tree, and keep few reference ones well maintained in it. Any ideas? Well, as said before, I shared this template project, for apps living out of iotivity tree (demos etc), http://git.s-osg.org/iotivity-example/ http://git.s-osg.org/iotivity-example/plain/README.md To deal with API (or breaking) changes, I am relying on branches: http://git.s-osg.org/iotivity-example/log/?h=clock/master http://git.s-osg.org/iotivity-example/log/?h=clock/1.2-rel Check more explanations at: https://blogs.s-osg.org/prototype-insecure-iotivity-apps-secure-library/ To get the pattern, here is slightly improved example: http://git.s-osg.org/iotivity-example/log/?h=brightness/1.2-rel http://git.s-osg.org/iotivity-example/log/?h=brightness/master I can give more details if interested, but first I am open to feedbacks My 2c
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
