Close, but not quite (yes I was there in that discussion via webex). iOS/MacOS are desirable platforms for the main iotivity code, so we want them to keep being verified and want a submaintainer.
Arduino is not in that category, and so it can be removed entirely from Jenkins verification in the main codebase, and instead be done in the iotivity-constrained project only. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Thursday, March 23, 2017 4:10 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Should IoTivity Arduino support be dropped? Our discussion was as follows in F2F meeting in AMS. The release perspective, Arduino/iOS(MacOS) are not tested. But Jenkins perspective Arduino/iOS(MacOS) builds are verified. If there is any issue in these platform build (especially Arduino), remove this build from Jenkins verification. Otherwise keep it until iotivity-constraint to be released in public for Arduino case. We are still open for iOS build submaintainer. BR ,Uze Choi From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Dave Thaler via iotivity-dev Sent: Thursday, March 23, 2017 1:24 PM To: Thiago Moura; Thiago Macieira Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Should IoTivity Arduino support be dropped? It was never certifiable before, and not fully working either (e.g., security never worked), so any jenkins CI ?testing? just slows down the builds for everything else without any real value. We just don?t want to destabilize the source until after 1.3 releases and then we can do clean up. From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Thiago Moura Sent: Wednesday, March 22, 2017 8:40 PM To: Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Should IoTivity Arduino support be dropped? > but such cleaning patches should wait until after 1.3 is released. > And yes the helpdesk ticket is still waiting for action from CJ. I am not sure if I follow the plan.. Arduino is still part of the 1.3 release but isn't going to be tested anymore? On Wed, Mar 22, 2017 at 11:23 PM, Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>> wrote: On quarta-feira, 22 de mar?o de 2017 09:47:48 PDT Thiago Moura wrote: > Well, it's been awhile and no decision on this topic. The decision was made after discussion on the mailing list: Arduino support is being removed from the IoTivity Standard. If anyone wants to revive it, they're welcome to do so in Constrained. > I am very curious if anyone here is developing real products based on > arduino (due/mega). Intel's research shows no one develops products with Arduino. They use it for early proof-of-concepts, then throw everything away and rewrite the code (no code reuse) when going to actual product prototypes. At most, Arduino gets used by hobbyists for one-off implementations in their own homes. So it's worthwhile to make it work, but not at the expense of real products. > Back to the subject.. I think dropping support for Arduino will benefit > everyone - Increase maintainability(code and build system cleanup), faster > CI and less headaches for project managers. I've found this > opened/unresolved tickets on Jira, most of them pending for more than 1 I agree. -- Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com> Software Architect - Intel Open Source Technology Center -- Thiago Guedes Cunha de Moura Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170323/5e011152/attachment.html>
