Changeset - 5b481410704b
[Not reviewed]
0 7 0
Bradley Kuhn (bkuhn) - 12 years ago 2010-10-04 01:44:32
bkuhn@ebb.org
Various formatting and typo fixes.
7 files changed with 15 insertions and 12 deletions:
0 comments (0 inline, 0 general)
www/conservancy/static/conservancy.css
Show inline comments
...
 
@@ -186,58 +186,58 @@ span.continued {
 
}
 

	
 
p.date {
 
  font-style: italic;
 
  font-size: .83em;
 
  margin-bottom: .3em;
 
  margin-top: .3em;
 
}
 

	
 
a.feedlink /* RSS icon */ { display: block; float: right; font-size: 10pt; }
 

	
 
blockquote, div.quote /* div.quote is used by conservancy whitepaper */ {
 
  margin-left: 2em;
 
  margin-right: 2em;
 
  padding-left: 1em;
 
  padding-right: 1em;
 
  border: 1px solid #fff;
 
  background: #eee;
 
}
 

	
 
.newsgraphic { float: right; }
 
.newsgraphic img { border: 1px solid #000; }
 

	
 
.secondary_info { font-size: 83%; }
 
.next_page_button { float: right; }
 
.document_format { border: 1px solid #888; padding: .2em; background: #fff99d;}
 
.copyright_info { font-size: 90%; }
 
hr.footnote-separator { width: 80%; margin-left: auto; margin-right: auto; }
 

	
 
/* Resources pages */
 
div.download-formats { margin-top: 2em; margin-bottom: 2em; }
 
.download-formats p { display: inline; }
 
#mainContent .download-formats ul { display: inline; list-style: none;
 
                                    padding-left: 0; }
 
.download-formats ul li { display: inline; padding-left: 2em; }
 

	
 
/* Resources - book styles */
 
hr.chapter-separator { display: none; }
 
h2.likechapterHead { text-align: center; }
 
h2.chapterHead { text-align: center; }
 
#mainContent ul.author { list-style-type: none; padding-left: 0; }
 
#mainContent div.footnotes { font-style: normal; } /* remove italics */
 
span.sectionToc { padding-left: 2em; } /* indent TOC properly */
 
span.subsectionToc { padding-left: 4em; }
 
span.subsubsectionToc { padding-left: 6em;}
 
.js, .js p, .js p.bibitem, .js p.bibitem-p { background-color: #cde7e9; }
 

	
 
body.conservancy-overview #navbar ul li.overview a,
 
body.conservancy-members #navbar ul li.members a,
 
body.conservancy-Members #navbar ul li.Members a,
 
body.conservancy-news #navbar ul li.news a,
 
body.conservancy-blog #navbar ul li.blog a,
 
body.conservancy-About #navbar ul li.About a,
 
body.conservancy-officers #navbar ul li.officers a,
 
body.conservancy-contact #navbar ul li.contact a,
 
body.conservancy-donate #navbar ul li.donate a /* NO COMMA HERE! */
 
{ 
 
    font-weight: bold;
 
    background: #fff url(/img/nav-bg-up.png) top repeat-x; color: #000; }
www/conservancy/static/members/apply/index.html
Show inline comments
 
{% extends "base_members.html" %}
 
{% block subtitle %}Member Project Services - {% endblock %}
 
{% block category %}members{% endblock %}
 
{% block submenuselection %}Services{% endblock %}
 
{% block submenuselection %}Applying{% endblock %}
 
{% block content %}
 

	
 
<h1>How To Apply to Become 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>The application process is somewhat informal.  New applicants should
 
  write
 
  to <a href="mailto:apply@sfconservancy.org">&lt;apply@sfconservancy.org&gt;</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>
 

	
 
<h1>Project Membership Application FAQs</h1>
 

	
 
<p><b>What are the key criteria our project must meet to join?</b></p>
 
<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, 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>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>
 

	
 
<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>
 

	
 
<h2>Is our project required to accept membership if offered?</h2>
 

	
 
<p>Not at all.  Many projects apply and subsequently decide not to join a
 
  non-profit, or decide to join a different non-profit entity.  Don't
 
  worry about &ldquo;wasting our time&rdquo; if your project's developers
 
  aren't completely sure yet if they want to join conservancy.  If
 
  membership in Conservancy is currently a legitimate consideration for
 
  your project, we encourage you to apply.  We'd rather that you apply and
 
  turn down an offer for membership than fail to apply and have to wait
 
  until the next application round when you're sure.</p>
 

	
 
<h2>What will the project leaders have to agree to if our project joins?</h2>
 

	
 
<p>Once you're offered membership, we'll send you a draft fiscal
 
  sponsorship agreement.  These aren't secret documents and many of our
 
  memer projects have even chosen to put theirs online.  However, we wait
 
  to send a draft of this document, until the application process is
 
  complete, as we often tailor and modify the agreements based on
 
  individual project needs.  This is painstaking work, and it's better to
 
  complete that work after both Conservancy and the project are quite sure
 
  that they both want the project will join Conservancy.</p>
...
 
@@ -121,48 +124,49 @@ it is an option for those projects that ask for it.</p>
 

	
 
<h2>If our project joins, must it be a member project of Conservancy forever?</h2>
 

	
 
<p>All agreements between member projects and the Conservancy stipulate
 
clearly that the member project can leave the Conservancy at any time.
 
Federal tax exemption law, though, states that projects must transfer
 
their assets from the Conservancy in a way that is consistent with the
 
Conservancy's not-for-profit tax status &mdash; meaning the assets cannot
 
be transferred to an individual or a for-profit entity.  Generally, a
 
project would either find another fiscal sponsor or form their own
 
independent tax-exempt non-profit.</p>
 

	
 
<p>We fully expect that some Conservancy projects will ultimately wish to
 
  form their own non-profit 501(c)(3) organizations; that's why we design
 
  our agreements with projects to allow them to leave to another 501(c)(3)
 
  organization.  Typically, projects join Conservancy because the project
 
  leaders don't want the burdens of running a non-profit themselves.
 
  Often, as projects grow, leaders get interested in the non-profit
 
  management and organizational side of the activities and are then
 
  prepared to take on the additional work themselves.</p>
 

	
 
<h2>How are &ldquo;product leaders&rdquo; defined with respect to Conservancy?</h2>
 

	
 
<p>How leaders are chosen for projects varies greatly from project to
 
  project.  Our goal is to do our best to embody the &ldquo;natural&rdquo;
 
  leadership structure that evolved in your project into the formal
 
  agreement with Conservancy.  As part of the agreement drafting, we work
 
  carefully with you to understand your project's governance and write up
 
  formally with you the decision-making process you use. Most project
 
  contributors find this process of formalizing the leadership structure
 
  helps them clarify in their own minds the governance of their project,
 
  even though the process can be difficult.  Since it can be a complicated
 
  process, we suggest that you prepare your project community for this
 
  discussion once your project is accepted.</p>
 

	
 
<h2>How much does will it cost us financially to join Conservancy?</h2>
 

	
 
<p>After your application is approved, as part of the negotiation of the
 
  formal agreement, we'll discuss this issue.  Typically, we ask that
 
  member projects voluntarily choose to donate some percentage of their
 
  donations received to support Conservancy's general operations servicing
 
  all its member projects (including yours).  We do understand that,
 
  particularly for small projects that only receive a few small donations,
 
  that donating a percentage of your income back to Conservancy can be a
 
  high burden.  Therefore, this is not a mandatory requirement.  We thus
 
  suggest that you be prepared to discuss this issue with us in detail
 
  after your application is approved.</p>
 

	
 
{% endblock %}
www/conservancy/static/members/current/index.html
Show inline comments
 
{% extends "base_members.html" %}
 
{% block subtitle %}Current Member Projects - {% endblock %}
 
{% block category %}members{% endblock %}
 
{% block submenuselection %}Current{% endblock %}
 
{% block content %}
 

	
 
<h1>Current Member Projects</h1>
 

	
 
<h2><a href="http://amarok.kde.org/">Amarok</a></a></h2>
 

	
 
<p>Amarok is a powerful music player with the aim to help people
 
rediscover music. It offers powerful collection management, context
 
information, integration of online services and a lot more.</p><p>Amarok
 
  is also affiliated with the KDE for project software development.</p>
 

	
 
<h2><a href="http://argouml.tigris.org/">ArgoUML</a></h2>
 

	
 
<p>ArgoUML is the leading open source UML modeling tool and includes
 
support for all standard UML 1.4 diagrams. It runs on any Java platform
 
and is available in ten languages. See the feature list for more details.</p>
 

	
 
<h2><a href="http://bongo-project.org/">Bongo</a></h2>
 

	
 
<p>The Bongo Project is creating fun and simple mail, calendaring and
 
contacts software: on top of a standards-based server stack; we're
 
innovating fresh and interesting web user interfaces for managing
 
personal communications. Bongo is providing an entirely free software
 
solution which is less concerned with the corporate mail scenario and
 
much more focused on how people want to organize their lives.</p>
 

	
 
<h2><a href="http://www.boost.org/">Boost</a></h2>
 

	
 
<p>Boost provides free peer-reviewed portable C++ source libraries.</p>
 

	
 
<p>Boost emphasizes libraries that work well with the C++ Standard
 
  Library.  Boost libraries are intended to be widely useful, and usable
 
  across a broad spectrum of applications.  The Boost license encourages
 
  both commercial and non-commercial use.</p>
 

	
 
<p>Boost aims to establish &ldquo;existing practice&rdquo; and provide
 
reference implementations so that Boost libraries are suitable for
 
eventual standardization. Ten Boost libraries are already included in the
 
C++ Standards Committee's Library Technical Report ( TR1) as a step toward
 
becoming part of a future C++ Standard. More Boost libraries are proposed
 
for the upcoming TR2.</p>
 

	
 
<h2><a href="http://www.busybox.net">BusyBox</a></h2>
 

	
 
<p>BusyBox combines tiny versions of many common UNIX utilities into a
 
single small executable. It provides replacements for most of the
 
utilities you usually find in GNU fileutils, shellutils, etc. The
www/conservancy/static/members/index.html
Show inline comments
 
{% extends "base_members.html" %}
 
{% block subtitle %}Project Membership in {% endblock %}
 
{% block category %}members{% endblock %}
 
{% block content %}
 

	
 
<h1>Conservancy Project Membership</h1>
 

	
 
<p>A major component of Conservancy's work to advance software freedom is
 
  through its work to provide
 
  non-profit <a href="/members/services/">infrastructure and services</a>
 
  to
 
  <a href="/members/current/">its member projects</a>.  Conservancy's goal
 
  is to handle all the parts of advocacy, leadership, organization and
 
  coordination other than actual development of the software and
 
  documentation.  By handling all these details, Conservancy allows its
 
  member project developers to focus on what they do best: writing,
 
  improving and documenting FLOSS.</p>
 

	
 
<p>Project leaders who believe that their project might benefit from
 
  Conservancy's <a href="/members/services/">member project services</a>
 
  are encouraged to <a href="/members/apply/">apply for
 
  membership</a>.</p>
 
{% endblock %}
www/conservancy/static/members/services/index.html
Show inline comments
 
{% extends "base_members.html" %}
 
{% block subtitle %}Member Project Services - {% endblock %}
 
{% block category %}members{% endblock %}
 
{% block submenuselection %}Services{% endblock %}
 
{% block content %}
 

	
 
<h1>Member Project Services</h1>
 

	
 
<p>Conservancy assists FLOSS project leaders by handling all matters other
 
  than software development and documentation, so the developers can focus
 
  on what they do best: improving the software for the public good.  The
 
  following are the services and options that are available to FLOSS
 
  projects that have joined Conservancy as a member project.</p>
 

	
 
<h2>Tax-Deductible, Earmarked Donations</h2>
 

	
 
<p>Member projects can receive earmarked donations through Conservancy.
 
   Since Conservancy is a 501(c)(3) charity incorporated in New York,
 
   donors can often deduct the donation on their USA taxes.  Additionally,
 
   the donors can indicate that their donation should be used to advance a
 
   specific member project, and those funds are kept in a separate account
 
   for the member project by Conservancy.  This structure prevents
 
   developers from having to commingle project funds with their own
 
   personal accounts or having to set up their own project specific
 
   account.</p>
 

	
 
   <p>Since the Conservancy is a tax-exempt organization, there are some
 
   limits that the law places on what member projects can do with their
 
   assets, but those limits are the same as if the project was an
 
   independent non-profit entity.  Usually, the project leadership can
 
   then indicate to Conservancy's leadership how the funds should be spent
 
   to advance the project and Conservancy permits these funds to be spent
 
   in any way that is appropriate activity under Conservancy's 501(c)(3)
 
   not-for-profit mission.  Some typical uses of earmarked donations by
 
   Conservancy's member projects are:
 
<ul>
 
<li>funding travel expenses for project developers to attend relevant
 
  conferences.</li> 
 

	
 
<li>domain name fees, bandwidth costs, and computer equipment
 
  purchases.</li>
 

	
 
<li>purchasing media for distribution of project software at conferences
 
  and events.</li>
 

	
 
<li>paying key developers on a contractual basis to improve the project's
 
  software and its documentation.</li>
 

	
 
<li>sponsoring and organizing conferences for the project.</li>
 
 
 
<li>trademark registration and enforcement.</li>
 

	
 
<li>FLOSS license enforcement and compliance activity.</li>
 
</ul>
 

	
 
</p>
 

	
 
<h2>Asset Stewardship</h2>
 

	
 
<p>Conservancy can hold any assets for the project on its behalf.  This
 
  includes copyrights, trademarks, domain names, physical computer
 
  equipment or anything that should be officially held in the name of the
 
  project.  Member projects are not required that Conservancy hold all
 
  assets of a project. (For example, member projects are
 
  not <em>required</em> to assign copyrights to the Conservancy.)
 
  However, Conservancy can accommodate the needs of projects that want
 
  their assets under the control of a not-for-profit entity and exercised
 
  only for the public good.</p>
 

	
 
<h2>Contract Negotiation and Execution</h2>
 

	
 
<p>Projects sometimes need to negotiate and execute a contract with a
 
  company.  For example, when a project wants to organize and run a
 
  conference, the venue usually has a complicated contract for rental of
 
  the space and services.  Conservancy assists projects in the negotiation
 
  of such contracts, and can sign them on behalf of the project.</p>
 

	
 
<h2>FLOSS Copyright License Enforcement</h2>
 

	
 
<p>Complying with FLOSS licenses is easy, as they permit and encourage
 
  both non-commercial and commercial distribution and improvements.
 
  Nevertheless, violations of FLOSS licenses (in particular of
 
  the <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>
 
  and <a href="http://www.gnu.org/licenses/lgpl.html">LGPL</a>) are all
 
  too common.  At request of the project's leaders, Conservancy can carry
 
  out license enforcement activity on behalf of the project's copyright
 
  holders.</p>
 

	
 
<h2>Fundraising Assistance</h2>
 

	
 
<p>Conservancy provides various tools and advice to member projects on
 
  methods of raising funds for their projects' earmarked accounts.</p>
 

	
 
<h2>Avoid Non-Profit Administrivia</h2>
 

	
 
<p>Member projects can continue to operate in the same way they did before
 
joining the Conservancy without having to select a board of directors or
 
any other layer of corporate management, without having to maintain
 
corporate records and without having to do any of the other things
 
required of incorporated entities.  The Conservancy handles all of that
 
burden on behalf of its projects.</p>
 

	
 

	
www/conservancy/templates/base_conservancy.html
Show inline comments
 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 

	
 
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 

	
 
  <head>
 
    <title>{% block title %}{% block subtitle %}{% endblock %}Software Freedom Conservancy{% endblock %}</title>
 
    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 
    <meta name="description" content="The Software Freedom Conservancy provides a non-profit home and services to Free, Libre and Open Source Software (FLOSS) projects." />
 
    <meta name="keywords" content="software, freedom, conservancy, open source, gnu, GNU, Open Source, Free and Open Source, Free and Open Source Software, FLOSS, FOSS, protect, protection, help, policy, linux, non-profit" />
 
    <link rel="stylesheet" type="text/css" media="screen, projection" href="/conservancy.css" />
 
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />
 
    {% block head %}{% endblock %}
 
  </head>
 

	
 
  <body class="conservancy-{% block category %}other{% endblock %}">
 
    <div id="conservancyheader">
 
      <h1><span id="logobutton"><a href="/">Software Freedom Conservancy</span></a></h1>
 
    </div>
 
    <div id="navbar-outer">
 
      <div id="navbar">
 
	<ul>
 
          <li class="overview"><a href="/overview/">Overview</a></li>
 
          <li class="news"><a href="/news/">News</a></li>
 
          <li class="blog"><a href="/blog/">Blog</a></li>
 
	  <li class="members"><a href="/members/">Member Projects &amp; Services</a></li>
 
	  <li class="Members"><a href="/members/">Member Projects &amp; Services</a></li>
 
          <li class="About"><a href="/about/">About</a></li>
 
	  <li class="donate"><a href="/donate/">Support Conservancy!</a></li>
 
	</ul>
 
      </div>
 
      <div id="navbar-clear"></div>
 
    </div>
 
      {% block outercontent %}<div id="mainContent">{% block content %}{% endblock %}</div>{% endblock %}
 
    <div id="conservancyfooter">
 
      <p><a href="/">Main Page</a> | <a href="/about/contact/">Contact</a> | <a href="/privacy-policy/">Privacy Policy</a> | <a href="/feeds/news/">News Feed</a></p>
 
      <p class="copyright_info">This page is licensed under the <a href="http://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons Attribution-NonCommercial-NoDerivs 2.0 license</a>.</p>
 
    </div>
 
  </body>
 
</html>
www/conservancy/templates/base_members.html
Show inline comments
 
{% extends "base_conservancy.html" %}
 
{% block category %}Members{% endblock %}
 
{% block outercontent %}
 
    <div id="container">
 
         <div id="sidebar" class="{% block submenuselection %}other{% endblock %}">
 
            <h2>Membership &amp; Services</h2>
 
            <h2>{% block category %}Members{% endblock %} Projects &amp; Services</h2>
 
            <ul>
 
            <li class="Current"><a href="/members/current/">Current Member Projects</a></li>
 
            <li class="Services"><a href="/about/services/">Member Project Services</a></li>
 
            <li class="Applying"><a href="/about/apply/">Applying</a></li>
 
            <li class="Services"><a href="/members/services/">Member Project Services</a></li>
 
            <li class="Applying"><a href="/members/apply/">Applying</a></li>
 
            </ul>
 
         </div>
 
               <div id="mainContent">{% block content %}{% endblock %}
 
               </div>
 
   </div>
 
{% endblock %}
0 comments (0 inline, 0 general)