list</a>. All of these lists have archives, so you can browse through previous
discussions or follow the list development on the web if you prefer.</p>
-<p>If you're looking for something to work on, check out our <a href="OpenProjects.html">Open Projects</a> page or go look through the <a href="http://llvm.org/bugs/">Bugzilla bug database</a>.</p>
+<p>You can also follow the <a href="http://planet.clang.org/">Planet Clang</a>
+community news feed which offers a window into the world, work and lives of
+Clang developers, contributors and the standards they implement.</p>
+
+<p>If you're looking for something to work on, check out our <a
+href="OpenProjects.html">Open Projects</a> page or look through the <a
+href="http://llvm.org/bugs/">Bugzilla bug database</a>.</p>
<h2 id="criteria">Contributing Extensions to Clang</h2>
<ul>
<li>Modular library based architecture</li>
<li>Support diverse clients (refactoring, static analysis, code generation,
- etc)</li>
+ etc.)</li>
<li>Allow tight integration with IDEs</li>
<li>Use the LLVM 'BSD' License</li>
</ul>
<h2>Why?</h2>
<!--=====================================================================-->
- <p>The development of a new front-end was started out of a need -- a need
+ <p>Development of the new front-end was started out of a need
for a compiler that allows better diagnostics, better integration with
IDEs, a license that is compatible with commercial products, and a
nimble compiler that is easy to develop and maintain. All of these were
<h2>Current Status</h2>
<!--=====================================================================-->
- <p>Clang is still under heavy development. Clang is considered to
+ <p>Clang is considered to
be a production quality C, Objective-C, C++ and Objective-C++ compiler when
targeting X86-32, X86-64, and ARM (other targets may have caveats, but are
usually easy to fix). If you are looking for source analysis or