Hi Philippe,
Question for your suggestion for separate git. Even if we separate the git into IoTivity core(with API) and IoTivity Samples. How are they related with developer?s accessibility and maintenance? Could you share the your idea more specifically? BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Philippe Coval Sent: Thursday, April 21, 2016 4:36 PM To: markus.jung at samsung.com Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Improve IoTivity documentation and samples On Thu, Apr 21, 2016 at 3:02 AM, Markus Jung <markus.jung at samsung.com> wrote: Hello, next week is the Samsung Developer Conference which gives IoTivity a good visibility opportunity. Therefore, it would be great if all maintainers and contributers can have a look on the documentation, wiki and sample apps. Hi, I started to share some of my knowledge about tizen support, and specially detailed all steps to use iotivity on actual tizen devices (as native app for Z1 or GearS2) : https://wiki.iotivity.org/tizen Feel free to edit that page, to make IoTivity more accessible to Tizen community. By the way here is a general overview and demos presented recently : http://www.slideshare.net/SamsungOSG/iotivity-on-tizen-how-to The question I have, do you think it's a good idea to have sample apps shipped into main IoTivity project as some of them seems no more maintained ? I would suggest to have them in separate git and eventually linked to main project using gitmodules ? I am asking this because I have also a couple of sample apps that could be pushed upstream But I believe a separate project would make it easier to developers, (my apps are shipping a setup.sh script to fetch build iotivity and deps). My 2 cents -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160421/53b97a21/attachment.html>
