Conservancy/policies
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Policies of the Software Freedom Conservancy, Inc.
73 commits 1 branch 0 tags 186 KiB
Find a file
Bradley M. Kuhn d88ddcd19c Gitorious Apocalypse: Kallithea is now canonical 
Conservancy's Kallithea instance is now the canonical location for the
Conservancy policies repository.
2016-07-19 16:27:06 -07:00
Conflicts Remove spurious LaTeX command 2014-06-30 22:19:49 -04:00
Document-Retention Typo fixes 2014-06-30 22:19:49 -04:00
Travel No policy change: update details for payment info. 2016-07-19 16:24:18 -07:00
Whistle-Blower removed non-canonical versions 2012-02-22 20:36:33 +00:00
CC0-1.0.txt Creative Commons 0 1.0 Universal (CC0 1.0), Public Domain Dedication, 2014-05-29 21:21:52 -04:00
README.md Gitorious Apocalypse: Kallithea is now canonical 2016-07-19 16:27:06 -07:00

README.md

Conservancy's Policies

These are the policies of the Software Freedom Conservancy, Inc..

License

To the extent possible, Conservancy disclaims all copyright on the documents herein, and provides them under the CC-0 1.0 Universal copyright waiver and fallback license. Conservancy kindly asks that you remove Conservancy's name and all references to contact information of our organization if you reuse these policies for your own organizations and projects.

Contributing

The canonical location for this repository is on Conservancy's Kallithea instance. Copies of this repository elsewhere, such as Github, are for backup purposes only. If you have contributions, submit them on via Conservancy's Kallithea instance.

These policies are discussed in public with Conservancy's member projects and other Conservancy enthusiasts on the polices-discuss mailing list.

The 'master' branch in this repository denotes the current polices that are in-effect for the Software Freedom Conservancy, Inc. Proposals are made by people in forked versions on Gitorious, and then if the Conservancy staff plans to propose them to Conservancy's Board of Directors, they are merged into the 'ready-for-board-approval' branch. Once approved by the Board of Directors, Conservancy staff merges the changes into the 'master' branch.