.. _help: ############## Help with NaCl ############## 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 :ref:`report new issues ` using the Native Client issue tracker. Documentation ============= * :doc:`Release Notes `. * :doc:`FAQ `. * `Talks, Demos, and Publications `_ (see especially Colt McAnlis' talk on porting C++ games to Native Client). .. TODO: Fix the talk link once ReST-ified. Forums ====== * For new Native Client developers: `Stack Overflow `_ is a great resource --- check this forum first for answers to your questions. * For in-depth technical discussions: `native-client-discuss mailing list `_ is a good group for detailed technical discussions about bugs and other Native Client issues. * For announcements, follow the `native-client-announce mailing list `_. * For 140 character goodness follow `@nativeclient `_ on Twitter. .. _report_issue: Issue tracker ============= To report a new issue: #. Go to the `Native Client issue tracker `_ for a Native Client bug, or the `Chromium issue tracker `_ for a Chrome/Chromium bug. #. 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. #. 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: * A `Native Client defect `_. * A `Native Client security issue `_ (only visible to the security team). * A `Native Client + Chrome integration issue `_. * A `Native Client + Chrome integration security issue `_ (only visible to the security team).