(→Policy on adding new subdomains)
(update name of Oxford University Computing Lab)
Revision as of 06:22, 24 April 2012
The names in the haskell.org domain point to a set of machines:
This machine (22.214.171.124) responds to the names haskell.org, www.haskell.org, bugs.haskell.org and lambda.galois.com. It is hosted in Germany by Hetzner.
MRTG: All network traffic.
Note: before December 2010 these domains were hosted by haskell.cs.yale.edu at Yale University.
This machine (126.96.36.199) responds to the names darcs.haskell.org, hackage.haskell.org, cvs.haskell.org, haskell.galois.com, abbot.galois.com. It is a dedicated host in Galois server room.
- darcs repositories for GHC and core libraries, http://darcs.haskell.org/
- HackageDB, http://hackage.haskell.org/
- old CVS repositories, http://cvs.haskell.org/
- various Trac instances, e.g. http://hackage.haskell.org/trac/ghc
For more details, see Abbot.
The Haskell community server is designed to support and encourage open Haskell-based projects and collaborations of all kinds, provided only that their intention is to contribute something to the community, and that all hosted project content is publicly available. Resources available include:
- Publicly available read-only darcs repositories, http://code.haskell.org/
- Write access to the darcs repositories for project members
- Trac instances for integrated issue tracking, wiki, and project management. Trac instances are also integrated with the project's darcs repository. http://trac.haskell.org/
- GNU Mailman mailing lists
- Public web-space for projects, http://projects.haskell.org/
- Personal web-space for project members
- Blog aggregation, http://planet.haskell.org/
For information about how to host a project, see http://community.haskell.org/.
Notes: machine has been increasingly unreliable. Plan to move to a VM host on new-www.haskell.org
sparky - a SPARC T2 donated by (formerly) Sun Microsystems. Kindly hosted by Chalmers but technically owned by Oxford University Department of Computer Science (?).
2 Relation between the services
I'm wondering what the relationship is (if any) between code.haskell.org and darcs.haskell.org.
- darcs.haskell.org hosts ghc, the core libs and many others. The server is maintained by Galois. Because it hosts the most central bits of the haskell platform, security is fairly tight and getting an account there is hard. There are very few community members with root privileges.
- community.haskell.org was created precisely to provide hosting to the wider community. It is hosted commercially, paid for by haskell.org's Google Summer of Code funds. We have several community admins with root privileges.
Should my projects be hosted at darcs or code?
- code.haskell.org. It's easy to get an account there via the web submission system: http://community.haskell.org/admin/
Is one more blessed/preferred over the other for community projects?
- Yes, code.haskell.org is preferred.
If my project is currently on darcs, should I migrate to code?
- You can if you like, there is no need to do so however. Accounts on darcs.haskell.org are not going to be revoked as far as I know. The community server is an addition, not a replacement.
If I have an account on darcs, will it work on code, or do I need to get a new account on code?
- They are totally separate systems.
2.1 See also
3 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 current policy is that new subdomains are to be used for services rather than content.
So for example a Haskell graphics related website should 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.
Clearly the line between services and content, and indeed the precise definitions of each, is something of a grey area, and we are certainly happy to be flexible particularly if there are technical or other reasons for doing things one way.