<div dir="ltr"><div>Dear all,</div><div>I would really like to move this forward, and I would be happy to put some work on it.</div><div><br></div><div>What do you think of the following plan?</div><div>- Create a ghc-proposal based on the (awesome) wiki page by Richard. I think the criteria in the wiki are quite nice. Explain that one of the goals is to encompass as many stable extensions as possible.</div><div>- Reformat the list to make 3 tables: one for extensions which satisfy all 5 criteria, one for extensions we want to include even if they don't, and one for those which should be rejected in the light of those criteria.</div><div><br></div><div>If the process works well, we could think about instaurating a yearly/bi-yearly/n-yearly process to create new -XGHC20XX versions.</div><div><br></div><div>Regards,</div><div>Alejandro<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El lun., 7 sept. 2020 a las 17:32, Simon Peyton Jones via ghc-steering-committee (<<a href="mailto:ghc-steering-committee@haskell.org">ghc-steering-committee@haskell.org</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Just back from holiday. Some thoughts<br>
<br>
* I don’t think this mailing list is the best place for the<br>
discussion. Basically, it's a GHC Proposal, so someone (possibly<br>
a committee member, possibly not) should write a proposal,<br>
and we should put it through the process.<br>
<br>
* We should advertise the criteria, as Richard has done on the<br>
wiki page.<br>
<br>
* Any such proposal should be informed by data. Notably, extension usage<br>
in Hackage, or perhaps Stackage (since it's a bit more curated).<br>
<br>
* A proposer might also want to run a public poll, as an additional<br>
source of data<br>
<br>
* When it comes to the committee, we can (I guess) vote on individual<br>
extensions, rather than just accept/reject the whole thing.<br>
<br>
I am intrigued by the idea of using Kialo to coordinate discussion.<br>
Maybe it'd work better than GitHub? Are there other alternatives?<br>
But that's orthogonal to the GHC 2020 idea; let's not conflate them.<br>
<br>
Simon<br>
<br>
| -----Original Message-----<br>
| From: ghc-steering-committee <ghc-steering-committee-<br>
| <a href="mailto:bounces@haskell.org" target="_blank">bounces@haskell.org</a>> On Behalf Of Richard Eisenberg<br>
| Sent: 02 September 2020 14:57<br>
| To: Eric Seidel <<a href="mailto:eric@seidel.io" target="_blank">eric@seidel.io</a>><br>
| Cc: <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
| Subject: Re: [ghc-steering-committee] GHC 2020<br>
| <br>
| It seems clear that my wiki idea isn't winning the day -- I never<br>
| really liked it either. I'd be fine with either Eric's or Joachim's<br>
| approaches. Maybe start with Joachim's approach and then use Eric's<br>
| when Joachim's runs out of steam? A big minus, though, to Joachim's<br>
| approach is that it seems hard to get good community involvement.<br>
| <br>
| Richard<br>
| <br>
| > On Sep 2, 2020, at 8:11 AM, Eric Seidel <<a href="mailto:eric@seidel.io" target="_blank">eric@seidel.io</a>> wrote:<br>
| ><br>
| > Opening a regular discussion about whether and how we want to work on<br>
| GHC 2020 sounds fine, that will also give the community a place to<br>
| weigh in. I do think the eventual contents should be informed by the<br>
| community though, it shouldn’t just be us working alone.<br>
| ><br>
| > Sent from my iPhone<br>
| ><br>
| >> On Sep 2, 2020, at 03:16, Joachim Breitner <mail@joachim-<br>
| <a href="http://breitner.de" rel="noreferrer" target="_blank">breitner.de</a>> wrote:<br>
| >><br>
| >> Hi,<br>
| >><br>
| >> sounds plausible. It would also allow us to use tags to easily<br>
| indicate<br>
| >> the status (e.g. clearly-not, definitely-yes, kinda-contested…), and<br>
| >> then filter by issue to get the current list…<br>
| >><br>
| >> But before we go there, shouldn’t we maybe have a discussion first<br>
| on<br>
| >><br>
| >> * do we even want that?<br>
| >> * what are the abstract criteria (or guidelines)?<br>
| >> * what is the process?<br>
| >><br>
| >> I believe that discussion could be done like any other proposal.<br>
| >><br>
| >><br>
| >> As for the process; when I brought up the idea, I was worried about<br>
| us<br>
| >> spending huge resources discussion individual extensions to death,<br>
| and<br>
| >> proposed, in the interest of efficiency and getting things done:<br>
| >><br>
| >>> The process could be: Every member can nominate any number of<br>
| >>> extensions, to include, maybe a small rationale and then we do one<br>
| >>> round of independent approval voting, requiring a supermajority to<br>
| >>> really only pick uncontested extensions.<br>
| >><br>
| >> So instead of long debates, we start with GHC2020 being just those<br>
| >> extensions that a supermajority on the committee considers to be ok.<br>
| >><br>
| >> This is much more lightweight process that we could get done in a<br>
| week<br>
| >> or two (maybe using a doodle-like voting page). Maybe we would leave<br>
| >> out one or two extension that initially people are reserved about,<br>
| but<br>
| >> could be swayed after lengthy discussions. But is that worth the<br>
| >> lengthy discussion?<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.jo" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jo</a><br>
| achim-<br>
| <a href="http://breitner.de" rel="noreferrer" target="_blank">breitner.de</a>%2F&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cfa6e3a6bcdf<br>
| 04ed5611208d84f480f21%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373<br>
| 46518199468575&sdata=ABgJCFijwzYszRybc0kReMPdR7oSLzC1nV1xJYSlxQ0%3D<br>
| &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>
| >><br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a>.<br>
| <a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cfa6e3a6bcdf04ed5<br>
| 611208d84f480f21%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637346518<br>
| 199468575&sdata=H1hFiX8qnuf%2FlYeNXfEE5j5Aik3dlVvsujoHOt%2FHTnw%3D&<br>
| amp;reserved=0<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>
| ><br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a>.<br>
| <a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cfa6e3a6bcdf04ed5<br>
| 611208d84f480f21%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637346518<br>
| 199468575&sdata=H1hFiX8qnuf%2FlYeNXfEE5j5Aik3dlVvsujoHOt%2FHTnw%3D&<br>
| amp;reserved=0<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" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a>.<br>
| <a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cfa6e3a6bcdf04ed5<br>
| 611208d84f480f21%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637346518<br>
| 199468575&sdata=H1hFiX8qnuf%2FlYeNXfEE5j5Aik3dlVvsujoHOt%2FHTnw%3D&<br>
| amp;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>
</blockquote></div>