Difference between revisions of "Haskell.org domain"
(update to point to new resources) |
|||
| (28 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Community]] |
[[Category:Community]] |
||
| − | The '''haskell.org domain''' includes these names: |
||
| + | == Overview == |
||
| − | * [[haskell.org]], [http://www.haskell.org/ www.haskell.org], [http://bugs.haskell.org/ bugs.haskell.org], at Yale university. <br>This machine runs the web server, wiki, and mailing lists. |
||
| + | The names in the '''haskell.org domain''' point to a set of machines. The bulk of those machines are now cataloged on the [https://phabricator.haskell.org/w/infrastructure/ Haskell Phabricator Wiki] |
||
| + | Certain machines had been made available for community hosting in the past, and many still exist on [http://community.haskell.org community.haskell.org]. However, given the rise of new options for hosting, we are discouraging the use of these servers, and would like to help those now currently using them to find a way to host their content elsewhere. See the February 2015 blog post [https://blog.haskell.org/post/the_future_of_community_haskell_org/ The Future of Community.Haskell.Org] for more. |
||
| − | * [http://darcs.haskell.org/ darcs.haskell.org], [http://hackage.haskell.org/ hackage.haskell.org], [http://cvs.haskell.org/ cvs.haskell.org], [http://haskell.galois.com/ haskell.galois.com], run by Galois. <br>This machine serves the central darcs repositories for the projects hosted at darcs.haskell.org, the darcsweb service, and it also runs the various Trac instances (eg. http://hackage.haskell.org/trac/ghc). |
||
| + | == Policy on adding new subdomains == |
||
| − | * [http://community.haskell.org/ community.haskell.org], [http://code.haskell.org/ code.haskell.org], [http://trac.haskell.org/ trac.haskell.org], [http://rt.haskell.org/ rt.haskell.org] <br>for hosting anyone's Haskell projects. See [http://www.haskell.org/pipermail/haskell/2007-June/019592.html this message]. |
||
| + | We limit the addition of new subdomains to haskell.org to minimise unnecessary proliferation of subdomains and to try to keep the haskell.org domain reasonably well organised, while still helping people do useful things with it. |
||
| − | {{stub}} |
||
| + | |||
| + | The policy has been that new subdomains are to be used for services rather than content. |
||
| + | |||
| + | So for example a Haskell graphics related website would normally go at <nowiki>http://www.haskell.org/graphics</nowiki>, rather than <nowiki>http://graphics.haskell.org</nowiki>. |
||
| + | |||
| + | In contrast a service like hackage does merit its own subdomain. |
||
| + | |||
| + | In either case, adding either new services or subsites is fairly rare and such requests will be considered on their own merits, on a case-by-case basis. |
||
Latest revision as of 16:44, 28 May 2015
Overview
The names in the haskell.org domain point to a set of machines. The bulk of those machines are now cataloged on the Haskell Phabricator Wiki
Certain machines had been made available for community hosting in the past, and many still exist on community.haskell.org. However, given the rise of new options for hosting, we are discouraging the use of these servers, and would like to help those now currently using them to find a way to host their content elsewhere. See the February 2015 blog post The Future of Community.Haskell.Org for more.
Policy on adding new subdomains
We limit the addition of new subdomains to haskell.org to minimise unnecessary proliferation of subdomains and to try to keep the haskell.org domain reasonably well organised, while still helping people do useful things with it.
The policy has been that new subdomains are to be used for services rather than content.
So for example a Haskell graphics related website would normally go at http://www.haskell.org/graphics, rather than http://graphics.haskell.org.
In contrast a service like hackage does merit its own subdomain.
In either case, adding either new services or subsites is fairly rare and such requests will be considered on their own merits, on a case-by-case basis.