Re: GHC Steering Committee Call for Nominations

--===============6731595071445008933==
Content-Type: multipart/alternative; boundary="000000000000e50cc60642fe20d9"

--000000000000e50cc60642fe20d9
Content-Type: text/plain; charset="UTF-8"

I previously set the deadline to be 6 November (yesterday), but since I
inadvertently forgot to send out a reminder about the deadline, I'm going
to continue accepting nominations over the weekend. Nominations in my inbox
by *Sunday 9 November* (anywhere on Earth) will be considered.

Thanks
Simon

On Thu, 16 Oct 2025 at 15:04, Simon Marlow <[email protected]> wrote:

> 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
>

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

<div dir=3D"ltr"><div>I previously set the deadline to be 6 November (yeste=
rday), but since I inadvertently forgot to send out a reminder about the de=
adline, I&#39;m going to continue accepting nominations over the weekend. N=
ominations in my inbox by <b>Sunday 9 November</b> (anywhere on Earth) will=
 be considered.</div><div><br></div><div>Thanks</div><div>Simon</div></div>=
<br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, 16 Oct 2025 at 15:04, Simon Marlow &lt;<a href=3D"m=
ailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Dear Hask=
ellers,<br>
<br>
The GHC <span><span>Steering</span></span> <span><span>Committee</span></sp=
an> is seeking <span><span>nominations</span></span> for new members.<br><b=
r></div><div><b>To nominate yourself=C2=A0</b>please send an email to=C2=A0=
<a href=3D"mailto:[email protected]" target=3D"_blank">Simon Marlow &lt;ma=
[email protected]&gt;</a>,=C2=A0</div><div>briefly summarising your backgrou=
nd and relevant experience. See below for details</div><div>on what committ=
ee membership involves, and what kind of experience would be useful.<div><b=
r></div><div>DEADLINE: 6 November 2025</div></div><div><br></div><div><b>Wh=
at&#39;s the GHC steering committee?</b></div><div><b><br></b></div><div>Th=
e <span><span>committee</span></span> scrutinizes, debates and eventually d=
ecides 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" target=3D"_blank">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" target=3D"_blank"><span><span>Committee</span></span> bylaws</a>.</div><=
div><br></div><div><b>Who are we looking for?</b></div><div><br>We are look=
ing for members who have the ability to:<ul><li>understand GHC proposals (e=
.g. for new language extensions),</li><li>find holes and missing corner cas=
es in the specifications,</li><li>foresee the interaction with other langua=
ge or compiler features,</li><li>comment constructively and improve proposa=
ls through engagement with others,</li><li>judge the cost/benefit ratio of =
changes, and</li><li>come to a justifiable conclusion.</li></ul>
Ideally, <span><span>committee</span></span> members should:<br><ul><li>hav=
e substantial experience of writing or teaching Haskell;</li><li>have a tra=
ck record of active contributions to the Haskell community; or</li><li>have=
 expertise in language design and implementation, in either=C2=A0Haskell or=
 related languages.</li></ul></div><div>It is our aim that this committee b=
e diverse; by representing<br>different viewpoints, we will make decisions =
that benefit larger<br>segments of our community. Even if you are uncertain=
 whether your<br>background qualifies you for the role, you are warmly enco=
uraged to<br>apply.<br><br>The committee&#39;s work requires a small, but n=
on-trivial amount of time,<br>especially when you are assigned a proposal f=
or shepherding. We<br>estimate the workload to be around 2 hours per week, =
and our process<br>works best if members usually respond to technical email=
s within 1-2<br>weeks (within days is even better). Please keep that in min=
d if your<br>email inbox is already overflowing.</div><div><br></div><div>C=
ommittee members serve for 3 years, but are free to re-nominate</div><div>t=
hemselves when their 3-year term expires.</div><div><br></div><div>Self-nom=
inations are the norm. You can nominate someone else, but<br>please obtain =
their explicit consent to do so. (We don&#39;t want to<br>choose someone wh=
o turns out to be unable to serve.)<br><br><b>What happens after nomination=
s?</b></div><div><b><br></b></div><div>In accordance with our=C2=A0<a href=
=3D"https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rs=
t" target=3D"_blank"><span><span>Committee</span></span> bylaws</a>, the co=
mmittee=C2=A0deliberates=C2=A0</div><div>nominations=C2=A0<i><b>in private<=
/b></i>=C2=A0before 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>minimum of 9 members. There are currently two members rota=
ting off,</div><div>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>
</blockquote></div>

--000000000000e50cc60642fe20d9--

--===============6731595071445008933==
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]

--===============6731595071445008933==--