<div dir="ltr">Hello,<div><br></div><div>I like the simple process, however I think I'd prefer a bit more discussion in phase 2,when we know the current tallies, and also I think we should give ourselves the option to decide *not* to have GHC2020---it seems odd that this is a proposal that is phrased as "we are definitely going to end up with GHC 2020, we just don't know what's in it :-)</div><div><br></div><div>-Iavor</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 13, 2020 at 5:41 AM Spiwack, Arnaud <<a href="mailto:arnaud.spiwack@tweag.io">arnaud.spiwack@tweag.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Joachim puts his opinion quite eloquently and convincingly :-)</div><div><br></div><div>I was initially in favour of one conversation space by proposed extension, but, at least for the first round this is likely to be overwhelming. At least, I haven't found or seen, yet, a way to make this manageable. So let me vote with the majority opinion here.</div><div><br></div><div>Let's see how it goes really, if it doesn't work out how we expected this time around, we can change the process for the next iteration.</div><div><br></div>/Arnaud</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 10, 2020 at 8:11 PM Eric Seidel <<a href="mailto:eric@seidel.io" target="_blank">eric@seidel.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks Alejandro and Joachim for pushing this forward!<br>
<br>
I also suggested a heavier process along the lines of (2) at some point, but after reading the proposal and Joachim's argument here, I feel comfortable with (1) as well.<br>
<br>
Also, I think @AntC2 made a good point about -fglasgow-exts on the PR [1]. For the initial round it would be useful to list the extensions enabled by -fglasgow-exts as a reference point.<br>
<br>
[1]: <a href="https://github.com/ghc-proposals/ghc-proposals/pull/372#issuecomment-716066900" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/372#issuecomment-716066900</a><br>
<br>
On Tue, Nov 10, 2020, at 06:18, Simon Peyton Jones via ghc-steering-committee wrote:<br>
> | Is anyone not in favor of this proposal, or has questions, or shall we<br>
> | declare consensus and merge it?<br>
> <br>
> In my message of 4 Nov, I asked for feedback within "a week or two". <br>
> Let's set a deadline of the end of this week.<br>
> <br>
> All: please respond before then, if you want to.<br>
> <br>
> I don't think this is terribly controversial, so I'll take silence as assent.<br>
> <br>
> All this assuming we adopt Alternative 1.<br>
> <br>
> Simon<br>
> <br>
> | -----Original Message-----<br>
> | From: ghc-steering-committee <<a href="mailto:ghc-steering-committee-bounces@haskell.org" target="_blank">ghc-steering-committee-bounces@haskell.org</a>> On<br>
> | Behalf Of Joachim Breitner<br>
> | Sent: 09 November 2020 16:28<br>
> | To: <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
> | Subject: Re: [ghc-steering-committee] GHC 20xx process<br>
> | <br>
> | Hi,<br>
> | <br>
> | Am Freitag, den 06.11.2020, 19:55 +0000 schrieb Richard Eisenberg:<br>
> | > This is an effective argument; you've changed my mind.<br>
> | ><br>
> | > I'm now in favor of Joachim's simpler process.<br>
> | <br>
> | thanks, also for making me get more clarity on this as well.<br>
> | <br>
> | Is anyone still preferring Alternative 2, or should we take it off the<br>
> | table?<br>
> | <br>
> | Is anyone not in favor of this proposal, or has questions, or shall we<br>
> | declare consensus and merge it?<br>
> | <br>
> | <br>
> | It seems that now is a good time to then actually do the first iteration of<br>
> | the process – the State of Haskell survey data, once out, will be fresh, and<br>
> | we'd be well in time for inclusion in the Spring release of GHC, likely 9.1<br>
> | (unless the 9.0 delay shifts things around… oh well, let’s just make sure we<br>
> | have GHC2021 defined before or near the start of 2021, not late in that year<br>
> | :-))<br>
> | <br>
> | Cheers,<br>
> | Joachim<br>
> | <br>
> | --<br>
> | Joachim Breitner<br>
> | <a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
> | <br>
> | <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joachim" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joachim</a><br>
> | -<br>
> | <a href="http://breitner.de" rel="noreferrer" target="_blank">breitner.de</a>%2F&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7C125f812494db4225<br>
> | 0f4808d884cc8403%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C63740536191896<br>
> | 4507%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1<br>
> | haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BfuHY7eCNyF5QlP7BfXDrNjxgWhoj%2FGI92S<br>
> | esCy1gLA%3D&reserved=0<br>
> | <br>
> | <br>
> | _______________________________________________<br>
> | ghc-steering-committee mailing list<br>
> | <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
> | <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haske" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haske</a><br>
> | <a href="http://ll.org" rel="noreferrer" target="_blank">ll.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
> | committee&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7C125f812494db42250f480<br>
> | 8d884cc8403%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C637405361918974502%<br>
> | 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi<br>
> | LCJXVCI6Mn0%3D%7C3000&sdata=TyxdMqz%2FXFY9WYgZKdUHkFSQEvqRMJdoVEajh39JNs<br>
> | A%3D&reserved=0<br>
> _______________________________________________<br>
> ghc-steering-committee mailing list<br>
> <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
> <a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
><br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>