Hi Dave, actually the list was just taken from the list of IoTivity projects: https://wiki.iotivity.org/projects_and_functions
Totally agree that there is some overlap between bridging in general and the more concrete bridges. The idea is simply that - when a new issues is created - it can be correlated to the source code, which in general resides in a sub folder of one of these ?projects?/bridges. I hope this does explain, why there is a proposal to have one component per ?project? listed on the IoTivity projects page. It shall help to assign issues/bugs found to the correct maintainers. But may be this is a wrong idea and this would not help in assigning bugs at all? thanks Christian On 29 Mar 2017, at 20:12, Dave Thaler <dthaler at microsoft.com<mailto:dthaler at microsoft.com>> wrote: Under proposed components, the wiki page shows: * Bridging (Todd Malsbary) * UPnP Bridge (Rick Bell) * AllJoyn-Bridge (Todd Malsbary) I don't understand the distinction between the first one and the others, it may just be a naming thing. In the OCF bridge spec, the term "bridge" is the term for a device independent of protocol, and "translator" is the term for a protocol-specific plugin in a bridge. So would "Bridging" include any translators or not? Shouldn't "AllJoyn-Bridge" be "AllJoyn translation" or something similar, if it's a separate JIRA component? Or we could combine translators into a common Bridging component in JIRA. But if we break them out then we should consistently break out a new component for every translator for every protocol (which might seem excessive). Dave -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org<mailto:[email protected]> [mailto:iotivity-dev- bounces at lists.iotivity.org<mailto:bounces at lists.iotivity.org>] On Behalf Of Mats Wichmann Sent: Tuesday, March 28, 2017 9:20 AM To: Christian Gran <gran at lynxtechnology.com<mailto:gran at lynxtechnology.com>>; iotivity- dev at lists.iotivity.org<mailto:dev at lists.iotivity.org> Subject: Re: [dev] Jira cleanup On 03/27/2017 11:31 PM, Christian Gran wrote: Hi, is there still something that needs to be changed here? https://wiki.iotivity.org/jira_proposed_changes https://wiki.iotivity.org/jira_how_to_use thanks Christian I'd like to see the "proposed changes" page implemented, doesn't mean we have to be completely done with the other discussions. Were there answers for the bits with questions? (mainly whether to have any presence of iotivity- constrained and iotivity-node). The updated/added components would be helpful in categorizing. _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/85ddbbf7/attachment.html>
