Thanks to all of you for your support. Let me prepare first batch of files for SVN commit and get back to you.<br><br>Thank you.<br><br><br><div class="gmail_quote">On Mon, Sep 21, 2009 at 11:56 PM, Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org">msc@freeswitch.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div class="im">On Mon, Sep 21, 2009 at 10:02 AM, Muhammad Shahzad <span dir="ltr"><<a href="mailto:shaheryarkh@googlemail.com" target="_blank">shaheryarkh@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sure, i fully understand this role and its responsibilities. I will take special care for SVN commit process.<br><br>Anyways, here is a rough plan for the project. I hope this ensures code integrity at all levels.<br><br>
1. Doxygen configuration files and directories setup.<br>
2. Then we will do header files documentation folder by folder, starting from inner most include directory (<FSROOT>/src/include/private) and then moving outwards.<br>3. Once one whole include folder is documented, we will first put it in our test environment and rebuild FS from scretch (i.e. after doing a distclean).<br>
4. One of my team member has promised me to provide a script that will run on each header file to produce a clean file (i.e. without any comments etc.). We will run it on both original (undocumented) and modified (documented) files and then do a diff on their output. If diff yeilds nothing then both documented and undocumented files are identical (code wise).<br>
5. When all files in a single folder pass this script test, I will commit it to SVN (alternatively i can forward them to you guys for review and then you can commit it to SVN).<br>6. Once all header files are done, we then do source code files repeating steps 3 - 5 for each folder in top most to inner most direction.<br>
<br>I haven't finalized resource allocation and time lines yet. However, the documentation will be mostly done by project members while i will do steps 3-5 personally.<br><br>Please review and give your feedback.<br>
<br>
Thank you.<br><br></blockquote></div><div><br>Thanks for being so thorough! If you complete this level of testing and don't have any build/compile issues then that's a pretty good indication that your methodology is adequate. Like Tony said, we can probably skip the review process, or maybe we could review the first few submissions just to be safe and then turn you guys loose. :)<br>
<br>Thanks for your willingness to help! The entire community will benefit.<br>-MC<br><br></div></div>
<br>_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Muhammad Shahzad<br>-----------------------------------<br>CISCO Rich Media Communication Specialist (CRMCS)<br>CISCO Certified Network Associate (CCNA)<br>Cell: +92 334 422 40 88<br>
MSN: <a href="mailto:shari_786pk@hotmail.com">shari_786pk@hotmail.com</a><br>Email: <a href="mailto:shaheryarkh@googlemail.com">shaheryarkh@googlemail.com</a><br>