-
Notifications
You must be signed in to change notification settings - Fork 3
/
params.json
1 lines (1 loc) · 2.83 KB
/
params.json
1
{"name":"Conservatory.github.io","tagline":"Web pages for the Conservatory.","body":"## The Conservatory\r\n\r\nWelcome to the Conservatory: [github.com/Conservatory](https://github.com/Conservatory)\r\n\r\nThe Conservatory is an archive for [open source](http://opensource.org/definition) code that doesn't have any other clear canonical version-controlled home on the public Internet. It's a place to stash code whose authors\r\n\r\n1. Haven't put it under public version control, or\r\n2. Have abandoned it, neglecting even to maintain a public copy, or\r\n3. Have actively tried to remove it from the Net, its open source license notwithstanding.\r\n\r\n(You might think that (3) never happens, but actually it was [an instance](https://github.com/Conservatory/openstv) of (3) that motivated the creation of the Conservatory.)\r\n\r\nThe Conservatory is strictly about preservation and ease of revival. The presence of a codebase in the Conservatory is _not_ a criticism of the code's authors or former maintainers in any way. No one is obligated to maintain a version-controlled public repository of anything, unless they've signed a contract to do so, in which case their obligation is to the contractual counterparty not to the public at large.\r\n\r\nThe Conservatory is archival. Repositories here do not take pull requests because they are not meant to be the \"social master\" repository of their respective projects. If you want to work on one of the codebases here, please fork it to a new repository and work on it there. If your fork catches on, it will be the new master, and the Conservatory's copy will become less and less important (as well as increasingly out-of-date) -- which is fine.\r\n\r\n### How to submit a codebase.\r\n\r\nFirst make absolutely sure it's licensed under an open source license, and make sure you've got a copy of the code yourself (don't count on it staying wherever on the Net you found it -- if it disappeared from other places it could disappear from there too). Then file an issue against [this repository](https://github.com/Conservatory/conservatory.github.io/) with details. That's it :-).\r\n\r\n### Why is the Conservatory on GitHub?\r\n\r\nGitHub offers unlimited zero-cost repository hosting for open source code, is reassuringly large and stable -- after all, this is an archive, so the whole point is for it to stick around -- and most open source developers know how to work with it (for example, they know how to fork a repository in order to start working on its code). [Gitorious.org](https://gitorious.org/) was tempting for philosophical reasons (the code that runs the site is itself open source), and we certainly encourage people to mirror any Conservatory repository there, but our primary goal was stability and familiarity.","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}