Personally I think it’s helpful to have the proposal and rationale in the public discussion thread, because that gives non-committee members a chance to contribute.  E.g. by supporting the recommendation or explaining why they think the recommendation is wrong.

 

Simon

 

From: ghc-steering-committee <ghc-steering-committee-bounces@haskell.org> On Behalf Of Simon Marlow
Sent: 02 December 2019 10:13
To: Joachim Breitner <mail@joachim-breitner.de>
Cc: ghc-steering-committee@haskell.org
Subject: [EXTERNAL] Re: [ghc-steering-committee] Please review #265: Unlifted Datatypes, Shepherd: Simon Marlow

 

On Thu, 28 Nov 2019 at 10:06, Joachim Breitner <mail@joachim-breitner.de> wrote:

Dear Committee,

this is your secretary speaking:

Unlifed Datatypes
has been proposed by Sebastian Graf
https://github.com/ghc-proposals/ghc-proposals/pull/265
https://github.com/sgraf812/ghc-proposals/blob/unlifted-data/proposals/0000-unlifted-datatypes.rst

I propose Simon Marlow as the shepherd, as the expert on low-level stuff.

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.

 

BTW, I just checked the proposal process documentation, and it says:

 

·  * Now the shepherd proposes to accept or reject the proposal. To do so, they

  • post their recommendation, with a rationale, on the GitHub discussion thread,
  • label the pull request as Pending committee review,
  • re-title the proposal pull request, appending (under review) at the end. (This enables easy email filtering.)
  • drop a short mail to the mailing list informing the committee that discussion has started.

which isn't exactly in line with the paragraph above. Shouldn't the first line be something like "post their recommendation, with a rationale, to the committee mailing list", and remove the final bullet?

 

Cheers

Simon

 

 


Thanks,
Joachim
--
Joachim Breitner
  mail@joachim-breitner.de
  http://www.joachim-breitner.de/

_______________________________________________
ghc-steering-committee mailing list
ghc-steering-committee@haskell.org
https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee