diff --git a/www/conservancy/static/members/apply/index.html b/www/conservancy/static/members/apply/index.html index 7c9abcfdca18208a5ff5904b375cdb0ea09d2d58..129582b286b0e9f90aacadc3667e9212fd72d51a 100644 --- a/www/conservancy/static/members/apply/index.html +++ b/www/conservancy/static/members/apply/index.html @@ -55,7 +55,7 @@
  • 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 + 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 @@ -84,10 +84,10 @@

    While any project meeting the criteria above can apply, meeting these - criteria doesn't guarantee acceptance of your project. The Conservancy + criteria doesn't guarantee acceptance of your project. 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 give higher priority to projects that + Furthermore, Conservancy does give higher priority to projects that have an established userbase and interest, but also tries to accept some smaller projects with strong potential.

    @@ -124,7 +124,7 @@ infrastructure and facilitates the project's ability to raise its own funds. Conservancy therefore assists your project in raising funds, and allows your project to hold those funds and spend them on activities - that simultaneously advance the non-profit mission of the Conservancy + that simultaneously advance Conservancy's non-profit mission and the FLOSS development and documentation goals of the project.

    What will the project leaders have to agree to if our project joins?

    @@ -146,51 +146,51 @@ project to join Conservancy.

    -

    If my project joins the Conservancy, how will it change?

    +

    If my project joins Conservancy, how will it change?

    Substantively, member projects continue to operate in the same way as -they did before joining the Conservancy. So long as the project remains +they did before joining Conservancy. So long as the project remains devoted to software freedom and operates consistently with the -Conservancy's tax-exempt status, the Conservancy does not intervene in the +Conservancy's tax-exempt status, Conservancy does not intervene in the project's development other than to provide administrative assistance. -For example, the Conservancy keeps and maintains books and records for the +For example, Conservancy keeps and maintains books and records for the project and assists with the logistics of receiving donations, but does not involve itself with technical or artistic decision making. Projects -are asked, however, to keep the Conservancy up to date on their +are asked, however, to keep Conservancy up to date on their activities.

    Once our project joins, who holds its assets (money, copyrights, trademarks, etc.)?

    -

    The Conservancy holds assets on behalf of its member projects and +

    Conservancy holds assets on behalf of its member projects and manages and disburses those assets in accordance with the wishes of the -project's leadership. Funds received by the Conservancy on behalf of a +project's leadership. Funds received by Conservancy on behalf of a project are kept track of separately for each specific project and the management of those funds is directed by the project. For example, if a donor wanted to contribute $100 to Project Foo, they would formally make -the donation to the Conservancy and identify Project Foo as the desired -project to support. The Conservancy would then deposit the check and +the donation to Conservancy and identify Project Foo as the desired +project to support. Conservancy would then deposit the check and earmark the funds for use by Project Foo. Project Foo would then tell the Conservancy how that money should be spent. As long as that expense is a legitimate non-profit expense fitting with Conservancy's non-profit mission, Conservancy pays the expense on the Project's behalf.

    Similarly, any copyrights, trademarks, domain name or other assets -transferred to a project can also be held by the Conservancy on behalf of -the project. A significant service that the Conservancy provides its +transferred to a project can also be held by Conservancy on behalf of +the project. A significant service that Conservancy provides its members is a vehicle through which copyright ownership in the project can be unified. There are several advantages to having a consolidated copyright structure, including that it makes enforcement activity easier and more effective. However, copyright, trademark, and domain name -assignment is not a requirement in order to join the Conservancy, rather, +assignment is not a requirement in order to join Conservancy, rather, it is an option for those projects that ask for it.

    If our project joins, must it be a member project of Conservancy forever?

    -

    All agreements between member projects and the Conservancy stipulate -clearly that the member project can leave the Conservancy with a few +

    All agreements between member projects and Conservancy stipulate +clearly that the member project can leave Conservancy with a few months' notice. 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 — +must transfer their assets from Conservancy in a way that is +consistent with Conservancy's not-for-profit tax status — 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.

    diff --git a/www/conservancy/static/members/services/index.html b/www/conservancy/static/members/services/index.html index c0cd79e9a52fa315b110e22e6281c5bc78ae1c95..e50772977247fa49f25ec1035dc8b7ffdbfc6dab 100644 --- a/www/conservancy/static/members/services/index.html +++ b/www/conservancy/static/members/services/index.html @@ -23,7 +23,7 @@ personal accounts or having to set up their own project specific account.

    -

    Since the Conservancy is a tax-exempt organization, there are some +

    Since 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 @@ -61,7 +61,7 @@ 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 required to assign copyrights to the Conservancy.) + not required to assign copyrights to 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.

    @@ -111,10 +111,10 @@

    Avoid Non-Profit Administrivia

    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 +joining 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 +required of incorporated entities. Conservancy handles all of that burden on behalf of its projects.

    diff --git a/www/conservancy/static/privacy-policy/index.html b/www/conservancy/static/privacy-policy/index.html index 66d9109c4cfa53da11d18c6d277ffbcfaf198fc8..abe3243e5391826611b97752360c32b3c50af51d 100644 --- a/www/conservancy/static/privacy-policy/index.html +++ b/www/conservancy/static/privacy-policy/index.html @@ -4,10 +4,10 @@

    Privacy Policy

    -

    The Software Freedom Conservancy (“Conservancy”) is +

    Software Freedom Conservancy (“Conservancy”) is committed to protecting the privacy of our website visitors, our supporters and our member projects. In this policy, -“Conservancy” or “We” refers to the Conservancy +“Conservancy” or “We” refers to Conservancy Board of Directors, officers, management, staff, cooperating attorneys, interns, volunteers, and consultants. As to all of the information described below, Conservancy will not give, sell, rent, or exchange the diff --git a/www/conservancy/templates/frontpage.html b/www/conservancy/templates/frontpage.html index 68d946d95bb3b0ca0615d4d3da1a769db0b5d52f..3ff0ce3d2642d0b4c36a0794f8e191ee2d1ef336 100644 --- a/www/conservancy/templates/frontpage.html +++ b/www/conservancy/templates/frontpage.html @@ -11,9 +11,9 @@

    -

    The Software Freedom Conservancy

    +

    Software Freedom Conservancy

    -

    The Software Freedom Conservancy is a not-for-profit organization that +

    Software Freedom Conservancy is a not-for-profit organization that helps promote, improve, develop, and defend Free, Libre, and Open Source Software (FLOSS) projects. Conservancy provides a non-profit home and infrastructure for FLOSS projects. This allows FLOSS developers to