{% extends "base_members.html" %}
{% block subtitle %}Member Project Services - {% endblock %}
{% block submenuselection %}Applying{% endblock %}
{% block content %}
<h1> Applying to Join Conservancy as a Member Project</h1>
<p>New applications for project membership with Conservancy are considered
twice a year. The deadlines for submission of application materials are
1 February and 1 September each year.</p>
<p>Conservancy's Evaluation Committee considers applications monthly on a
rolling basis.</p>
<p>The application process is somewhat informal. New applicants should
write
write an initial inquiry email
to <a href="mailto:apply@sfconservancy.org"><apply@sfconservancy.org></a>
with a very brief description of their project and a URL to their
project's website. We'll send back initial questions if we have any,
and after that, we'll send the full application materials. Applications
should be submitted in plain ASCII text via email.</p>
<p>Projects are reviewed by Conservancy's Evaluation Subcommittee (which
is a subcommittee of Conservacy's Directors), and the subcommittee's
recommendations are submitted to
Conservancy's <a href="/about/board/">Board of Directors</a>, who make
the final decision to offer membership.</p>
project's website. We'll send back initial questions (if any), and
after those questions are answered, we'll send the full application
materials. Applications should be submitted in plain ASCII text via
email.</p>
<p>Projects are reviewed by Conservancy's Evaluation Committee, which is
chartered by Conservancy's <a href="/about/board/">Board of
Directors</a>.</p>
<h1>Project Membership Application FAQs</h1>
<p>The following are various questions that we typically get from project
leaders that wish to apply to Conservancy.</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>
<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
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>
<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
“proof of concept” implementation are generally not
eligible.</li>
</ul>
</p>
<p>While any project meeting the criteria above can apply, meeting these