GHC Steering Committee Call for Nominations

--===============8160735974535367473==
Content-Type: multipart/alternative; boundary="0000000000004349a206414718ca"

--0000000000004349a206414718ca
Content-Type: text/plain; charset="UTF-8"

Dear Haskellers,

The GHC Steering Committee is seeking nominations for new members.

*To nominate yourself *please send an email to Simon Marlow
<[email protected]> <[email protected]>,
briefly summarising your background and relevant experience. See below for
details
on what committee membership involves, and what kind of experience would be
useful.

DEADLINE: 6 November 2025

*What's the GHC steering committee?*

The committee scrutinizes, debates and eventually decides to accept or
reject proposals to change the language or major features supported by
GHC. Our processes are described in the GitHub repository
<https://github.com/ghc-proposals/ghc-proposals> where
proposals are submitted. In particular, please have a look at the Committee
bylaws
<https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst>.

*Who are we looking for?*

We are looking for members who have the ability to:

   - understand GHC proposals (e.g. for new language extensions),
   - find holes and missing corner cases in the specifications,
   - foresee the interaction with other language or compiler features,
   - comment constructively and improve proposals through engagement with
   others,
   - judge the cost/benefit ratio of changes, and
   - come to a justifiable conclusion.

Ideally, committee members should:

   - have substantial experience of writing or teaching Haskell;
   - have a track record of active contributions to the Haskell community;
   or
   - have expertise in language design and implementation, in
   either Haskell or related languages.

It is our aim that this committee be diverse; by representing
different viewpoints, we will make decisions that benefit larger
segments of our community. Even if you are uncertain whether your
background qualifies you for the role, you are warmly encouraged to
apply.

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.

Committee members serve for 3 years, but are free to re-nominate
themselves when their 3-year term expires.

Self-nominations are the norm. You can nominate someone else, but
please obtain their explicit consent to do so. (We don't want to
choose someone who turns out to be unable to serve.)

*What happens after nominations?*

In accordance with our Committee bylaws
<https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst>,
the committee deliberates
nominations *in private* before communicating the decision.

The committee doesn't have a fixed size, although we like to have a
minimum of 9 members. There are currently two members rotating off,
but as the committee currently has 10 members, we will be looking to
appoint at least one but possibly (hopefully!) more.

On behalf of the committee,

Simon Marlow

--0000000000004349a206414718ca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear Haskellers,<br>
<br>
The GHC <span class=3D"gmail-il"><span class=3D"gmail-il">Steering</span></=
span> <span class=3D"gmail-il"><span class=3D"gmail-il">Committee</span></s=
pan> is seeking <span class=3D"gmail-il"><span class=3D"gmail-il">nominatio=
ns</span></span> for new members.<br><br></div><div><b>To nominate yourself=
=C2=A0</b>please send an email to=C2=A0<a href=3D"mailto:[email protected]=
">Simon Marlow &lt;[email protected]&gt;</a>,=C2=A0</div><div>briefly summ=
arising your background and relevant experience. See below for details</div=
><div>on what committee membership involves, and what kind of experience wo=
uld be useful.<div><br></div><div>DEADLINE: 6 November 2025</div></div><div=
><br></div><div><b>What&#39;s the GHC steering committee?</b></div><div><b>=
<br></b></div><div>The <span class=3D"gmail-il"><span class=3D"gmail-il">co=
mmittee</span></span> scrutinizes, debates and eventually decides to accept=
 or <br>
reject proposals to change the language or major features supported by <br>
GHC. Our processes are described in the <a href=3D"https://github.com/ghc-p=
roposals/ghc-proposals">GitHub repository</a> where <br>
proposals are submitted. In particular, please have a look at the <a href=
=3D"https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rs=
t"><span class=3D"gmail-il"><span class=3D"gmail-il">Committee</span></span=
> bylaws</a>.</div><div><br></div><div><b>Who are we looking for?</b></div>=
<div><br>We are looking for members who have the ability to:<ul><li>underst=
and GHC proposals (e.g. for new language extensions),</li><li>find holes an=
d missing corner cases in the specifications,</li><li>foresee the interacti=
on with other language or compiler features,</li><li>comment constructively=
 and improve proposals through engagement with others,</li><li>judge the co=
st/benefit ratio of changes, and</li><li>come to a justifiable conclusion.<=
/li></ul>
Ideally, <span class=3D"gmail-il"><span class=3D"gmail-il">committee</span>=
</span> members should:<br><ul><li>have substantial experience of writing o=
r teaching Haskell;</li><li>have a track record of active contributions to =
the Haskell community; or</li><li>have expertise in language design and imp=
lementation, in either=C2=A0Haskell or related languages.</li></ul></div><d=
iv>It is our aim that this committee be diverse; by representing<br>differe=
nt viewpoints, we will make decisions that benefit larger<br>segments of ou=
r community. Even if you are uncertain whether your<br>background qualifies=
 you for the role, you are warmly encouraged to<br>apply.<br><br>The commit=
tee&#39;s work requires a small, but non-trivial amount of time,<br>especia=
lly when you are assigned a proposal for shepherding. We<br>estimate the wo=
rkload to be around 2 hours per week, and our process<br>works best if memb=
ers usually respond to technical emails within 1-2<br>weeks (within days is=
 even better). Please keep that in mind if your<br>email inbox is already o=
verflowing.</div><div><br></div><div>Committee members serve for 3 years, b=
ut are free to re-nominate</div><div>themselves when their 3-year term expi=
res.</div><div><br></div><div>Self-nominations are the norm. You can nomina=
te someone else, but<br>please obtain their explicit consent to do so. (We =
don&#39;t want to<br>choose someone who turns out to be unable to serve.)<b=
r><br><b>What happens after nominations?</b></div><div><b><br></b></div><di=
v>In accordance with our=C2=A0<a href=3D"https://github.com/ghc-proposals/g=
hc-proposals/blob/master/committee.rst"><span class=3D"gmail-il"><span clas=
s=3D"gmail-il">Committee</span></span> bylaws</a>, the committee=C2=A0delib=
erates=C2=A0</div><div>nominations=C2=A0<i><b>in private</b></i>=C2=A0befor=
e communicating the decision.=C2=A0</div><div><br></div><div>The committee =
doesn&#39;t have a fixed size, although we like to have a=C2=A0</div><div>m=
inimum of 9 members. There are currently two members rotating off,</div><di=
v>but as the committee currently has 10 members, we will be looking to</div=
><div>appoint at least one but possibly (hopefully!) more.</div><div><br></=
div><div>On behalf of the committee,</div><div><br>Simon Marlow<br></div></=
div>

--0000000000004349a206414718ca--

--===============8160735974535367473==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============8160735974535367473==--