<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I support this proposal. Having many accepted but unimplemented proposals is not a good look. If need be, we can create a ready-for-submission-but-lacking-implementor label so that potential contributors can find ideas, but I favor waiting for a demand before creating that structure.<div class=""><br class=""></div><div class="">Simon's idea of un-accepting proposals is interesting, but should probably not get tucked into this idea.</div><div class=""><br class=""></div><div class="">Richard<br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 4, 2022, at 7:02 PM, Simon Peyton Jones <<a href="mailto:simon.peytonjones@gmail.com" class="">simon.peytonjones@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:tahoma,sans-serif">Dear committee,</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:tahoma,sans-serif">See
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/517" rel="noreferrer" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals/pull/517</a> <br class=""></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Joachim suggests that a prerequisite for submitting a proposal to the committee is that someone is offering to implement it.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><ul class=""><li class="">This would avoid us spending precious cycles debating a proposal that no one is going to implement.</li><li class="">An offer of implementation cannot be binding, so it is something of a soft constraint. (An author could cynically volunteer themselves, without having any intention of carrying through, but we expect better of the Haskell community.)</li><li class="">We should stress that nothing stops someone creating a proposal, making a PR, and debating it with the community, all without an implementor. Only when it is submitted to the committee for review and approval is an implementor required.</li><li class="">Joachim suggests that this replaces the (never used) "Endorsements" section.<br class=""></li></ul><div class="">I wonder if a proposal that is accepted but not implemented (for whatever reason) should be un-accepted after, say, a year. That would provide some incentive to get on with it; and the language context might be different by then.</div><div class=""><br class=""></div><div class="">I suggest that we debate the principle first. I have a few word-smithing suggestions, but principles first!</div><div class=""><br class=""></div><div class="">On balance I recommend acceptance, with the above nuances clarified.</div><div class=""><br class=""></div><div class="">Simon<br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Aug 2022 at 07:50, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" class="">mail@joachim-breitner.de</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Committee,<br class="">
<br class="">
I have submitted a meta-proposal to require implementors to be named<br class="">
before proposal submission, to focus on those proposals that are likely<br class="">
to be actually implemented.<br class="">
<br class="">
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/517" rel="noreferrer" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals/pull/517</a><br class="">
<br class="">
Because this is a process-related proposal, I’d like to ask Simon to shepherd it.<br class="">
<br class="">
Please guide us to a conclusion as outlined in <br class="">
<a href="https://github.com/ghc-proposals/ghc-proposals#committee-process" rel="noreferrer" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals#committee-process</a><br class="">
<br class="">
Thanks,<br class="">
Joachim<br class="">
<br class="">
<br class="">
<br class="">
-- <br class="">
Joachim Breitner<br class="">
<a href="mailto:mail@joachim-breitner.de" target="_blank" class="">mail@joachim-breitner.de</a><br class="">
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank" class="">http://www.joachim-breitner.de/</a><br class="">
<br class="">
_______________________________________________<br class="">
ghc-steering-committee mailing list<br class="">
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class="">
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class="">
</blockquote></div>
_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a><br class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee<br class=""></div></blockquote></div><br class=""></div></div></body></html>