- ghc-steering-committee

Please review #167: Deprecated Entities, Shepherd: Vitaly
by Joachim Breitner 21 Jan '19

21 Jan '19

Dear Committee, this is your secretary speaking: Adding namespaces to DEPRECATED has been proposed by Alex Dudarenko: https://github.com/ghc-proposals/ghc-proposals/pull/167 https://github.com/nineonine/ghc-proposals/blob/depr-entities/proposals/000… I propose Vitaly Bragilevsky as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Status
by Joachim Breitner 16 Dec '18

16 Dec '18

Dear committee, ’tis the season – but not for committee work, it seems. Well, here is what happened: * were asked to review these proposals: #158 The HasField-setfield proposal (shepherd: Iavor) * got a recommendation from shepherds about: #175 Lift.liftTyped (rec: accept) * decided about the following proposals -none- We currently have to act on the following 7 proposals, one up from last time. Most saw no activity in the last month! liftTyped https://github.com/ghc-proposals/ghc-proposals/pull/175 Shepherd: Ben Status: Acceptance recommended, but a discussion ensured and did not conclude. Ben, Eric, what is the status. record-set-field proposal https://github.com/ghc-proposals/ghc-proposals/pull/158 Shepherd: Yav Status: Waiting for a recommendation. Type annotated quoters https://github.com/ghc-proposals/ghc-proposals/pull/125 Shepherd: Manuel Status: Still waiting for recommendation. Manuel? Provenance-Qualified Package Imports https://github.com/ghc-proposals/ghc-proposals/pull/115 Shepherd: Ben Status: Still waiting for recommendation. This is pretty old! ExtraCommas https://github.com/ghc-proposals/ghc-proposals/pull/87 Shepherd: Chris Recommendation: accept Status: Met with some reservation. Chris, please pick this up again. Or-Patterns https://github.com/ghc-proposals/ghc-proposals/pull/43 Shepherd: Manuel Recommendation: accept Status: Round 2 discussion ebbed down. Manuel, can you conclude this? Bundling patterns with synonyms https://github.com/ghc-proposals/ghc-proposals/pull/28 Shepherd: Chris Recommendation: reject Status: Chris, you still need to write the rejection reasons to the ticket. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Please review #158: HasField-setField, Shepherd: Iavor
by Joachim Breitner 16 Dec '18

16 Dec '18

Dear Committee, this is your secretary speaking: Adding `setField` to `HasField` has been proposed by Neil Mitchell: https://github.com/ghc-proposals/ghc-proposals/pull/158 https://github.com/ndmitchell/ghc-proposals/blob/patch-1/proposals/0000-rec… I propose Iavor as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Guidelines for respectful communication
by Simon Peyton Jones 08 Dec '18

08 Dec '18

Friends As many of you will know, I have been concerned for several years about the standards of discourse in the Haskell community. I think things have improved since the period that drove me to write my Respect email<https://mail.haskell.org/pipermail/haskell/2016-September/024995.html>, but it's far from secure. We discussed this at a meeting of the GHC Steering Committee<https://github.com/ghc-proposals/ghc-proposals> at ICFP in September, and many of us have had related discussions since. Arising out of that conversation, the GHC Steering Committee has decided to adopt these Guidelines for respectful communication<https://github.com/ghc-proposals/ghc-proposals/blob/master/GRC.rst> We are not trying to impose these guidelines on members of the Haskell community generally. Rather, we are adopting them for ourselves, as a signal that we seek high standards of discourse in the Haskell community, and are willing to publicly hold ourselves to that standard, in the hope that others may choose to follow suit. We are calling them "guidelines for respectful communication" rather than a "code of conduct", because we want to encourage good communication, rather than focus on bad behaviour. Richard Stallman's recent post<https://lwn.net/Articles/769167/> about the new GNU Kind Communication Guidelines<https://gnu.org/philosophy/kind-communication.html> expresses the same idea. Meanwhile, the Stack community is taking a similar approach<https://www.snoyman.com/blog/2018/11/proposal-stack-coc>. Our guidelines are not set in stone; you can comment here<https://github.com/ghc-proposals/ghc-proposals/commit/373044b5a78519071b9a2…>. Perhaps they can evolve so that other Haskell committees (or even individuals) feel able to adopt them. The Haskell community is such a rich collection of intelligent, passionate, and committed people. Thank you -- I love you all! Simon

2 1

Guidelines for respectful communication
by Simon Peyton Jones 04 Dec '18

04 Dec '18

Friends on the GHC steering group Joachim has published our new guidelines, here https://github.com/ghc-proposals/ghc-proposals/blob/master/GRC.rst I'll send an email to ... what... ghc-users and ghc-devs perhaps. Simon

1 0

GHC proposals
by Simon Peyton Jones 03 Dec '18

03 Dec '18

Joachim * Could we add a tag for "Implemented" so that we can have convenient lists for "accepted and implemented" vs "accepted and not yet implemented"? Easy, and valuable. * The "under discussion" list seems terribly short - only two proposals! https://github.com/ghc-proposals/ghc-proposals/pulls?q=is%3Aopen+is%3Apr+no… There are tons of proposals under discussion! What's wrong? Thanks Simon

3 7

Please review #175: Lift.liftTyped, Shepherd: Ben Gamari
by Joachim Breitner 05 Nov '18

05 Nov '18

Dear Committee, this is your secretary speaking: Add `liftTyped` to the `Lift` typeclass, by Alec Theriault, was proposed https://github.com/ghc-proposals/ghc-proposals/pull/175 https://github.com/harpocrates/ghc-proposals/blob/lift-typed/proposals/0000… I propose Ben as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

3 2

Status
by Joachim Breitner 05 Nov '18

05 Nov '18

Dear committee, This was a quiet, but very productive month. Since the last status update, we * were asked to review these proposals: #173 The dot type operator (shepherd: Eric) #174 lower precedence for UNPACK (shepherd: Joachim) #166 List instances in ghci (shepherd: Iavor) #175 liftTyped (shepherd: Ben) * got a recommendation from shepherds about: #170 Unrestricted OverloadedLables (rec: accept) #28 Bundling patterns with type synonyms (rec changed to reject) #174 lower precedence for UNPACK (rec: accept) #173 The dot type operator (rec: accept) #111 Linear types (rec: conditional accept) #166 List instances in ghci (rec: accept) * decided about the following proposals #174 lower precedence for UNPACK (accept) #168 fail with Overloaded Strings (accept) #173 The dot type operator (accept) #170 Unrestricted OverloadedLables (accept) #111 Linear types (rec: conditional accept) #166 List instances in ghci (accept) We currently have to act on the following 6 proposals, 3 less than last round, continuing a pleasant downward trend. liftTyped https://github.com/ghc-proposals/ghc-proposals/pull/175 Shepherd: Ben Status: Waiting for recommendation. Type annotated quoters https://github.com/ghc-proposals/ghc-proposals/pull/125 Shepherd: Manuel Status: Still waiting for recommendation. Manuel? Provenance-Qualified Package Imports https://github.com/ghc-proposals/ghc-proposals/pull/115 Shepherd: Ben Status: Still waiting for recommendation. This is pretty old! ExtraCommas https://github.com/ghc-proposals/ghc-proposals/pull/87 Shepherd: Chris Recommendation: accept Status: Met with some reservation. Chris, what is the status of discussion? Or-Patterns https://github.com/ghc-proposals/ghc-proposals/pull/43 Shepherd: Manuel Recommendation: accept Status: Round 2 discussion ebbed down. Manuel? Bundling patterns with synonyms https://github.com/ghc-proposals/ghc-proposals/pull/28 Shepherd: Chris Recommendation: reject Status: Rejection imminent Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Discussion: List instances for a type in GHCi #166
by Iavor Diatchki 05 Nov '18

05 Nov '18

Hello, I'd like to start the discussion about feature request #166, "List instances for a type in GHCi". In short, the idea is that we add a new command to GHCi, `:instances TYPE`, which given a type, will show the list of instances---for any class---that could be used with this type. It seems like this could be a potentially handy thing to do, and it doesn't really interfere with anything else, so I recommend that we accept it. Please let me know what you think. -Iavor

3 2

Proposal #170: Unrestricted OverloadedLabels (was: Uppercase OverloadedLabels), rec: accept
by Vitaly Bragilevsky 05 Nov '18

05 Nov '18

Hi all, The proposal #170: Unrestricted OverloadedLabels (was: Uppercase OverloadedLabels) (https://github.com/ghc-proposals/ghc-proposals/pull/170) was updated to allow any nonempty alphanumeric string following a # under OverloadedLabels. So I repeat my recommendation to accept it. Please speak up within a week if you have any concerns. Silence is understood as agreement. Regards, Vitaly

2 1