<div dir="ltr">Turns out making a decision log is really BORING - who knew?!<div><br></div><div>I have made a start. Here is a Google Sheet: <a href="https://docs.google.com/spreadsheets/d/1fhYL7VqUAzL9_K22G6GS9leK-Yd-XRQdWh9IU1LLF9U/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1fhYL7VqUAzL9_K22G6GS9leK-Yd-XRQdWh9IU1LLF9U/edit?usp=sharing</a> </div><div><br></div><div>It's got a lot of gaps. I will try and fill it in a bit more when I get more motivation. If anyone feels like adding stuff in, please be my guest.</div><div><br></div><div>Cheers</div><div>Felicity</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 4, 2019 at 1:05 AM Clarence Cromwell <<a href="mailto:clarencewcromwell@gmail.com">clarencewcromwell@gmail.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 dir="auto">A decision log would be a much better history of the project than searching through email. The email archive is going to become large, and searching it for history that you don’t already know about might seem like a forbidding task. <div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)"> And the lack of historical info could discourage newcomers by depriving them of any context. </span><div><br></div><div>It would be better for future contributors if we could explain the decision history in a log, and this is important because the project is about better user experience through better documentation.</div><div><br></div><div><span style="background-color:rgba(255,255,255,0)">At the very least the decisions voted on over the previous week should be summarized in the meeting minutes. </span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">It would be better to accumulate all the decisions in one place, either by compiling the minutes or by having a consistently formatted decision log.</span></div><div><br><br><div id="gmail-m_-2368319392658243552AppleMailSignature" dir="ltr">Sent from my iPhone</div><div dir="ltr"><br>On Aug 2, 2019, at 5:01 PM, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<p>+0 from me.</p>
<p>I think it is a good idea, although I haven't seen it used in
Open Source projects I've been involved in, which makes me
question how important it is if open communities haven't picked it
up.</p>
<p>I'd be inclined to make it super light, to encourage use.
Probably:</p>
<p>Date, Motion, Pass/Fail result, a link to the final email in
thread which calls the vote. (If interested, historians can dig
through the email archive.<br>
</p>
<div class="gmail-m_-2368319392658243552moz-cite-prefix">On 3/8/19 7:52 am, Erin McKean wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Thanks to a great suggestion from Ríona MacNamara,
I'd like to propose we start a decision log for the Good Docs
project.
<div><br>
We are sending a lot of email and it might be hard for people
to find decisions there or in the meeting notes.</div>
<div><br>
</div>
<div>General format is description, date, deciders, rationale,
alternatives considered, followup needed.</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Thanks!<br>
<br>
Erin</div>
<div>
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail-m_-2368319392658243552gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Erin
McKean |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Developer
Relations Program Manager, Open Source Strategy |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:emckean@google.com" target="_blank">emckean@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> she/her</span></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="gmail-m_-2368319392658243552mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_-2368319392658243552moz-quote-pre">_______________________________________________
SeasonOfDocs mailing list
<a class="gmail-m_-2368319392658243552moz-txt-link-abbreviated" href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a>
<a class="gmail-m_-2368319392658243552moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a>
</pre>
</blockquote>
<pre class="gmail-m_-2368319392658243552moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>SeasonOfDocs mailing list</span><br><span><a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a></span><br><span><a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a></span><br></div></blockquote></div></div></div>_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>