Changeset - 0e54fb764ed9
[Not reviewed]
0 1 0
Brett Smith (brett) - 6 years ago 2018-09-18 13:46:45
brett@sfconservancy.org
apply: Remove outdated "must be a software project" criteria.
1 file changed with 1 insertions and 6 deletions:
0 comments (0 inline, 0 general)
www/conservancy/static/projects/apply/index.html
Show inline comments
...
 
@@ -27,54 +27,49 @@
 
<p>The following are various questions that we typically get from project
 
  leaders that wish to apply to Conservancy.</p>
 

	
 

	
 
<h2>I sent in my inquiry letter and/or application a long time ago.  Why haven't you replied?</h2>
 

	
 
<p>Conservancy receives an overwhelming level of interest and we have very few
 
  <a href="/about/staff/">staff positions</a> to
 
  meet the interest and demand
 
  for <a href="/members/services/">Conservancy's
 
  services</a> to its member projects.  Meanwhile, Conservancy always
 
  prioritizes needs of
 
  its <a href="/members/current/">existing member
 
  projects</a> over new inquiries and applications.  Therefore, it
 
  sometimes can take quite a while to finish the application process and
 
  be offered membership, but please note that such delays mean that should
 
  your project ultimately become a member project, your project will then
 
  be a beneficiary of this policy.</p>
 

	
 
<h2>What are the key criteria our project must meet to join?</h2>
 

	
 
<p>In order to join, projects need to meet certain criteria.  A rough
 
  outline of those criteria are as follows:</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>
 

	
 
    <li>The project must be exclusively devoted to the development and
 
<ul><li>The project must be exclusively devoted to the development and
 
    documentation of FLOSS.  The project's goals must be consistent with
 
    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>
 

	
 
    <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="https://creativecommons.org/licenses/by-sa/3.0/">CC-By-SA</a>
 
      or <a href="https://creativecommons.org/licenses/by/3.0/">CC-By</a>
 
      or
 
        <a href="https://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
0 comments (0 inline, 0 general)