src/native_client_sdk/doc_generated/help.html

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