Ha, my calendar is off ("February 31st") :)
I meant Friday April 3rdFrom: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Dave Thaler via iotivity-dev Sent: Friday, February 24, 2017 11:19 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Should IoTivity Arduino support be dropped? As platform support project architect/maintainer, I am calling the question... I have previously heard arguments on this list for dropping Arduino support in IoTivity itself, which I will summarize as: 1) IoTivity-constrained is designed for this use case and should be used instead 2) Some code paths have not been maintained for some time 3) There is no IoTivity submaintainer for Arduino I have not yet heard arguments to keep it. So the question is: should we drop Arduino support in IoTivity and instead refer Arduino developers to IoTivity-constrained? If yes, the plan would be to * immediately turn off the jenkins CI build which would then leave more capacity to speed up other builds, and * over time remove the arduino-specific #ifdef'ed code paths. If anyone has technical objections to this plan, please explain why by Friday February 31st (and be prepared to suggest someone to be Arduino submaintainer). Thanks, Dave Thaler -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170224/79897837/attachment.html>
