From 96f20a285541fa99cc585b046b05562a69512356 Mon Sep 17 00:00:00 2001
From: "Bradley M. Kuhn" <bkuhn@ebb.org>
Date: Thu, 16 Dec 2010 11:06:47 -0500
Subject: [PATCH] Make bullet list of benefits.

---
 .../static/members/apply/index.html           | 66 ++++++++++++-------
 1 file changed, 43 insertions(+), 23 deletions(-)

diff --git a/www/conservancy/static/members/apply/index.html b/www/conservancy/static/members/apply/index.html
index 8282d190..dee01ea6 100644
--- a/www/conservancy/static/members/apply/index.html
+++ b/www/conservancy/static/members/apply/index.html
@@ -31,31 +31,51 @@
 
 <h2>What are the key criteria our project must meet to join?</h2>
 
-<p>In order to join, projects need to meet certain criteria, including the
-requirement that the project be exclusively devoted to the development of
-FLOSS and that it be consistent with the Conservancy's tax-exempt purposes
-and the financial requirements imposed by the IRS.  Most FLOSS projects
-will meet these requirements.</p>
+<p>In order to join, projects need to meet certain criteria.  A rough
+  outline of those criteria are as follows:</p>
+<p>
+<ul><li>The project must be a software development or documentation
+    project.  Non-software projects to advance the cause of software
+    freedom, while important and useful, are beyond the scope of
+    Conservancy.</li>
 
-<p>Additionally, the project must be licensed in a way fitting with
-  software freedom principles.  Specifically, all software of the project
-  should be licensed under a license that is listed both as
-  a <a href="http://www.gnu.org/licenses/license-list.html">Free Software
-  license by the Free Software Foundation</a> and as
-  an <a href="http://www.opensource.org/licenses/alphabetical">Open Source
-  license by the Open Source Initiative</a>.  All software documentation
-  for the project should be licensed under a license on the preceding
-  lists, or under Creative
-  Commons' <a href="http://creativecommons.org/licenses/by-sa/3.0/">CC-By-SA</a>
-  or <a href="http://creativecommons.org/licenses/by/3.0/">CC-By</a> or
-  <a href="http://creativecommons.org/choose/zero/">CC-0</a>.</p>
+    <li>The project must be exclusively devoted to the development and
+    documentation of FLOSS.  The project's goals must be consistent with
+    the Conservancy's tax-exempt purposes, and other requirements imposed
+    on Conservancy by the IRS' 501(c)(3) rules.  Namely, the goal of the
+    project must to develop and document the software in a not-for-profit
+    way to advance the public good, and must develop the software in
+    public.</li>
 
-<p>While any project licensed under FLOSS licenses can apply, the
-  Conservancy seeks in particular projects that are well-established and
-  have some track record of substantial contributions from a community of
-  volunteer developers.  The Conservancy does gives higher priority to
-  projects that have an established userbase and interest, but also tries
-  to accept some smaller projects with strong potential.</p>
+    <li>The project must be licensed in a way fitting with software
+      freedom principles.  Specifically, all software of the project
+      should be licensed under a license that is listed both as
+      a <a href="http://www.gnu.org/licenses/license-list.html">Free
+      Software license by the Free Software Foundation</a> and as
+      an <a href="http://www.opensource.org/licenses/alphabetical">Open
+      Source license by the Open Source Initiative</a>.  All software
+      documentation for the project should be licensed under a license on
+      the preceding lists, or under Creative
+      Commons' <a href="http://creativecommons.org/licenses/by-sa/3.0/">CC-By-SA</a>
+      or <a href="http://creativecommons.org/licenses/by/3.0/">CC-By</a>
+      or
+        <a href="http://creativecommons.org/choose/zero/">CC-0</a>.</li>
+
+   <li>The project should have an existing, vibrant, diverse community
+      that develops and documents the software.  For example, projects
+      that have been under development for less than a year or only a
+      &ldquo;proof of concept&rdquo; implementation are generally not
+      eligible.</li>
+</ul>
+</p>
+
+<p>While any project meeting the criteria above can apply, meeting these
+  criteria don't guarantee acceptance of your project.  The Conservancy
+  favors projects that are well-established and have some track record of
+  substantial contributions from a community of volunteer developers.
+  Furthermore, the Conservancy does gives higher priority to projects that
+  have an established userbase and interest, but also tries to accept some
+  smaller projects with strong potential.</p>
 
 <h2>Is our project required to accept membership if offered?</h2>