<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2176/25/9/_/styles/combined.css?spaceKey=TOP&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Development">Development</a></h2>
<h4>Page <b>edited</b> by <a href="https://wiki.asterisk.org/wiki/display/~mdavenport">Malcolm Davenport</a>
</h4>
<br/>
<h4>Changes (1)</h4>
<div id="page-diffs">
<table class="diff" cellpadding="0" cellspacing="0">
<tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">h1. An Invitation! <br> <br>Digium invites hard-core code gurus, development wizards, and people who like a challenge and want to be involved with the low-level development of Asterisk SCF, to participate immediately. Over the next several months, many key decisions will continue to be made and APIs will be finalized. Once the APIs have become stable, core-level application developers will benefit directly from the capabilities of Asterisk SCF. Once those core-level application developers have built applications, end users will be able to directly use Asterisk SCF. <br> <br></td></tr>
<tr><td class="diff-unchanged" >h2. Access to Code and Documentation <br> <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
</table>
</div> <h4>Full Content</h4>
<div class="notificationGreySide">
<h2><a name="Development-AccesstoCodeandDocumentation"></a>Access to Code and Documentation </h2>
<p>The central repository for all documentation and project information, including information on downloading the code, tools, whitepapers, roadmap information and more, is this wiki... you are here!</p>
<p>This section of the wiki contains details on how to get "connected" to the community, how to get started with Asterisk SCF development and some helpful tips to make your Asterisk SCF endeavors a success! If you wish to make contributions to the Asterisk SCF repositories, see the <a href="#Development-contribute">section below on the contribution</a> process.</p>
<ul><li><a href="/wiki/display/TOP/Best+Practices" title="Best Practices">Best Practices</a></li><li><a href="/wiki/display/TOP/Tools" title="Tools">Tools</a></li><li><a href="/wiki/display/TOP/Tech+Tips" title="Tech Tips">Tech Tips</a></li><li><a href="/wiki/display/TOP/Asterisk+SCF+Developer+Conference+Call" title="Asterisk SCF Developer Conference Call">Asterisk SCF Developer Conference Call</a></li><li><a href="/wiki/display/TOP/Getting+Started+With+Ice" title="Getting Started With Ice">Getting Started With Ice</a></li><li><a href="/wiki/display/TOP/Project+Ideas+for+Getting+Started+With+Asterisk+SCF" title="Project Ideas for Getting Started With Asterisk SCF">Project Ideas for Getting Started With Asterisk SCF</a></li><li><a href="/wiki/display/TOP/Writing+Asterisk+SCF+Unit+Tests" title="Writing Asterisk SCF Unit Tests">Writing Asterisk SCF Unit Tests</a></li><li><a href="/wiki/display/TOP/Asterisk+SCF+and+CMake+howto" title="Asterisk SCF and CMake howto">Asterisk SCF and CMake howto</a></li><li><a href="/wiki/display/TOP/Supporting+Failover+-+Understanding+What+Ice+is+Doing" title="Supporting Failover - Understanding What Ice is Doing">Supporting Failover - Understanding What Ice is Doing</a></li><li><a href="/wiki/display/TOP/Supporting+Failover+-+Operation+Context+and+Idempotent+Operations" title="Supporting Failover - Operation Context and Idempotent Operations">Supporting Failover - Operation Context and Idempotent Operations</a></li></ul>
<p><a name="Development-contribute"></a>h2. Contributor Process </p>
<p>To contribute new source code or modifications to existing Asterisk SCF source code you must have a <a href="https://issues.asterisk.org/view_license_agreement.php" class="external-link" rel="nofollow">Contributor Agreement</a> on file with Digium. If you have a Contributor Agreement already in place for Asterisk, the same agreement is used for Asterisk SCF so you don't need to submit another one. </p>
<p>Next, you should request a team repo to be created on the <a href="https://myth.asterisk.org/wiki/display/TOP/Source+Repository" class="external-link" rel="nofollow">Asterisk SCF git server</a>. You can do this on Asterisk SCF mailing list referred to above. In your request, make sure you give us the email address used when executing your Contributor Agreement (i.e. the email address on file in Mantis.) </p>
<p>Finally, send us the public portion of your SSH key. We'll register your public key on the git server so that you can create branches in your team repo. All code is migrated by a Digium-assigned engineer from your team repo into the relevant integration repo for review. All reviews are conducted within the integration tree. </p>
<p>Summary: </p>
<ol>
<li>If you don't already have an Asterisk Contributor Agreement in place, execute a new <a href="https://issues.asterisk.org/view_license_agreement.php" class="external-link" rel="nofollow">contributor agreement</a></li>
<li>Request your own team git repo via the mailing list, providing your Mantis email address and public SSH key.</li>
<li>Push your code into your team member branch.</li>
<li>Post a request for review on the mailing list.</li>
</ol>
<h1><a name="Development-DigiumPartners"></a>Digium Partners </h1>
<p>In the short run, the impact to many of Digium’s partners, with the announcement of Asterisk SCF, will be minor. Asterisk SCF will be in heavy development from 2010-2011 and, during this time, will most likely not be suitable for large-scale or carrier-grade deployments. In the long term, we expect Asterisk SCF to provide access to markets that, until now, have been inaccessible or otherwise extremely difficult to service with Asterisk. </p>
<p>Partners with sufficient in-house programming staff are encouraged to begin experimentation with the Asterisk SCF codebase now and to participate in design and development discussions with the Asterisk SCF community at-large. Issues that might arise with your products future use with Asterisk SCF are best uncovered sooner rather than later; we invite your assistance to reduce the number of future problems. </p>
<p>In order to assist partners in their development efforts, Digium provides extensive Asterisk SCF project documentation and information on the online wiki at <a href="https://wiki.asterisk.org" class="external-link" rel="nofollow">https://wiki.asterisk.org</a>. Digium also conducts weekly conference calls to which any interested parties are invited for open discussions about any Asterisk SCF-related topics. </p>
<h1><a name="Development-EndUsers"></a>End Users </h1>
<p>End users building large scale solutions are invited to participate in the ongoing development of Asterisk SCF. Digium recognizes that the success of Asterisk is largely due to the insights and efforts of the thousands who contributed to its development, testing and evangelism. </p>
<p>In the near term, Asterisk SCF will have little impact on the average end user of Asterisk, as the interfaces available will be limited to low-level programming directly against the Asterisk SCF core APIs. Over the course of the next 18 months, we expect to see the addition of high-level interfaces that make Asterisk SCF significantly more accessible. </p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=TOP">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
<a href="https://wiki.asterisk.org/wiki/display/TOP/Development">View Online</a>
|
<a href="https://wiki.asterisk.org/wiki/pages/diffpagesbyversion.action?pageId=131145&revisedVersion=5&originalVersion=4">View Changes</a>
|
<a href="https://wiki.asterisk.org/wiki/display/TOP/Development?showComments=true&showCommentArea=true#addcomment">Add Comment</a>
</div>
</div>
</div>
</div>
</div>
</body>
</html>