123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 |
- {{+bindTo:partials.standard_nacl_article}}
- <b><font color="#cc0000">
- NOTE:
- Deprecation of the technologies described here has been announced
- for platforms other than ChromeOS.<br/>
- Please visit our
- <a href="/native-client/migration">migration guide</a>
- for details.
- </font></b>
- <hr/><section id="help-with-nacl">
- <h1 id="help-with-nacl">Help with NaCl</h1>
- <p>Check the documentation resources below for help with common issues and
- problems. For additional questions, reach out to the Native Client
- 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>
- <h2 id="documentation">Documentation</h2>
- <ul class="small-gap">
- <li><a class="reference internal" href="/native-client/sdk/release-notes.html"><em>Release Notes</em></a>.</li>
- <li><a class="reference internal" href="/native-client/faq.html"><em>FAQ</em></a>.</li>
- </ul>
- <h2 id="forums">Forums</h2>
- <ul class="small-gap">
- <li>For new Native Client developers: <a class="reference external" href="http://stackoverflow.com/questions/tagged/google-nativeclient">Stack Overflow</a> is a
- great resource — check this forum first for answers to your
- questions.</li>
- <li>For in-depth technical discussions: <a class="reference external" href="https://groups.google.com/group/native-client-discuss">native-client-discuss mailing
- list</a> is a good
- group for detailed technical discussions about bugs and other Native Client
- issues.</li>
- <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>
- <li>For 140 character goodness follow <a class="reference external" href="https://twitter.com/nativeclient">@nativeclient</a> on Twitter.</li>
- </ul>
- <h2 id="issue-tracker"><span id="report-issue"></span>Issue tracker</h2>
- <p>To report a new issue:</p>
- <ol class="arabic simple">
- <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
- 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>
- <li>Before you report an issue, search to see if your issue has already
- been reported. You can add a comment to an existing issue if you have
- additional information.</li>
- <li>To report a new issue, fill out the Summary and Description fields on
- the issue form and click the “Submit issue” button. You can report:<ul class="small-gap">
- <li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Defect%20report">Native Client defect</a>.</li>
- <li>A <a class="reference external" href="https://code.google.com/p/nativeclient/issues/entry?template=Security%20Bug">Native Client security issue</a>
- (only visible to the security team).</li>
- <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>
- <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>
- (only visible to the security team).</li>
- </ul>
- </li>
- </ol>
- </section>
- {{/partials.standard_nacl_article}}
|