I prefer proposal 2. They are whole IoTivity APIs. But, I think C and C++ API documentation need to be separated.
BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Junmo Yang Sent: Tuesday, March 31, 2015 2:31 PM To: Kourt, Tim A; Lankswert, Patrick; ???; isg at lists.iotivity.org; Shaver, Michael R; Bowden, George; ??? Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] API Doc on Website Dear All, This is Junmo Yang, who is working with June for Release Management. I have 2 Questions releated to below. 1. Anyone can share configuration files for Javadoc? - For consistency, we may need same configuration files like as doxygen. 2. Any suggestion for API document structure in IoTivity Web Site? - Proposal 1: Two Separate API Documents for Base & Primitive Service (Shoud be separte C/C++ & Java) ex) - Base API (C/C++) - Base API (Java) - Primitive Service (C/C++) - Primitive Servvice (Java) - Proposal 2: Intergated API Documents ex) - API for C/C++ - API for Java Please share your idea or resource. BR, - Junmo Yang ------- Original Message ------- Sender : Kourt, Tim A<tim.a.kourt at intel.com> Date : 2015-03-31 03:19 (GMT+09:00) Title : RE: [dev] API Doc on Website June, The Android API is currently annotated for the Javadoc tool. Thanks, Tim From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Lankswert, Patrick Sent: Monday, March 30, 2015 8:35 AM To: juney at samsung.com; ???; isg at lists.iotivity.org; Shaver, Michael R; Bowden, George; ??? Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] API Doc on Website June, Javadoc is more appropriate for Java. Pat From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of JuneYong Young Sent: Sunday, March 29, 2015 9:33 PM To: JuneYong Young; ???; isg at lists.iotivity.org; Shaver, Michael R; Bowden, George; ??? Cc: iotivity-dev at lists.iotivity.org Subject: [dev] API Doc on Website Hi Mike, George, If you look at API Docs in IoTivity Website, you can find there Primitive API parts are missing when 0.9.0 was released. I have two questions. - Doxygen file was generated as a whole from the source codes, but why was Primitive service part missing? Are there some specific fields should exist in the source code, makefiles, or etc? We need to find out why in order to be well prepared for 0.9.1. - JAVA API document also is required now. I think Doxygen is also ok for JAVA API, any opinion? Regards June June Yong Young Principal Engineer IoT Solution Lab. | Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com ------- Original Message ------- Sender : JuneYong Young<juney at samsung.com> S6/Principal Engineer/IoT Solution Lab./Samsung Electronics Date : 2015-03-30 09:56 (GMT+09:00) Title : [dev] Branching Policy for DEV branch Dear All, The attached is the material presented in last OIC F2F meeting. It included Branching Policy announcement indicating DEV branch should be created & maintained for the new feature to be deployed. Still a lot of development is going on on Master branch, but it will have to be applied on new DEV branch to created after 0.9.1 release on 4/24. If any concerns, please let us all know. Regards June http://www.samsung.net/service/ml/AttachController/image001.gif?cmd=downdirectly&filepath=/LOCAL/ML/CACHE/j/20150331/image001.gif at 01D06AC8.52A0D5A0788junmo2.yang&contentType=IMAGE/GIF;charset=UTF8&msgno=788&partno=2&foldername=INBOX&msguid=66604 June Yong Young Principal Engineer IoT Solution Lab. | Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com ??? (Junmo Yang, Ph. D) Principal Engineer IoT Solution Lab./Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. Mobile: +82-10-7260-7032 E-mail: junmo2.yang at samsung.com <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=969de3e7d398516ea49e250801ff1573a1bdf72b82acd06d2ddbb306ad6a22d54e60fcf6aeb61df594c3b6ddffd7613bcb238d00164b0be48eeb9bec5ad9c75d326bbdfb2ea96a2fcf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150331/82117096/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 66181 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150331/82117096/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 75784 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150331/82117096/attachment-0001.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 13168 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150331/82117096/attachment-0002.gif>
