<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.Code, li.Code, div.Code
{mso-style-name:Code;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
.MsoPapDefault
{mso-style-type:export-only;
margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Joachim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">The new organisation at
<a href="https://github.com/ghc-proposals/ghc-proposals">https://github.com/ghc-proposals/ghc-proposals</a> is so much better. Thank you!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">How can I edit it in cosmetic ways? I see no edit button. (Defeated by github again.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I agree that we should assign a shepherd when the owner submits a proposal to the committee. Of course committee members can (and I hope will) get
involved earlier.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Simon<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> ghc-steering-committee [mailto:ghc-steering-committee-bounces@haskell.org]
<b>On Behalf Of </b>Simon Marlow<br>
<b>Sent:</b> 27 February 2017 10:48<br>
<b>To:</b> Joachim Breitner <mail@joachim-breitner.de><br>
<b>Cc:</b> ghc-steering-committee@haskell.org<br>
<b>Subject:</b> Re: [ghc-steering-committee] Redid our documentation<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
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.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
Cheers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
Simon<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
On 26 February 2017 at 04:26, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
[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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Ftree%2Fwip%2Fdocs-restructur&data=02%7C01%7Csimonpj%40microsoft.com%7Cc3454ff11b474b5813a108d45efe20c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636237892968379132&sdata=sM402v4a3DgfMjmvUADYzPLWEMgEbCMzHwrlS8Gs7kk%3D&reserved=0" target="_blank">https://github.com/ghc-proposals/ghc-proposals/tree/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 style="color:#888888"><br>
<br>
<br>
<span class="hoenzb">--</span><br>
<span class="hoenzb">Joachim “nomeata” Breitner</span><br>
<span class="hoenzb"> <a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a> •
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.joachim-breitner.de%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cc3454ff11b474b5813a108d45efe20c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636237892968535389&sdata=yVRoXu9qb%2BYvutm%2FGb%2FzFd04NMr7taMaVFIzLz4P9wQ%3D&reserved=0" target="_blank">
https://www.joachim-breitner.de/</a></span><br>
<span class="hoenzb"> XMPP: <a href="mailto:nomeata@joachim-breitner.de">nomeata@joachim-breitner.de</a> • OpenPGP-Key: 0xF0FBF51F</span><br>
<span class="hoenzb"> Debian Developer: <a href="mailto:nomeata@debian.org">nomeata@debian.org</a></span></span><br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org">ghc-steering-committee@haskell.org</a><br>
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=02%7C01%7Csimonpj%40microsoft.com%7Cc3454ff11b474b5813a108d45efe20c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636237892968535389&sdata=w84hmRquM4%2BcK47yt43tAgl8iyzIcK7BoCht2FiLaSs%3D&reserved=0" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>