[ghc-steering-committee] GHC 2020

[Richard Eisenberg]

It seems clear that my wiki idea isn't winning the day -- I never really liked it either. I'd be fine with either Eric's or Joachim's approaches. Maybe start with Joachim's approach and then use Eric's when Joachim's runs out of steam? A big minus, though, to Joachim's approach is that it seems hard to get good community involvement.

Richard

> On Sep 2, 2020, at 8:11 AM, Eric Seidel <eric at seidel.io> wrote:
> 
> Opening a regular discussion about whether and how we want to work on GHC 2020 sounds fine, that will also give the community a place to weigh in. I do think the eventual contents should be informed by the community though, it shouldn’t just be us working alone. 
> 
> Sent from my iPhone
> 
>> On Sep 2, 2020, at 03:16, Joachim Breitner <mail at joachim-breitner.de> wrote:
>> 
>> Hi,
>> 
>> sounds plausible. It would also allow us to use tags to easily indicate
>> the status (e.g. clearly-not, definitely-yes, kinda-contested…), and
>> then filter by issue to get the current list…
>> 
>> But before we go there, shouldn’t we maybe have a discussion first on
>> 
>> * do we even want that?
>> * what are the abstract criteria (or guidelines)?
>> * what is the process?
>> 
>> I believe that discussion could be done like any other proposal.
>> 
>> 
>> As for the process; when I brought up the idea, I was worried about us
>> spending huge resources discussion individual extensions to death, and
>> proposed, in the interest of efficiency and getting things done:
>> 
>>> The process could be: Every member can nominate any number of 
>>> extensions, to include, maybe a small rationale and then we do one 
>>> round of independent approval voting, requiring a supermajority to 
>>> really only pick uncontested extensions.
>> 
>> So instead of long debates, we start with GHC2020 being just those
>> extensions that a supermajority on the committee considers to be ok. 
>> 
>> This is much more lightweight process that we could get done in a week
>> or two (maybe using a doodle-like voting page). Maybe we would leave
>> out one or two extension that initially people are reserved about, but
>> could be swayed after lengthy discussions. But is that worth the
>> lengthy discussion?
>> 
>> 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
> 
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee