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:iotivity-dev- > 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>; iotivity- > 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
