A quick tour: https://www.iotivity.org/get-involved
Lists things out including getting an account and submitting patches. https://www.iotivity.org/get-involved/contribution-guidelines Then there are the coding guidelines https://wiki.iotivity.org/iotivity_c_coding_standards Perhaps the trickiest aspect is getting the whitespace correct :-) Spaces, not tabs, and watch out for trailing whitespace. View Whitespace can help http://blogs.msdn.com/b/zainnab/archive/2010/04/09/view-white-space-vstipedit0043.aspx On 09/17/2015 04:34 PM, Mohammed Javid via iotivity-dev wrote: > I have not registered with the Gerrit. I directly downloaded the zipped > source code from the site. I don't what the process is. Besides, I need to > refactor the code that I added as I have done the modifications in a very > short time to see if we can use the stack for a bigger project we are > planning. Please let me know the process. > Thanks,Javid > > > On Thursday, September 17, 2015 4:19 PM, Thiago Macieira > <thiago.macieira at intel.com> wrote: > > > On Thursday 17 September 2015 22:44:41 Mohammed Javid wrote: >> I have already ported the c resource sdk to work with Visual Studio 2015. >> Currently, I am not using the scons, but instead have created visual studio >> projects for the same. I can run the sample ocserver and occlient >> successfully. > > Hello Mohammed > > (I've just noticed I was addressing you as Jawid; sorry, I mistook you for a > colleague with that name) > > That's great news! > > Can you send your modifications for review into Gerrit? > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com
