[ghc-steering-committee] Solicitation for a new member

[Joachim Breitner]

Hi,

thanks for all your feedback. Here is an updated draft – basically
Simons version, with the explicit time and responsiveness requirements
that Richard mentined, and I took the liberty of putting “education”
next to “real-world production use”. Will send this out in a day or
two.

Cheers,
Joachim

=====
Dear community,

the GHC Steering committee is seeking nomination for a new member, and
ask for self-nominations.

The committee scrutinizes, nitpicks, improves, weights 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 in the README in
https://github.com/ghc-proposals/ghc-proposals
which is also the GitHub repository where proposals are proposed.

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,
 * make constructive comments and improvements,
 * 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 language, which they can share with us.

The GHC developers themselves are already well represented already.  We
seek Haskell _users_ more than GHC hackers.

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. Please keep that in mind if your email inbox is already
overflowing.

There is no shortage of people who are very eager to get fancy new
features into the language, both in the committee and the wider
community. But each new feature imposes a cost, to implement, to learn,
(particularly) through its unexpected interaction with other features.
We need to strike a balance, one that encourages innovation (as Haskell
always has) while still making Haskell attractive for real-world
production use and for teaching. We therefore explicitly invite
“conservative” members of the community to join the committee.

To nominate yourself, please send an email to me (as the committee
secretary) at mail at joachim-breitner.de until July 23th. I will
distribute the nominations among the committee, and we will keep the
nominations and our deliberations private.

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

On behalf of the committee,
Joachim Breitner

=====
-- 
Joachim Breitner
  mail at joachim-breitner.de
  http://www.joachim-breitner.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20180709/0f6aa4c8/attachment.sig>