Project Requirements

note: these requirements are being updated and adapted in a file in our legal repo

Required licenses and FLO definitions

Free/Libre/Open (FLO) means unrestricted freedoms to use, modify, and share. A few precise FLO definitions compete for recognition as the standard in different fields.1 Thankfully, the most accepted definitions are practically equivalent. We do not want to create yet another competing standard, so we defer to the options listed below.

Note: we have a separate page in the About section, titled “Why Only Free/Libre/Open Projects?” discussing why we limit the site to FLO projects.

Software

Software projects must meet either of these definitions:

Educational, research, and cultural works

Projects in the fields of education, research, journalism, art, video, and music must meet either of these definitions:

Online services

Online services must meet the Open Software Service Definition open service logo and should otherwise abide by the Franklin Street Statement on Freedom and Network Services.

Overall, online services should relate in a fundamental way to networking and communication and not merely substitute for products that would be equally effective when run locally and offline.2

Hardware plans

Snowdrift.coop focuses on funding the production of non-rivalrous goods. Projects that produce hardware are still welcome as long as funding from Snowdrift.coop is aimed toward serving the non-rivalrous elements of the project.

Projects working on plans, software, designs, and related resources for hardware must meet either:

License options

Each definition above includes connected lists of approved licenses. See our separate discussion of FLO license options.

Copyfree The list of Copyfree licenses from the Copyfree Initiative includes several legitimate FLO licenses that have not been reviewed by the organizations above, so we will accept any of those licenses as well — as long as the definitions above are still otherwise met.

Patent non-aggression

All projects which involve any patentable subject matter must accept a pledge that the developers themselves will not use patent claims to restrict the freedoms otherwise included in the FLO definitions above.3

Although not required, we also suggest that such projects use a license that includes explicit patent grant such as:

Product release requirements

  • Products must entirely meet the definitions above
    • We do not accept projects which release only limited versions of their work under the FLO definitions while producing a separate proprietary version.
      • Of course, permissively-licensed products are susceptible to derivatives being made proprietary. We do not exclude projects merely because someone else has made a proprietary derivative. However, the project team itself must not actively promote the use of proprietary derivatives.
    • Although we strongly discourage it, project teams may make fully-distinct, independent products that do not meet our requirements, but such products shall not be promoted, funded, or otherwise supported through Snowdrift.coop.
    • A project itself can meet these requirements even if typically used in a proprietary context (such as an otherwise FLO software program that runs on a proprietary operating system).
  • Release your final results in standard non-proprietary formats.
  • Provide unobstructed public access to anything fully published.
    • Do not force users to do anything extra (such as registering with your site) in order to download the product.
    • For high-bandwidth items, limits on direct access are fine if alternative access is provided via BitTorrent or other unrestricted mirrors.
  • Documentation and support materials must themselves meet the project requirements.

Transparency

Use of funds raised through Snowdrift.coop

Development should result in concrete end-products and/or improvements in existing products. Use funds from Snowdrift.coop for ongoing progress rather than for profits or compensation for past work.

Projects should maximize efficient use of funds. Hire as many quality team members as can be put to good use and as funds will permit while aiming to provide a living wage.4

Appropriate uses of funds:

  • Payments to team for ongoing work
  • Covering necessary expenses, including incidental bandwidth/hosting costs 5
  • Saving funds in accounts budgeted for future costs
  • Donations to upstream FLO projects 6

  1. The different definitions are generally between “freedom”-focus versus “open”-focus, which involves the same terminology debates surrounding the term Free/Libre/Open.

  2. The GNU.org article Who does that server really serve? is useful for further consideration. That article describes the problems with Service as a Software Substitute (SaaSS).

  3. We are considering requiring the Defensive Patent License. The initial version had a fatal flaw excluding “clone products” from the licensing guarantee. The newer v. 1.1 seems better but has some burdensome acceptance procedures which sound like there must be a process for each acceptance of a license from an entity. So it does not appear to serve the generalized need we have here. Perhaps the Open Invention Network is better and good enough to require for all patentable-subject-matter projects. The OIN focuses on the Linux community but is for anyone and is very easy to join.

  4. Compensation rates for team members can be controversial and complex. Our ideal is a decent living far all.

    Of course, a project with limited funding must decide whether to support a larger team only part-time (thus requiring them to find additional outside income, either through unrelated jobs or from other FLO projects) or to provide a higher level of support to a smaller team. While we encourage paying a living wage, a projects with limited income must make tough choices.

    On the other side, projects may choose to pay higher competitive market rates in order to recruit and retain the best teams who might otherwise work on proprietary projects. We encourage projects to find teams with lower cost of living in order to make the most of limited resources, but each team may handle these decisions in their own way, subject only to transparency requirements and continued support from the patron community. As a general guideline, projects should recruit the best teams by emphasizing a decent living, autonomy, challenge, and social purpose instead of focusing on the highest pay or other luxuries.

  5. Costs considered incidental are those that are only a small fraction of overall development expenses. At this time, we do not support the use of Snowdrift.coop funds to pay the expensive hosting costs for especially high-bandwidth items (such as large quantities of streaming HD video). We encourage distributed services like BitTorrent as much as possible. Otherwise, we encourage per-use charges for rivalrous goods like server bandwidth or physically-shipped media. Keeping these costs direct encourages a more honest economic market, better transparency, and conservative use of limited resources.

  6. Any project that is directly related or has significantly contributed to your development can be considered ‘upstream’. For example, Snowdrift.coop is an upstream project for others on the site because we provide a supporting service.