Hi Mats, Actually I considered the same question and couldn't come up with a perfect answer. It seems to me that we either a) don't include the information (which is very useful to project/release managers) or b) link to Kavi because there is OCF only information in some of the documents (particularly the draft CRs).
Alternately, we could probably scrub the dashboard for public release (in fact at this point it may not be sensitive anyway), and then link to v0.3 of the CRs (which won't be entirely up to date). I felt it was better to give the best info to the IoTivity Security layer developers, QA, and release manager, who are all in OCF anyway, particularly because as Dwarka said it is not hard to join OCF if a person wants an early preview of the CRs/Specifications. I am happy to follow whatever decision makes sense... I'm not passionate about this issue either way, just trying to get it done :) Thanks, Nathan -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Dwarkaprasad Dayama Sent: Friday, March 17, 2017 7:34 AM To: 'Mats Wichmann' <mats at wichmann.us>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Request on IoTivity 1.3 release items. Hi Mats, I don't see any other way to document such entries. Giving direct attachments is anyway illegal. By giving link, we make sure only OCF members know about it. If a community member is not an OCF member, he/she should wait until the information is made public. As such becoming a basic member or individual member is not difficult. So it is encouraged to join OCF if interested to follow OCF discussions. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation ? OSWG ? Spec Coordination TG Chair Iotivity Steering Group ? Advisory Committee -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, March 17, 2017 11:16 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Request on IoTivity 1.3 release items. On 03/16/2017 02:50 AM, ??? (Uze Choi) wrote: > Hi, Feature contributors in 1.3 release. > > > > Please check as below. and respond by this week. > > > > [Jira Registration/Tagging into wiki] > > Please add Jira tick link on > https://wiki.iotivity.org/1.3_release_plan. as like security related item. > > Introspection, Versioning, Endpoint > > MPM, AllJoyn Bridge, UPnP Bridge > > CoAP Native Cloud Project items. > > Generic Java Binding. Just to circle back on this once more - should IoTivity wiki entries or Jira tickets contain links to non-public OCF resources? It's clear that certain developers of iotivity may have to refer to unpublished materials in preparing for a new release, and are able to do so if they "live in both camps", but including such links in the public IoTivity resources makes them opaque to readers without OCF member status. If the team feels this is okay, I won't ask about it any more. Examples: This 1.3 wiki page: === Security updates (see dashboard spreadsheet for details) (the "dashboard spreadsheet" is a link to https://workspace.openconnectivity.org/apps/org/workgroup/security_os_tg/download.php/8839/IoTivity%201.3%20Security%20Feature%20Dashboard.xlsx) === Jira ticket to provide software update hooks (https://jira.iotivity.org/browse/IOT-1786): === The CR 24 can be found on Kavi: https://workspace.openconnectivity.org/apps/org/workgroup/security_wg/download.php/8395/CR_SecWG_OCF1.0_00024.004_SoftwareUpdate.docx ... and the OCF bugzilla is private: The Bugzilla issue number is 1384: https://bugzilla.openconnectivity.org/show_bug.cgi?id=1384 === _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
