[ghc-steering-committee] Deadlines for Shepherds?

[Manuel M T Chakravarty]

Sorry about the delay. It is summer holidays in Australia :)

I am not sure that deadlines with re-assigning proposals will work better. In fact, I think, you current way of sending regular reminders/status emails is very good and I very much appreciate the effort that this surely takes on your side.

Cheers
Manuel

> Am 06.01.2018 um 08:06 schrieb Joachim Breitner <mail at joachim-breitner.de>:
> 
> 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/
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee