[ghc-steering-committee] Deadlines for Shepherds?

[Joachim Breitner]

Hi,

you know that I like slim smooth processes with not too many rules, and
our current process worked pretty nicely for the first few proposals.
But now it seems that we lost some steam, and a fair number of
proposals are stuck waiting for their Shepherd to make progress.

Does this mean that people simply need deadlines for work to be done?

Do you want deadlines?


Also, I am happy to re-assign some stalled proposals to new shepherds.
Does anyone want to volunteer recommending a decision for one or more
of these proposals:

Lazy unboxed tuples
https://github.com/ghc-proposals/ghc-proposals/pull/35

Mutable constructor fields
https://github.com/ghc-proposals/ghc-proposals/pull/8

Deprecate STM invariant mechanism
https://github.com/ghc-proposals/ghc-proposals/pull/77

-Wall to include incomplete-uni-patterns and incomplete-record-updates
https://github.com/ghc-proposals/ghc-proposals/pull/71

Thanks,
Joachim

-- 
Joachim Breitner
  mail at joachim-breitner.de
  http://www.joachim-breitner.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20180105/b24c57f9/attachment.sig>