1{{+bindTo:partials.standard_nacl_article}} 2 3<section id="help-with-nacl"> 4<span id="help"></span><h1 id="help-with-nacl"><span id="help"></span>Help with NaCl</h1> 5<p>Check the documentation resources below for help with common issues and 6problems. For additional questions, reach out to the Native Client 7community in the forums below. You can also <a class="reference internal" href="#report-issue"><em>report new issues</em></a> using the Native Client issue tracker.</p> 8<section id="documentation"> 9<h2 id="documentation">Documentation</h2> 10<ul class="small-gap"> 11<li><a class="reference internal" href="/native-client/sdk/release-notes.html"><em>Release Notes</em></a>.</li> 12<li><a class="reference internal" href="/native-client/faq.html"><em>FAQ</em></a>.</li> 13<li><a class="reference external" href="https://devsite.googleplex.com/native-client/community/talks">Talks, Demos, and Publications</a> (see 14especially Colt McAnlis’ talk on porting C++ games to Native Client).</li> 15</ul> 16</section><section id="forums"> 17<h2 id="forums">Forums</h2> 18<ul class="small-gap"> 19<li>For new Native Client developers: <a class="reference external" href="http://stackoverflow.com/questions/tagged/google-nativeclient">Stack Overflow</a> is a 20great resource — check this forum first for answers to your 21questions.</li> 22<li>For in-depth technical discussions: <a class="reference external" href="https://groups.google.com/group/native-client-discuss">native-client-discuss mailing 23list</a> is a good 24group for detailed technical discussions about bugs and other Native Client 25issues. * For announcements, follow the <a class="reference external" href="http://groups.google.com/group/native-client-announce">native-client-announce mailing list</a>.</li> 26<li>For 140 character goodness follow <a class="reference external" href="https://twitter.com/nativeclient">@nativeclient</a> on Twitter.</li> 27</ul> 28</section><section id="issue-tracker"> 29<span id="report-issue"></span><h2 id="issue-tracker"><span id="report-issue"></span>Issue tracker</h2> 30<p>To report a new issue:</p> 31<ol class="arabic simple"> 32<li>Go to the <a class="reference external" href="https://code.google.com/p/nativeclient/issues">Native Client issue tracker</a> for a Native Client 33bug, or the <a class="reference external" href="https://code.google.com/p/chromium/issues">Chromium issue tracker</a> for a Chrome/Chromium bug.</li> 34<li>Before you report an issue, search to see if your issue has already 35been reported. You can add a comment to an existing issue if you have 36additional information.</li> 37<li>To report a new issue, fill out the Summary and Description fields on 38the issue form and click the “Submit issue” button. You can report:<ul class="small-gap"> 39<li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Defect%20report">Native Client defect</a>.</li> 40<li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Security%20Bug">Native Client security issue</a> 41(only visible to the security team).</li> 42<li>A <a class="reference external" href="https://code.google.com/p/chromium/issues/entry?template=NaCl%20Issue">Native Client + Chrome integration issue</a>.</li> 43<li>A <a class="reference external" href="https://code.google.com/p/chromium/issues/entry?template=Security%20Bug">Native Client + Chrome integration security issue</a> 44(only visible to the security team).</li> 45</ul> 46</li> 47</ol> 48</section></section> 49 50{{/partials.standard_nacl_article}} 51