NaCl docs: add project ideas

native_client_sdk/src/doc/faq.rst

 ##########################
 Frequently Asked Questions
 ##########################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 This document answers some frequently asked questions about Native
@@ skipping 183 matching lines @@
 Native Client is completely open: the executable format is open and the
 `source code is open <https://code.google.com/p/nativeclient/>`_. Right
 now the Native Client project is in its early stages, so it's premature
 to consider Native Client for standardization.
 
 We consistenly try to document our design and implementation and hope to
 standardize Portable Native Client when it gains more traction. A good
 example is our :doc:`PNaCl bitcode reference manual
 <reference/pnacl-bitcode-abi>`.
 
+How can I contribute to Native Client?
+--------------------------------------
+
+Read about :doc:`contributor ideas <ideas>`.
+
 What are the supported instruction set architectures?
 -----------------------------------------------------
 
 Portable Native Client uses an architecture-independent format (the
 ``.pexe``) which can currently be translated to execute on processors
 with the x86-32, x86-64, and ARM instruction set architectures, as well
 as experimental support for MIPS. As new architectures come along and
 become popular we expect Portable Native Client to support them without
 developers having to recompile their code.
 
@@ skipping 20 matching lines @@
 as well as to compile more languages to LLVM's intermediate representation
 (e.g. support Halide_, Haskell with GHC_ or support Fortran with flang_), or
 transpile languages to C/C++ (source-to-source compilation). Even JavaScript is
 supported by compiling V8_ to target PNaCl.
 
 The PNaCl toolchain is built on LLVM and can therefore generate code from
 languages such as Rust_, Go_, or Objective-C, but there may still be a few rough
 edges.
 
 If you're interested in getting other languages working, please contact the
-Native Client team by way of the native-client-discuss_ mailing list.
+Native Client team by way of the native-client-discuss_ mailing list, and read
+through :doc:`contributor ideas <ideas>`.
 
 Do you only support Chrome? What about other browsers?
 ------------------------------------------------------
 
 We aim to support multiple browsers. However, a number of features that
 we consider requirements for a production-quality system that keeps the
 user safe are difficult to implement without help from the
 browser. Specific examples are an out-of-process plugin architecture and
 appropriate interfaces for integrated 3D graphics. We have worked
 closely with Chromium developers to deliver these features and we are
@@ skipping 188 matching lines @@
 proxying OS functionality or emulating UNIX system calls. For example,
 Native Client provides an ``mmap()`` system call that behaves much like
 the standard UNIX ``mmap()`` system call.
 
 Is my favorite third-party library available for Native Client?
 ---------------------------------------------------------------
 
 Google has ported several third-party libraries to Native Client; such libraries
 are available in the naclports_ project. We encourage you to contribute
 libraries to naclports, and/or to host your own ported libraries, and to let the
-team know about it on native-client-discuss_ when you do.
+team know about it on native-client-discuss_ when you do. You can also read
+through :doc:`contributor ideas <ideas>` to find ideas of new projects to port.
 
 Do all the files in an application need to be served from the same domain?
 --------------------------------------------------------------------------
 
 The ``.nmf``, and ``.nexe`` or ``.pexe`` files must either be served from the
 same origin as the embedding page or an origin that has been configured
 correctly using CORS_.
 
 For applications installed from the Chrome Web Store the Web Store manifest
 must include the correct, verified domain of the embedding page.
@@ skipping 123 matching lines @@
 .. _Rust: http://www.rust-lang.org/
 .. _Go: https://golang.org
 .. _native-client-discuss: https://groups.google.com/group/native-client-discuss
 .. _deprecated in Chrome: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
 .. _OpenGL ES 2.0: https://www.khronos.org/opengles/
 .. _GLES2 file: https://code.google.com/p/chromium/codesearch#chromium/src/ppapi/lib/gl/gles2/gles2.c
 .. _Google Chrome privacy policy: https://www.google.com/chrome/intl/en/privacy.html
 .. _Google Chrome Terms of Service: https://www.google.com/chrome/intl/en/eula_text.html
 .. _naclports: https://code.google.com/p/naclports
 .. _CORS: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing