Any comments before I go ahead and fill in the list of corresponding maintainers on the wiki and let any corrections be made there? For gtest, I guess I would put the CTT maintainer(s) as they are the QA lead(s) as I understand it. Speak up if that's not correct.
From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Dave Thaler via iotivity-dev Sent: Tuesday, September 20, 2016 11:45 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Maintainers for extlibs Currently https://wiki.iotivity.org/projects_and_functions has ource path Project or note Active Maintainer, Sub-maintainers and experts extlibs Third-party libraries, shared responsibility The problem is that there's no point maintainer for extlibs, and so it's hard to know who to add as reviewers when a change is made (e.g., to the sconscript file associated with the extlib, or discussions about what version it uses, or obsoleting it, or whatever else). Based on what projects actually use various extlibs, here's a proposed table. Not sure if this is correct, but this is a first cut: Android Platform Support (Android) Arduino Platform Support (Arduino) Asn1cert Security Bluez Connectivity Boost Platform Support Cjson Connectivity Gtest ? Libcoap Connectivity Libstrophe IoTivity Cloud Mbedtls Security Rapidxml Primitive Service Raxmpp IoTivity Cloud Sqlite3 Security Timer Platform Support Tinycbor Connectivity Tinydtls Security Wksxmppxep IoTivity Cloud Yaml Primitive Service Zigbee Connectivity Feedback/corrections? I'd suggest we update the wiki page to list each extlib in the table and list the relevant project's maintainers next to it. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160922/d1b62f37/attachment.html>
