<br><div class="gmail_quote">On Fri, Jun 5, 2009 at 10:15 AM, Tilghman Lesher <span dir="ltr"><<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.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;">
<div><div></div><div class="h5">On Thursday 04 June 2009 15:24:40 Dhirendra Pal Singh wrote:<br>
> I am very interested in asterisk and want to help with coding.<br>
><br>
> Now I did look at<br>
> <a href="http://svn.asterisk.org/svn/asterisk/trunk/doc/janitor-projects.txt" target="_blank">http://svn.asterisk.org/svn/asterisk/trunk/doc/janitor-projects.txt</a> and I<br>
> think I can start working on some of them in no particular order.<br>
><br>
> I was wondering if there are some docs to help me jump start my coding<br>
> effort for asterisk. Any pointers? Any body?<br>
><br>
> Since I am a newbie to asterisk development, so please be gentle :)<br>
<br>
</div></div>The main issue that we typically have with patches is a lack of following<br>
the coding guidelines. These are mainly issues with spacing and indentation,<br>
and occasionally with line terminators (people using Windows line terminators<br>
instead of Unix line terminators). The coding guidelines are all located<br>
here:<br>
<a href="http://svn.digium.com/svn/asterisk/trunk/doc/CODING-GUIDELINES" target="_blank">http://svn.digium.com/svn/asterisk/trunk/doc/CODING-GUIDELINES</a><br>
<br>
Once you have a candidate patch, you'll want to upload the patch as a<br>
contribution to <a href="https://issues.asterisk.org" target="_blank">https://issues.asterisk.org</a>. You'll need to sign a<br>
contributor license agreement. It's also best to prefix the subject line<br>
of the issue with "[janitor]", so that we can distinguish your contribution<br>
from a bugfix patch. Additionally, janitor patches should all be against<br>
trunk, unless otherwise specified in the janitor.<br>
<br>
And finally, welcome to the developer community. Many of the developers<br>
hang out in #asterisk-dev on the Freenode IRC network, so if you have a coding<br>
guidelines question, feel free to come ask us there. (Questions on the usage<br>
of Asterisk itself should be asked in #asterisk).<br>
<br>
--<br>
Tilghman</blockquote><div><br> Hi Tilghman,<br>
Thanks for the response. I totally understand the pain of people not following coding guidelines. I have been working as a contractor for last 10 years, and seen a lot of that. <br><br>I have gone through the coding guide lines, couple of times, and probably will go over it couple of more times, in near future :), to make sure that I incorporate it in my code.<br>
<br>Also thanks for clearing that janitor patches should be made against trunk. I was wondering on that. <br><br>Let me try to get my first patch ready and then I can ask for the contributer license. I am currently working on the janitor project "Convert all existing uses of astobj.h to astobj2.h". Hopefully I can have a patch out in next couple of days.<br>
<br>See you on IRC sometime..<br><br>Thanks again for your help..<br>Regards<br>Deep<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Thanks<br>Deep<br><br>