+1 for
? For the documentation - I believe this is about using Doxygen for the APIs. Better Documentation is a high want from OCF. However - on a 2nd thought - this does not make sense as an own component with a separate owner, for me it does make more sense that every maintainer of a module tries to get this updated anyway :-) ? There are lot of concerns regarding API guidelines and documentation. 1st timer for IoTivity are prone to make mistake on how to use an API or even fail to produce correct runnable binary. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation ? OpenSource WG Vice-Chair | Spec. Cord. TG Chair Iotivity Steering Group ? Advisory Committee From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Christian Gran Sent: Friday, April 07, 2017 8:04 PM To: Bell, Richard S <richard.s.bell at intel.com>; Nash, George <george.nash at intel.com>; iotivity-dev at lists.iotivity.org; Mats Wichmann <mats at wichmann.us> Subject: Re: [dev] Jira changes implemented Hi, sorry - my mistake. It was not the plan to do any new assignments here - just trying to capture the status quo (who does what). For the documentation - I believe this is about using Doxygen for the APIs. Better Documentation is a high want from OCF. However - on a 2nd thought - this does not make sense as an own component with a separate owner, for me it does make more sense that every maintainer of a module tries to get this updated anyway :-) Thoughts? This is now the current status for the components - any volunteers for the ones that do not have a maintainer/default assignee yet? Does this look ok? * AllJoyn-Bridge (Todd Malsbary) * Bridging General (Todd Malsbary) * Build System (???) * Cloud (Jee Hyeok Kim) * Discovery/Connectivity (Ashok Babu Channa) * Documentation (???) ? do we need this component? * Generic Java (Rick Bell) * Node.js Bindings (???) * Notification service (Poovizhi Avudai) * Platform Support (Dave Thaler) * Primitive Service (Uze Choi) * Remote Access (???) * Sample Application (???) * SDK (Uze Choi) - Deprecated - do use more specific component if possible * Security (Randeep Singh) * Transport (???) * UPnP Bridge (Rick Bell) * web site (Thiago Macieira) thanks Christian On 7. Apr 2017, at 01:03, Bell, Richard S <richard.s.bell at intel.com <mailto:richard.s.bell at intel.com> > wrote: Christian, George is on my team and we cannot sign up as owners of the build system. We will handle any build issues related to Android but not the build system as a whole. One other item, we need to figure out how to address is public SDK APIs in regards to Android. We have been finding developers creating new public APIs but not implementing Android/JNI. We only find them when somebody looks for them in Android and find that it had not been implemented. They will also go unnoticed when new public APIs are created without jira ticket not and just doing patches. First we need to require Jira for any change and second we need to have a some type of flag indicates that we need Android/JNI implemented or has been implemented. Thanks, -Rick From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of Nash, George Sent: Thursday, April 6, 2017 3:34 PM To: Christian Gran < <mailto:gran at lynxtechnology.com> gran at lynxtechnology.com>; <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jira changes implemented Christian, I am not sure that I am the right person for the Build System. If I do become the lead for Build Systems I will need to develop a lot more contacts. :) I am well versed in the build system for most of the OSs but so far I have not been the lead for any of that work. Also what is the Documentation portion? Is this API documentation, Wiki documentation, or Web site documentation? George Nash From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of Christian Gran Sent: Thursday, April 6, 2017 5:03 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] Jira changes implemented Hi, most of the changes from the Wiki have now been implemented ( <https://wiki.iotivity.org/jira_proposed_changes> https://wiki.iotivity.org/jira_proposed_changes) We now have these components (lead listed in brackets): * AllJoyn-Bridge (Todd Malsbary) * Bridging General (Todd Malsbary) * Build System (George Nash) * Cloud (Jee Hyeok Kim) * Discovery/Connectivity (Ashok Babu Channa) * Documentation (???) * Generic Java (Rick Bell) * Node.js Bindings (???) * Notification service (Poovizhi Avudai) * Platform Support (Dave Thaler) * Primitive Service (Uze Choi) * Remote Access (???) * Sample Application (???) * SDK (Uze Choi) / Deprecated - do use more specific component if possible * Security (Randeep Singh) * Transport (???) * UPnP Bridge (Rick Bell) * web site (Thiago Macieira) For the components with ???, I do not know the component lead. Would be great if you could send me the information, so that I can update it in Jira :-) Please send me a note if there is a mistake (wrong component lead, or something else). Please also have a look at <https://wiki.iotivity.org/jira_how_to_use> https://wiki.iotivity.org/jira_how_to_use thanks Christian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170407/5210d251/attachment.html>
