<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Thanks for initiating this, Joachim.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I have made some small suggested adjustments, below. (Needs a bit of paragraph filling.)<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Simon</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
<pre>Dear Haskell community,
the GHC Steering committee is seeking nominations for at least two new
members.
The committee scrutinizes, nitpicks, improves, <span style="background-color:rgb(255,255,0)">weighs </span>and eventually
accepts or rejects proposals that extend or change the language
supported by GHC and other (public-facing) aspects of GHC.
Our processes are described at
<a href="https://github.com/ghc-proposals/ghc-proposals">https://github.com/ghc-proposals/ghc-proposals</a>
which is also the GitHub repository where proposals are proposed. In
particular, please have a look at the bylaws at
<a href="https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst">https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst</a>
<br>
We are looking for a member who has the ability
* to understand such language extension proposals,
* to find holes and missing corner cases in the specifications,
* foresee the interaction with other language features and
specifications,
* comment constructively and improve the proposals,
* judge the cost/benefit ratio and
* finally come to a justifiable conclusion.
We look for committee members who have some of these properties:
* have substantial experience in writing Haskell applications or
libraries, which they can use to inform judgements about the
utility or otherwise of proposed features,
* have made active contributions to the Haskell community, for
some time,
* have expertise in language design and implementation, in either
Haskell or related languages, which they can share with us.
There is no shortage of people who are eager to get fancy new
features into the language, both in the committee and the wider
community. <span style="background-color:rgb(255,255,0)">But each new feature imposes a cost, to implement, to maintain<br>in perpetuity in GHC's code base, to learn,
and to deal with its unexpected interaction with other features.
We need to strike a balance, one that encourages innovation (as GHC
always has) while still making Haskell attractive for real-world
production use and for teaching. We therefore seek a balance of<br>background, expertise, and views on the committee.</span>
<span style="background-color:rgb(255,255,0)">Membership of the committee gives you the chance to influence the future<br>direction of Haskell, and to serve the Haskell community.</span>
The committee’s work requires a small, but non-trivial amount of time,
especially when you are assigned a proposal for shepherding. We
estimate the workload to be around 2 hours per week, and our process
works best if members usually respond to technical emails within 1-2
weeks (within days is even better). Please keep that in mind if your
email inbox is already overflowing.
To make a nomination, please send an email to me (as the committee
secretary) at <a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee">mail at joachim-breitner.de</a> until February 11th. I will
distribute the nominations among the committee, and we will keep the
nominations and our deliberations private.
We explicitly encourage self-nominations. You can nominate others, but
please obtain their explicit consent to do so. (We don’t want to choose
someone who turns out to be unable to serve.)
</pre>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 2 Oct 2022 at 12:54, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Committee,<br>
<br>
with Baldurs resignation, we now have 8 non-expiring member (Arnaud’s<br>
term has expired in July) and we ought to do a new call for<br>
nominations. Arnaud is of course very welcome to re-nominate himself,<br>
and I personally hope he will.<br>
<br>
Do you have any suggestions for improvements to the process?<br>
This is the mail I sent around last time – do you want to to change<br>
anything there?<br>
<a href="https://mail.haskell.org/pipermail/ghc-steering-committee/2022-January/002711.html" rel="noreferrer" target="_blank">https://mail.haskell.org/pipermail/ghc-steering-committee/2022-January/002711.html</a><br>
<br>
Should I maybe remove the paragraph asking for “conservative members”?<br>
<br>
Also maybe think of people you’d personally like to nudge to apply.<br>
<br>
Cheers,<br>
Joachim<br>
<br>
<br>
<br>
<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank">http://www.joachim-breitner.de/</a><br>
<br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>