| ... | ... | @@ -7,13 +7,13 @@ |
|
|
|
- John Launchbury
|
|
|
|
- Andres Löh \<loeh at iai.uni-bonn.de\>
|
|
|
|
- Ian Lynagh \<igloo at earth.li\>
|
|
|
|
- Simon Marlow (co-chair)
|
|
|
|
- Simon Marlow (co-editor)
|
|
|
|
- John Meacham \<john at repetae.net\>
|
|
|
|
- Ravi Nanavati \<ravi at bluespec.com\>
|
|
|
|
- Henrik Nilsson \<nhn at cs.nott.ac.uk\>
|
|
|
|
- Ross Paterson \<ross at soi.city.ac.uk\>
|
|
|
|
- Simon Peyton Jones \<simonpj at microsoft.com\>
|
|
|
|
- Don Stewart \<dons at cse.unsw.edu.au\> (co-chair)
|
|
|
|
- Don Stewart \<dons at cse.unsw.edu.au\> (co-editor)
|
|
|
|
- Audrey Tang \<autrijus at gmail.com\>
|
|
|
|
- Simon Thompson \<S.J.Thompson at kent.ac.uk\>
|
|
|
|
- Malcolm Wallace \<Malcolm.Wallace at cs.york.ac.uk\>
|
| ... | ... | @@ -34,11 +34,11 @@ Each committee is formed for the period of one year, starting after the announce |
|
|
|
|
|
|
|
The committee consists of
|
|
|
|
|
|
|
|
- a chair (or a pair of co-chairs), who are responsible for editing the final language report, and for guiding the process along.
|
|
|
|
- 1-2 editors, who are responsible for editing the final language report, and for guiding the process along.
|
|
|
|
- 10-15 members
|
|
|
|
|
|
|
|
|
|
|
|
Continuity is expected to be around 50% from year to year, and a particular member should participate in no more than two consecutive committees.
|
|
|
|
Continuity is expected to be no more than 50% from year to year, and a particular member should participate in no more than two consecutive committees.
|
|
|
|
|
|
|
|
|
|
|
|
The committee should represent each class of stakeholders with roughly equal weight. These classes are
|
| ... | ... | @@ -50,10 +50,16 @@ The committee should represent each class of stakeholders with roughly equal wei |
|
|
|
- Teachers
|
|
|
|
- Authors
|
|
|
|
|
|
|
|
|
|
|
|
In addition, members of the committee should be long-standing users with a deep knowledge of Haskell, and preferably with experience of language design. The committee should contain at least some members with a comprehensive knowledge of the dark corners of the Haskell language design, who can offer perspective and rationale for existing choices and comment on the ramifications of making different choices.
|
|
|
|
|
|
|
|
## Process for forming the next committee
|
|
|
|
|
|
|
|
|
|
|
|
(to be decided)
|
|
|
|
There will be a short period in which open nominations for new committee members will be solicited from the community on the haskell-prime@… mailing list. Self-nominations are allowed, and existing committee members can put themselves forward for the following year's committee, provided they don't serve more than two years in succession.
|
|
|
|
|
|
|
|
|
|
|
|
Following nominations, the existing committee will choose the core of a new committee, consisting of up to 10 members, up to 2 of whom are editors. Further committee members may be appointed by the core committee during the following months leading up to the committee discussion, based on the need for expertise in areas related to important proposals (which may in some cases mean appointing the proposer themselves, at the discretion of the committee).
|
|
|
|
|
|
|
|
## Responsibilities
|
|
|
|
|
| ... | ... | |