Modified: trunk/htdocs/doc/manual/habari.html (3890 => 3891)
--- trunk/htdocs/doc/manual/habari.html 2009-12-16 01:52:16 UTC (rev 3890)
+++ trunk/htdocs/doc/manual/habari.html 2009-12-16 01:58:05 UTC (rev 3891)
@@ -31,7 +31,7 @@
<p>Those are just a few of the technical differences, but a major component of what makes Habari different is its community participation model. Users who demonstrate a consistent level of quality contributions to the project are granted more privileges within the project.</p>
<h2>Our Process</h2>
<h3>Meritocracy</h3>
- <p>Following the <a href="http://www.apache.org/foundation/how-it-works.html#meritocracy/" title="External link to http://www.apache.org/foundation/how-it-works.html#meritocracy/" target="_blank">meritocracy</a> model advocated by the Apache Software Foundation, the Habari project rewards contributors with decision making privilege in the project. Regular participants should be able to influence the direction of the project to which they dedicate their time and talent. The requirement for participation will be something of a moving target over time, but the barrier to entry should never be so high that dedicated people are excluded.</p>
+ <p>Following the <a href="http://www.apache.org/foundation/how-it-works.html#meritocracy" title="External link to http://www.apache.org/foundation/how-it-works.html#meritocracy" target="_blank">meritocracy</a> model advocated by the Apache Software Foundation, the Habari project rewards contributors with decision making privilege in the project. Regular participants should be able to influence the direction of the project to which they dedicate their time and talent. The requirement for participation will be something of a moving target over time, but the barrier to entry should never be so high that dedicated people are excluded.</p>
<h3>Transparency</h3>
<p>A fundamental aspect of successful open source projects is transparency. Decisions are made in the public's eye, and discussion and deliberation takes place in the open. The Habari project pursues transparency by using the Google issues tracker to maintain a record of proposed changes, and discussion associated with those changes. All proposals -- whether for code, documentation, visual style, etc -- are logged through the issues tracker for public scrutiny and input.</p>
<h3>Licensing</h3>