<html 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=Windows-1252">
<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:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Philosophically, I agree.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Practically, I am unsure whether it will solve the issue. I am also lost in the stuff going on, and how to track it. But I hate issue trackers, so that would not solve it. Maybe a transparent GIT-like doc system would
help. But I do not think that the versioning is what is needed, the transparent, always online exposure is the crux.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Let’s give it a try… <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">M.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Oceania-Board <oceania-board-bounces@lists.osgeo.org><br>
<b>Date: </b>Friday, 20 November 2020 at 1:11 am<br>
<b>To: </b>oceania-board@lists.osgeo.org <oceania-board@lists.osgeo.org><br>
<b>Subject: </b>Re: [Oceania-Board] Proposal: policy as code<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">hey Alex, John proposed this a long time ago and some work was done<br>
towards an OO gitlab repository, I believe we have one already<br>
somewhere..<br>
<br>
I was supportive of the idea then, and I still am now, so thanks for<br>
raising it again. I prefer gitlab because we can make it immune from<br>
the whims of a huge company if we want to, but also not keen to make<br>
that preference an impediment. whatever works, knowing that we always<br>
risk *something*...<br>
<br>
I think it is totally fine to gently mentor ourselves toward using a<br>
git based structure, there is plenty of help!<br>
<br>
Cheers<br>
<br>
Adam<br>
_______________________________________________<br>
Oceania-Board mailing list<br>
Oceania-Board@lists.osgeo.org<br>
<a href="https://lists.osgeo.org/mailman/listinfo/oceania-board">https://lists.osgeo.org/mailman/listinfo/oceania-board</a><o:p></o:p></p>
</div>
</div>
</body>
</html>