﻿﻿﻿In recent years, haskell.org has started to receive assets, e.g. Google Summer Of Code funds, donations for Hackathons, and a Sparc machine for use in GHC development. We have also started spending this money: on the community server, on a server to take over hosting haskell.org itself, and on the haskell.org domain name. There is also interest in running fundraising drives for specific things such as Hackathon sponsorship and hosting fees.

To resolve who is responsible for haskell.org’s infrastructure development, open nominations were held to form a haskell.org committee, based on representatives from the open source Haskell community. Nominations were received, and we are pleased to announce that the new committee has formed.

The current members of the committee are:

Members are expected to serve a 3 year term, and terms are staggered so that 2 or 3 members step down each year.

What we’re working on

Over the past year, two of the core infrastructure nodes: http://www.haskell.org (which hosts the main wiki), and code.haskell.org (which hosts a lot of project repositories) have become increasingly unreliable. To address this, a new high-spec, dedicated host was purchased, which will be used to replace both services.

The commitee is now working directly to solve these issues:

Moving http://www.haskell.org (and the mailing lists) from Yale to the new dedicated host.

Migrating the code.haskell.org host to a VM on the new machine.

More news on this work shortly.

Stay up to date

To help people better keep up to date on the status of the haskell.org infrastructure, stay up to date via:

Twitter : get status updates about haskell.org services via twitter.

: get status updates about haskell.org services via twitter. Email: To get in touch with the committee, use the committee @ haskell.org address.