<div dir="ltr">I like the new organisation. One functional difference I noticed: the new description says that we assign a shepherd when the proposal starts the review process, but under the existing process a shepherd is assigned to each proposal when the PR is created (but I guess we haven't been sticking to this?). Ideally I think we'd assign shepherds earlier because it will streamline the review process: the shepherd will spot things that should be clarified or addressed before the rest of the committee gets involved. I think it's likely to be a better use of resources.<div><br></div><div>This also addresses the question about labels: if each proposal has a shepherd, then the shepherd will notice when the proposer adds a comment to the PR requesting review, and can formally start the process with the rest of the committee.</div><div><br></div><div>Cheers</div><div>Simon</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 February 2017 at 04:26, Joachim Breitner <span dir="ltr"><<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[I sent this mail from Monday to the wrong address, second try]<br>
<br>
Hi,<br>
<br>
there was a bit confusion about our documentation, so with SPJ’s<br>
blessing I went ahead and restructured it a bit. For now, this is only<br>
on a branch and not live yet:<br>
<br>
<a href="https://github.com/ghc-proposals/ghc-proposals/tree/wip/docs-restructur" rel="noreferrer" target="_blank">https://github.com/ghc-<wbr>proposals/ghc-proposals/tree/<wbr>wip/docs-restructur</a><br>
ing<br>
<br>
Note that it starts with a concise timeline of a proposal, and from<br>
there has links to section answering specific questions, within the<br>
same file. What was three files before (README, process, committee) is<br>
now all in here (with the exception of the “detailed instructions” for<br>
the Github-novice, which is in a separate file). This should make it<br>
easier for everyone involved to know who has to do what when.<br>
<br>
Our process is, however, flawed: We ask authors to set labels (“Under<br>
Discussion” and “Under Committee Review”), but they do not have<br>
permissions to do so. So this does not quite work.<br>
<br>
So I suggest the following change:<br>
<br>
* What was “Under Discussion” is now simply any PR that does not have<br>
any other label. This way, when opening discussion, nothing concrete<br>
has to be done. Which is easier. (GitHub allows to list all PRs that<br>
have no label, so there is no loss in functionality here.)<br>
<br>
* When the author wants to submit the PR, he sends a mail to this<br>
mailinglist (is this set up to accept mails from non-subscribers?) and<br>
it its the task of the shephard to set the label to indicate that that<br>
the committee has accepted to review the proposal. (At this point, the<br>
shephard could for example set the `Out-of-scope` label instead.)<br>
<br>
<br>
If there are no complains I will adjust the docs-restructuring branch<br>
accordingly and then move that to master.<br>
<br>
Greetings,<br>
Joachim<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Joachim “nomeata” Breitner<br>
<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a> • <a href="https://www.joachim-breitner.de/" rel="noreferrer" target="_blank">https://www.joachim-breitner.<wbr>de/</a><br>
XMPP: <a href="mailto:nomeata@joachim-breitner.de">nomeata@joachim-breitner.de</a> • OpenPGP-Key: 0xF0FBF51F<br>
Debian Developer: <a href="mailto:nomeata@debian.org">nomeata@debian.org</a></font></span><br>______________________________<wbr>_________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org">ghc-steering-committee@<wbr>haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/ghc-<wbr>steering-committee</a><br>
<br></blockquote></div><br></div>