[ghc-steering-committee] committee constitution

[Iavor Diatchki]

I am not really keen on putting these labels on folks, so my preference
would be to not bake this into the process.

I am also not sure what problem we are solving though.

Iavor


On Wed, Jun 24, 2020, 04:58 Joachim Breitner <mail at joachim-breitner.de>
wrote:

> Hi,
>
> Am Mittwoch, den 24.06.2020, 11:57 +0100 schrieb Richard Eisenberg:
> >  A. By having shepherds reach out to community members external to the
> committee who can share their expert opinion
> >  B. By maintaining a list of constituencies that the committee
> membership covers (ideally)
> >
> > These can be combined, or we could do neither. (Right now, we do
> neither.)
>
> I think we have sometimes used A. For example with the proposal about
> Arrow something, we (or the author?) reached out the likely affected
> library authors.
>
> I am slightly favoring A (less formal, less process overhead, maybe
> more flexible).
>
> Cheers,
> Joachim
>
> --
> Joachim Breitner
>   mail at joachim-breitner.de
>   http://www.joachim-breitner.de/
>
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20200624/737fbdd8/attachment.html>