<div dir="ltr">Hello,<div><br></div><div>I think this sounds fairly reasonable, but it is hard to say how well it will work in practice until we try it.</div><div><br></div><div>Some clarifying questions on the intended process:</div><div>   1.  After submitting the initial merge request, is the person making the proposal to wait for any kind of acknowledgment, or just move on to step 2?</div><div>   2. Is the discussion going to happen on one of the mailing lists, if so which?   Is it the job of the proposing person to involve/notify the committee about the discussion?  If so, how are they to find out who is on the committee?</div><div>   3. How does one actually perform step 3, another pull request or simply an e-mail to someone?</div><div><br></div><div>Typo: two separate bullets in the proposal are labelled as 4.</div><div><br></div><div>Cheers,</div><div>-Iavor</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 11, 2016 at 2:36 PM, Simon Peyton Jones via Glasgow-haskell-users <span dir="ltr"><<a href="mailto:glasgow-haskell-users@haskell.org" target="_blank">glasgow-haskell-users@haskell.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just to be clear:<br>
<br>
* We are actively seeking feedback about the proposal [4] below.<br>
  It's not a fait-accompli.<br>
<br>
* You can join the dialogue by (a) replying to this email,<br>
  (b) via the "Conversations" tab of [4], namely<br>
      <a href="https://github.com/ghc-proposals/ghc-proposals/pull/1" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/1</a><br>
  Doubtless via reddit too!<br>
<br>
  If you don't like something, the more specific and concrete you<br>
  can be about a better alternative, the better.  E.g. Richard's<br>
  comments on the "conversations" tab both ask questions and propose<br>
  answers.  Bravo!<br>
<br>
Simon<br>
<div><div class="h5"><br>
| -----Original Message-----<br>
| From: ghc-devs [mailto:<a href="mailto:ghc-devs-bounces@haskell.org">ghc-devs-bounces@haskell.org</a>] On Behalf Of Ben<br>
| Gamari<br>
| Sent: 09 July 2016 21:46<br>
| To: GHC developers <<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a>>; ghc-users <glasgow-haskell-<br>
| <a href="mailto:users@haskell.org">users@haskell.org</a>><br>
| Subject: Rethinking GHC's approach to managing proposals<br>
|<br>
| Hello everyone,<br>
|<br>
| Recently there has been a fair bit of discussion[1,2] around the<br>
| mechanisms by which proposed changes to GHC are evaluated. While we have<br>
| something of a formal proposal protocol [3], it is not clearly<br>
| documented, inconsistently applied, and may be failing to serve a<br>
| significant fraction of GHC's potential contributor pool.<br>
|<br>
| Over the last few weeks, I have been doing a fair amount of reading,<br>
| thinking, and discussing to try to piece together a proposal scheme<br>
| which better serves our community.<br>
|<br>
| The resulting proposal [4] is strongly inspired by the RFC process in<br>
| place in the Rust community [5], the leaders of which have thought quite<br>
| hard about fostering community growth and participation. While no<br>
| process is perfect, I feel like the Rust process is a good starting<br>
| point for discussion, offering enough structure to guide new<br>
| contributors through the process while requiring only a modest<br>
| investment of developer time.<br>
|<br>
| To get a sense for how well this will work in our community, I propose<br>
| that we attempt to self-host the proposed process. To this end I have<br>
| setup a ghc-proposals repository [6] and opened a pull request for<br>
| discussion of the process proposal [4].<br>
|<br>
| Let's see how this goes.<br>
|<br>
| Cheers,<br>
|<br>
| - Ben<br>
|<br>
|<br>
| [1]<br>
</div></div>| <a href="https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.red" rel="noreferrer" target="_blank">https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.red</a><br>
| <a href="http://dit.com" rel="noreferrer" target="_blank">dit.com</a>%2fr%2fhaskell%2fcomments%2f4oyxo2%2fblog_contributing_to_ghc%2f&<br>
| data=01%7c01%7csimonpj%<a href="http://40064d.mgd.microsoft.com" rel="noreferrer" target="_blank">40064d.mgd.microsoft.com</a>%7c99735311c5f64cac6a6608<br>
| d3a83a032a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=Hl6GqRWfu7IOQtpE<br>
| jpfsNAkv3mmLgNKm2ciQDoMe6HA%3d<br>
| [2]<br>
| <a href="https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.red" rel="noreferrer" target="_blank">https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.red</a><br>
| <a href="http://dit.com" rel="noreferrer" target="_blank">dit.com</a>%2fr%2fhaskell%2fcomments%2f4isua9%2fghc_development_outsidein%2f<br>
| &data=01%7c01%7csimonpj%<a href="http://40064d.mgd.microsoft.com" rel="noreferrer" target="_blank">40064d.mgd.microsoft.com</a>%7c99735311c5f64cac6a660<br>
| 8d3a83a032a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=bj2AQqQirX3X%2f<br>
| 4%2fFr05eXFuD4yW0r9Nmrmdg7IGEF%2f8%3d<br>
<span class="">| [3]<br>
| <a href="https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/AddingFeatures" rel="noreferrer" target="_blank">https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/AddingFeatures</a><br>
| [4] <a href="https://github.com/ghc-proposals/ghc-" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-</a><br>
| proposals/pull/1/files?short_path=14d66cd#diff-<br>
| 14d66cda32248456a5f223b6333c6132<br>
| [5] <a href="https://github.com/rust-lang/rfcs" rel="noreferrer" target="_blank">https://github.com/rust-lang/rfcs</a><br>
| [6] <a href="https://github.com/ghc-proposals/ghc-proposals" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals</a><br>
</span>_______________________________________________<br>
Glasgow-haskell-users mailing list<br>
<a href="mailto:Glasgow-haskell-users@haskell.org">Glasgow-haskell-users@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users</a><br>
</blockquote></div><br></div>