Hi, A new getting started guide would be very nice. When doing so could someone also describe some demo scenarios like you have to start this application and then this and now they can send messages to each other using this part of the specification. I am lost in all these binaries that are getting build in the IoTivity build and some description for some demo scenarios would be very nice. So not just describing how it should theoretically work, but also give some examples on how to actually do it, so it can be understood better. I like to sniff such demo with wireshark to better understand what happens there. You should not require some extra hardware for it, but a extra description on how to use IoTivity with e.g. BLE would also be nice.
Why not replace the complete documentation with a link to some wiki pages or integrate the wiki pages into the website? I do not think that we will get lots of problems with some people adding bad content, only spam would be a problem. When everyone is able to edit the documentation it will be easier to make them stay up to date, otherwise you probably have to create some management to solve the documentation problem which is probably much more complicated. Why do I have to login to see gerrit? Hauke -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of RAVI NANJUNDAPPA Sent: Freitag, 26. Juni 2015 07:03 To: Morrow, Joseph L; Macieira, Thiago Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity 'Getting-Started' Guides hi Joey, I was one among the victims who tried to follow up the documentation available at iotvity.org and got confused with the source code. So, can we have some quick links that talks about different categories like the ones below : ? Roadmap - Features planned for upcoming release (for ex: like 1.0.0) Todo - Other new ideas ( which are not yet on the Roadmap) Samples - Some samples of how to use Cairo and any other Presentation or PDF files that might be of use to the community. These details help the newbies who are willing to contribute and explore about iotivity. HTH. Thanks and Best Regards, N Ravi ------- Original Message ------- Sender : Morrow, Joseph L<joseph.l.morrow at intel.com> Date : Jun 26, 2015 03:30 (GMT+05:30) Title : Re: [dev] IoTivity 'Getting-Started' Guides Hi Thiago, It may behoove us to make sub-pages in those two reference columns (https://www.iotivity.org/documentation & https://www.iotivity.org/get-involved) for each release. We can place the current stuff that is located there now under some X release version link (whatever/however we referred to the version that is currently document at those two links). Then we can take snapshots of the Wiki with its respective release and place that documentation above the aforemention "X release version" above. This may be the easiest, and least amount of compromise by all. Thanks, Joey -----Original Message----- From: Macieira, Thiago Sent: Thursday, June 25, 2015 5:54 PM To: Morrow, Joseph L Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity 'Getting-Started' Guides On Thursday 25 June 2015 14:46:32 Morrow, Joseph L wrote: > Hi Thiago, > > I would **like** to see the website redesigned so that community can > grow and change as it needs by singularly using the Wiki. Once a major > release (ie. "1.0.0") is made, it may behoove us to document these > things on the main page. However, until then, any work up to that > point should likely only exist on the Wiki. Hi Joey I agree with what you said. We can treat the wiki as a place to draft content for the main website. > With this website locked down and not necessarily matching what the > wiki has up, this makes the IoTivity project look seriously > disorganized. This may also create issues for end users who put time > into practicing the wrong documentation. It's a real scenario where an > end user may simply walk away from IoTivity due to frustration. All > contribution work (including all steps up to actually contributing) > can change & will change. This model where any developer who make a > slight change must contact one of a handful of people to broadcast > their changes is not scalable, and isn't even working currently. > > Please re-consider the avoidance of re-designing. Perhaps we can add a > new column "Wiki" and we can provide some quick links that people whom > are absolutely brand new should look at first. Also, as said above, > any concrete documentation for a major release could certainly exist > on the main page of Iotivity. I don't have the technical skills to redesign. I can at most edit text that is on the main website. In any case, those pages don't actually contain content. They only contain links to other pages. I can easily change the links to point to the wiki. -- 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 _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
