[ghc-steering-committee] GHC2024 committee deliberation
Chris Dornan
chris at chrisdornan.com
Thu Nov 23 04:33:42 UTC 2023
Joachim,
Gathering some data might be a good idea, provided the secretary is banned from doing this! (I mean it is really, really bad idea to load up the secretary with these kinds of activities.)
I am not in favour of polling. We collect that kind of data in the survey -- can we not use that?
Advertising the ghc-proposal issue in the usual places should be sufficient. Otherwise I fear we would be inviting problems and poor decisions.
Chris
> On 22 Nov 2023, at 20:25, Joachim Breitner <mail at joachim-breitner.de> wrote:
>
> Hi,
>
> it was brought to my attention that the proposal that introduced
> GHC20xx actually laid out a specific process to decide about the next
> GHC20xx:
> https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0372-ghc-extensions.rst#process
>
> This includes “secretary tallies usage on Hackage” and “secretary runs
> a public poll”, and also wants to do all these things on _all_
> extensions, instead on focusing on those that least someone nominates,
> and requires every committee member to independently propose a set of
> extensions.
>
> I’m not sure to what extend we should tie ourselves to a process we
> imagined three years ago. But if anyone things we should do one of
> these things, we can.
>
> I guess I could at least do a simple poll on discourse with the
> currently proposed extensions.
>
> 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
More information about the ghc-steering-committee
mailing list