Hi Margaret, It's fairly easy to notice the issues on the API surface, but in the other hand this represents a huge engineering challenge and needs more specification to be tackled. I am not directly involved with the framework development, therefore I don't find myself able to take such responsibility. I'd rather team up with other volunteers and be mentored by one or more experts on this area (especially on the Java side)
Moreover, Instead of a table I'd suggest you to share a document we can specify each scope more precisely for all contribution areas. Lastly, I think it would be nice to outsource some areas (e.g sample apps) to students via the Google Summer of Code program ( https://summerofcode.withgoogle.com/). I also follow the Vert.x project and the results they obtained from last year edition has helped a lot the community. (http://vertx.io/gsoc/). regards, On Wed, May 3, 2017 at 5:27 PM, Nash, George <george.nash at intel.com> wrote: > Mats, > > You are 100% correct. The doxygen is by far the easy part. I hope as a > mentor, I can help smooth out some of the struggles a developer will have > if they want to make improvements. In truth I am not 100% sure that I am > the perfect person for the things I have volunteered to be a mentor for. > > I have had a fair amount of success getting changes committed in the areas > I have volunteered to help with. Some of that success is probably due to > having an email associated with one of the major member companies. Some of > the success is that I do things a little at a time. I almost never make a > giant change. Maintainers like small changes they can understand quickly. > We have had some amazingly good commits for build changes but they were > huge changes that stalled mostly due to the size of the change. No one > wants to be the maintainer that approved a change that inadvertently caused > a huge number of problems. > > This is all new. I don't really know how much of a work load I have signed > myself up for. I hope it is not too much. If I see things a lot I will > update the wiki so I can point people there. > > George > > -----Original Message----- > From: Mats Wichmann [mailto:mats at wichmann.us] > Sent: Wednesday, May 3, 2017 12:54 PM > To: Nash, George <george.nash at intel.com>; LaBrecque, Margaret < > margaret.labrecque at intel.com>; iotivity-dev at lists.iotivity.org > Subject: Re: [dev] prelim list of areas where IoTivity needs new > contributors > > On 05/03/2017 01:17 PM, Nash, George wrote: > > Margaret, > > > > I split the documentation into two sections API documentation and Wiki > documentation. I am prepared to be a mentor for API related documentation > but I am not prepared to do the same for wiki related changes. > > > > If someone feels they would be willing to mentor with wiki related > changes please feel free to volunteer. > > > > To clarify if you are volunteering to be a mentor. You will help new or > experienced developers/volunteers to get involved with IoTivity if they > want to try and help in the area of interest. We can have multiple mentors > for a single section. If you feel you know enough about using Doxygen you > could add yourself as an additional Mentor for the Documentation API. > > > FWIW, Doxygen is by far the Easy Part of this task. For those who are > going to work on the API docs, understanding the API and its interaction > with other APIs is key (in the sense that good docs will have > cross-references, deprecation warnings will point to alternatives, etc.), > as is figuring out what is really part of public apis and what is just > documented but internal apis, how all the headers get included and thus > interact with each other, and how to get changes merged when the > maintainers of the affected areas who have to act on your gerrit requests > are utterly slammed with things they see as much higher > priority (usually rightly so). How you mentor the last part I'm not > sure <speak="from experience"> but without some movement on the patch flow > thing, it gets pretty frustrating pretty quickly </speak> > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- *Thiago Guedes Cunha de Moura* Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170505/3c524ff8/attachment.html>
