<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I suspect we might want to consider a hybrid -- if so, do we need
to find an assistant to Joachim to maintain the spreadsheet? (Let's not
add to Joachim's workload but share it.)</div></blockquote><div><br></div><div>Aha -- I should have been clearer. I never intended to suggest that Joachim alone would maintain the spreadsheet. We all will! It took me about 20 mins to put together the entire status quo before sending my email. I think it would take an extra thirty seconds or so for us to each update it with our votes, and view others.</div><div><br></div><div>For me it'll reduce my workload, because I won't have to scroll through dozens of messages to reconstruct the current state of play.</div><div><br></div><div>I'm going to give it a try anyway. Even if no one else joins it, it'll be helpful to me. But I hope you will.</div><div><br></div><div>Simon <br></div>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 11 Sept 2023 at 04:48, Chris Dornan <<a href="mailto:chris@chrisdornan.com">chris@chrisdornan.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>While I think the spreadsheet is really nice, I have to say I am personally comfortable with Joachim's periodic summaries and his ability to read the room as to whether a proposal has the support of the committee.<div><br></div><div>If folks don't have time to respond for feedback then that is just the way it is and enough of the remainder of the committee have weighed in then I think we just move on. If Joachim is aware of missing coverage in any response then he waits until we have satisfactory coverage.</div><div><br></div><div>I am not saying we could not do better, but, for my needs, Joachim is managing everything pretty optimally.</div><div><br></div><div>Of course we all have way of working so it would be really good if folks could indicate whether they want (1) the old way (2) the way of the spreadsheet or (3) some hybrid.</div><div><br></div><div>I suspect we might want to consider a hybrid -- if so, do we need to find an assistant to Joachim to maintain the spreadsheet? (Let's not add to Joachim's workload but share it.)</div><div><br><div>Chris</div><div><br></div><div><br><blockquote type="cite"><div>On 10 Sep 2023, at 03:06, Simon Peyton Jones <<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Dear GHC steering committee<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Re GHC proposals I was talking to Simon M about</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><ul><li>Making the shepherd's job easier and quicker</li><li>Providing a way for members of the committee to say (explicitly) "I don't have an opinion about this proposal" and thus recuse themselves. Explicit recusal is better than "silence means assent" because silence can, and often does, mean "I'm under water and not listening".</li></ul><div>With that in mind, I want to revive my suggestion of running <a href="https://docs.google.com/spreadsheets/d/1e6GdwHmAjeDEUhTvP-b18MDkpTfH3SMHhFu5F3nDIWc/edit?usp=sharing" target="_blank">an online spreadsheet </a>to describe the state of proposals that are in our active purview. That is, I'm not proposing to show proposals that are under discussion by the community, or accepted etc -- just the ones that are in our inbox, <b>where the next action is ours.</b></div><div><b><br></b></div><div>That makes it much easier to see our current inbox, without looking back for Jocahim's last email and then adding deltas for all the emails since -- which I cannot do in my head.</div><div><br></div><div>Specifically, I have <b>a column for each committee member's vote. </b> That should make it easy for the shepherd to see who is yet to express an opinion, which I always find difficult.</div><div><br></div><div>As I say above, I am very uncomfortable with "silence means assent" for any but the smallest proposals. <b>I suggest instead that if there is a proposal where you feel unable to offer an opinion, due to lack of expertise, or lack of time, you can say "recuse" meaning that you explicitly want to stand down from this particular proposal.</b> (Somehow "abstain" carries a connotation of conflict of interest or something, but it amounts to the same thing.) If you are too under water to even recuse yourself, maybe it's time to step down.<br></div><div><br></div><div>So in columns F to O we should see explicit responses from every committee member, in a timely way.</div><div><br></div><div>Joachim doesn't like spreadsheets like this because they can easily get out of date. But it must be better than manually trawling email. <b>And it is up to each of us (not Joachim) to fill in our own column for proposals in our inbox.</b></div><div><br></div><div>If we don't like it, we can change it. You all have edit rights.</div><div><br></div><div>I have populated it with data from Joachim's message of 2 Sept, but there has been some action since then, so shepherds please update it. This is not Joachim's task!</div><div><br></div><div>Thanks</div><div><br></div><div>Simon<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div>
_______________________________________________<br>ghc-steering-committee mailing list<br><a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br></div></blockquote></div><br></div></div></blockquote></div>