On Aug 18, 2017 3:07 PM, "Thiago Macieira" <[email protected]> wrote:
On Friday, 18 August 2017 12:03:01 PDT Dave Thaler via iotivity-dev wrote: > “should not vendor-specific features go in vendor-specific > forks or libs? otherwise we end up with a kitchen sink o' cruft.” > > Completely agree with that. Vendor-specific features should never be coded > (even if #ifdef’ed) into the middle of files in the master branch, in my > view. But they may be accepted in IoTivity, so long as they don't clutter the code or give the wrong impression of being official? iotivity, the project, or iotivity, the ocf implementation? my 2 cents: the project is an appropriate home for vendor-contributed "add-ons", but the iotivity core/kernel implementation is not. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
