Personal tools committee

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(10 intermediate revisions by 3 users not shown)

Latest revision as of 22:59, 8 July 2016

To contact the committee, send email to committee [AT] To discuss how the committee has things set up on haskell community infrastructure, services provided, and that they might wish to add, and how you can help (or even just what your thoughts are on how things might be done and to participate in committee discussions), join the haskell-community list.


[edit] 1 Responsibilities is incorporated in the state of New York as of November 2015. Its governing rules are laid out in the Board Resolution of that month. Its purpose is to promote educational and scientific progress relating to the Haskell programming language and related technologies. As a whole it seeks to service the open source Haskell community.

Some particular aspects of the work of include producing and maintaining material regarding the Haskell language on and other associated websites; hosting and maintaining shared assets and infrastructure for the benefit of the Haskell community; coordinating educational activities including mentorship programs; and potentially organizing event regarding the Haskell language.

The committee serves as the board of directors of, Inc. Its responsibilities include:

  • setting the policy on what the domain name, and its subdomains, may be used for
  • setting the policy on what the servers owned by may be used for
  • determining how funds are spent activities are directed towards charitable purposes, and are in compliance with section 501(c)(3) of the U.S. federal income tax code. has nonprofit tax-exempt status under this section.

[edit] 2 Current members

  • Adam Foltzer (term ends 2016)
  • Nicolas Wu (term ends 2016)
  • Andres Loeh (term ends 2016)
  • Edward Kmett (term ends 2017)
  • Ryan Trinkle (term ends 2017)
  • John Wiegley (term ends 2017)
  • Gershom Bazerman [chair] (term ends 2018)

e-mail: committee [AT]

[edit] 3 Operation

The committee consists of 7 members. Members are expected to serve a 3 year term, and terms are staggered so that 2 or 3 members step down each year, at the end of October.

The members will elect one of their number to be chair each year. The chair is responsible for making sure that things keep moving, and to ensure that a conclusion is reached on any issues raised.

When a member steps down, either because they have reached the end of their term or because other circumstances require them to step down early, open self-nominations will be sought from the community via the haskell@ mailing list. Previous committee members, including those who have just stepped down, will also be eligible for nomination.

The committee will then select a replacement from amongst those nominated. For the purposes of considering nominations, the committee will include any outgoing members who are not seeking re-appointment.

The committee replacement process is intentionally currently very light. As we get more experience, we may wish to change it, e.g. by having a larger subset of "the community" vote on nominations.

If any member of the community wishes to raise any issue with the committee, they may contact it by e-mailing committee [AT]

The committee seeks to discuss its matters brought to it, as much as possible, via the haskell-community [AT] mailing list where all interested parties may participate. Ideally it will seek to reach consensus among its membership on its decisions. Ultimately, the committee will make decisions by more than half of the membership voting for a particular outcome. These rules of operation may also be changed in the same way.

Each year, the committee will post a statement of the assets, and the transactions for that year. Some details may be omitted, e.g. for confidentiality of donors.

[edit] 4 Discussions

In general and by default, the committee will seek to conduct its discussions on the haskell-community list, which is open to anyone to join, and where discussions can be held not just among members of the committee but also in conjunction with anyone else who wishes to participate.

[edit] 5 History

The committee was initially formed in November 2010. As described there:

In recent years, 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 itself, and on the 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’s infrastructure development, open nominations were held to form a committee, based on representatives from the open source Haskell community.