I think there needs to be someone (tech writer or not that) that is curating the documentation to make it *MUCH* better. In trying to write the objective-c interface, I run across things like QoS with no explanation on what it means. It?s enum is High,Med,Low, but under the hood it?s confirmable or not-confirmable.
https://api-docs.iotivity.org/0.9.0/namespace_o_c.html#aa6b5415cd75a9061b54 6d8c5e6faebde On 4/14/15, 12:50 PM, "Thiago Macieira" <thiago.macieira at intel.com> wrote: >On Tuesday 14 April 2015 16:20:17 Bowden, George wrote: >> Back in January we discussed the need for a tech writer for IoTivity >> documentation (API docs, release notes, Wiki content, web content, >> etc.). Today I?m seeing many requests to get documentation >>updated/added >> to the IoTivity site. > >API docs are the responsibility of the developer adding the public APIs, >so >the technical writer isn't involved here. > >Wiki content is by developers for developers, so I don't think tech >writers >are needed either. > >The tech writer is needed for the release notes and for technical web >content >only. > >-- >Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > >_______________________________________________ >iotivity-dev mailing list >iotivity-dev at lists.iotivity.org >https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5859 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150414/c868c397/attachment.p7s>
