[ghc-steering-committee] GHC 2020

[Alejandro Serrano Mena]

I would really like this effort not to die, so I've given the proposal
another push. Following the comments from Simon and Joachim, I've re-framed
the proposal as laying down a process to create new "language versions"
yearly. The idea is to have one of these every year (or 2, or 3, whatever
is decided), coinciding with the spring release of GHC.
https://github.com/serras/ghc-proposals/blob/ghc-2020/proposals/0000-ghc-2020.md

I think it's important for the community to be involved in the process. If
it's clear that an extension is loved by most of the community, that's a
big plus for acceptance. In addition, if we come with a list ourselves, we
risk having made choices which only show our (biased) point of view.

Since in the first round the possible list of extensions may be quite big,
we might introduce a "fast-lane process" for this one time, for extensions
like EmptyDataDecls or different number formats which seem to have
unanimous support.

Looking forward to hearing from all of you,
Alejandro

El lun., 5 oct. 2020 a las 12:07, Joachim Breitner (<
mail at joachim-breitner.de>) escribió:

> Hi,
>
> Am Montag, den 05.10.2020, 10:21 +0100 schrieb Simon Marlow:
> > > Personally, I would also like to come up with general guidance. Do
> > > we expect *any* extension fulfilling the criteria to be included?
> > >
> >
> > Let's be conservative: if there's controversy around a particular
> > extension, default to not including it in GHC2020.
>
> that was a core idea of my original process proposal:
>
> Without long, time-consuming and process-heavy debate around each
> extension, let’s all of us individually assemble a list of extensions,
> and turn that into GHC2020. (Maybe for extensions that were not on the
> list by only one or two give them a chance to reconsider).
>
> This way there is still a chance that it'd become GHC2020, and not
> GHC2021 or GHC2022, or just fizzle…
>
> And it would hopefully be the a GHC2020 that contains all the low-
> hanging, non-controversial fruit. This also means that GHC2020 has a
> good chance of actually getting used. Which means for the work for
> GHC2021, picking the next set of extensions, is actually relevant and
> meaningful.
>
>
> And if something doesn’t make it into GHC2020 that maybe should have?
> No big deal, as Simon says.
>
> 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/20201017/5cfc0ab1/attachment.html>