help.html 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. {{+bindTo:partials.standard_nacl_article}}
  2. <b><font color="#cc0000">
  3. NOTE:
  4. Deprecation of the technologies described here has been announced
  5. for platforms other than ChromeOS.<br/>
  6. Please visit our
  7. <a href="/native-client/migration">migration guide</a>
  8. for details.
  9. </font></b>
  10. <hr/><section id="help-with-nacl">
  11. <h1 id="help-with-nacl">Help with NaCl</h1>
  12. <p>Check the documentation resources below for help with common issues and
  13. problems. For additional questions, reach out to the Native Client
  14. 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>
  15. <h2 id="documentation">Documentation</h2>
  16. <ul class="small-gap">
  17. <li><a class="reference internal" href="/native-client/sdk/release-notes.html"><em>Release Notes</em></a>.</li>
  18. <li><a class="reference internal" href="/native-client/faq.html"><em>FAQ</em></a>.</li>
  19. </ul>
  20. <h2 id="forums">Forums</h2>
  21. <ul class="small-gap">
  22. <li>For new Native Client developers: <a class="reference external" href="http://stackoverflow.com/questions/tagged/google-nativeclient">Stack Overflow</a> is a
  23. great resource &#8212; check this forum first for answers to your
  24. questions.</li>
  25. <li>For in-depth technical discussions: <a class="reference external" href="https://groups.google.com/group/native-client-discuss">native-client-discuss mailing
  26. list</a> is a good
  27. group for detailed technical discussions about bugs and other Native Client
  28. issues.</li>
  29. <li>For announcements, follow the <a class="reference external" href="http://groups.google.com/group/native-client-announce">native-client-announce mailing list</a>.</li>
  30. <li>For 140 character goodness follow <a class="reference external" href="https://twitter.com/nativeclient">&#64;nativeclient</a> on Twitter.</li>
  31. </ul>
  32. <h2 id="issue-tracker"><span id="report-issue"></span>Issue tracker</h2>
  33. <p>To report a new issue:</p>
  34. <ol class="arabic simple">
  35. <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
  36. 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>
  37. <li>Before you report an issue, search to see if your issue has already
  38. been reported. You can add a comment to an existing issue if you have
  39. additional information.</li>
  40. <li>To report a new issue, fill out the Summary and Description fields on
  41. the issue form and click the &#8220;Submit issue&#8221; button. You can report:<ul class="small-gap">
  42. <li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Defect%20report">Native Client defect</a>.</li>
  43. <li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Security%20Bug">Native Client security issue</a>
  44. (only visible to the security team).</li>
  45. <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>
  46. <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>
  47. (only visible to the security team).</li>
  48. </ul>
  49. </li>
  50. </ol>
  51. </section>
  52. {{/partials.standard_nacl_article}}