haskell-org-committee: merge in content from the wiki

As outlined in haskell-infra#59, there are two pages which describe the Haskell.org committee and it's roles, responsibilities, process, history, etc. One is here on haskell.org, the other is on the wiki at https://wiki.haskell.org/Haskell.org_committee. Both pages appear authoritative, but differ in their content. At the same time, the general consensus is to move content off the wiki (particularly the more "official" content such as this). We would then replace that wiki article with a link to the this page. This is a first attempt which is more of a "bulk import" (or "merge") of the existing content. Note that there are a few places where the differences in content on the haskell.org page and wiki article may seem to be in conflict (or where one does not go as far as the other). These discrepancies and conflicts should be reviewed and updated. Some of the wiki content is more verbose than that on this page, and may still deserve some word-smithing.

A rough list of changes:
* collected the full list of links at the bottom of the page
* move the list of "committee members" a little lower in the page, bumping contact info and responsibilities above
* Included (merged) process, history and responsibilities content (from the wiki) that was missing here on this page

haskell-org-committee.markdown

@@ -14,15 +14,21 @@ Haskell.org is a 501(c)(3) non-profit organization that oversees the Haskell.org
   * [Discourse][discourse]
   * [Hoogle], a type-aware Haskell search engine
 
-Haskell.org also organizes Haskell's participation in  the [Google Summer of Code program][summer].
+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 Haskell.org include producing and maintaining material regarding the Haskell language on haskell.org 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.
+
+Haskell.org also organizes Haskell's participation in  the [Google Summer of Code program][gsoc].
+
+### Contact
+
+  * [[email protected]][email]: directly email the committee
+  * [haskell-community mailing list][list]: public discussions about the committee and Haskell community infrastructure
+  * [GitHub][github]: issues, suggestions and pull requests for the website
+  * TODO: add one for proposal process?
 
-[summer]: https://summer.haskell.org/
-[wiki]: https://wiki.haskell.org/Haskell
-[mailing]: https://www.haskell.org/mailing-lists/
-[discourse]: https://discourse.haskell.org
-[Hoogle]: https://hoogle.haskell.org/
-[Hackage]: https://hackage.haskell.org/
-[GHC]: https://www.haskell.org/ghc/
 
 ## Haskell.org Committee
 
@@ -44,25 +50,47 @@ The committee consists of 7 members serving 3-year terms. The current members ar
   * Rebecca Skinner (term ends 2022)
   * Alexandre Garcia de Oliveira (term ends 2022)
 
-In November of each year—or if a member steps down before their term is over—the committee holds an open call for new members, encouraging self-nominations. Committee members whose terms are over are eligible for renomination.
-
 Committee members do not need to be deep technical Haskell experts.  Instead we look for enthusiasm towards improving the Haskell community.  We aim to represent the different facets of the community.  We aim to be diverse in terms of industry or research, and in terms of gender, race and location.
 
+### Process
+
+* The committee's governing rules are laid out in the [Board Resolution](https://wiki.haskell.org/wikiupload/9/9c/Haskell-org-board-res.pdf) of that month.
+* The committee uses the [haskell-community][list] for public discussion, where all interested parties may participate.
+* Proposals and meeting notes are stored in a [public repository][repo].
+* The committee 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.
+
+#### Committee Membership
+
+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.
+
+In November of each year — or if a member steps down before their term is over — the committee holds an open call for new members, encouraging self-nominations. Committee members whose terms are over are eligible for renomination.
+
 After nominations have been solicited, the current committee—including any outgoing members—selects new members with a simple majority vote.
 
 While this has never occurred in the past, Committee members can also be removed by majority vote.
 
-### Process
 
-The Committee uses the [haskell-community][list] for public discussion.  Proposals and meeting notes are stored in a [public repository][repo].
+### History
 
-### Contact
+Haskell.org is incorporated in the state of New York as of November 2015.
 
-  * [committee@haskell.org][email]: directly email the committee
-  * [haskell-community mailing list][list]: public discussions about the committee and Haskell community infrastructure
-  * [GitHub][github]: issues, suggestions and pull requests for the website
+The Haskell.org committee was [initially formed in November 2010](https://mail.haskell.org/pipermail/haskell/2010-November/022375.html). As described there:
+
+    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.
+
+[discourse]: https://discourse.haskell.org
 [email]: mailto:[email protected]
-[list]: https://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
+[Hackage]: https://hackage.haskell.org/
+[Hoogle]: https://hoogle.haskell.org/
+[GHC]: https://www.haskell.org/ghc/
 [github]: https://github.com/haskell-infra/www.haskell.org/
+[list]: https://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
+[mailing]: https://www.haskell.org/mailing-lists/
 [repo]: https://github.com/haskell-org/committee
+[gsoc]: https://summer.haskell.org/
+[wiki]: https://wiki.haskell.org/Haskell