<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Calibri;color: #000000;text-align: left" dir="ltr">
As per Martin and others, I think p<span style="font-size: 10pt">hilosophically, it is a good idea. It is an issue we as a board are grappling with and I am not sure there is an easy answer or solution</span><div><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt">My concern, </span>and<span style="font-size: 10pt"> as Alex notes, is that it is a technical solution. It </span><span style="font-size: 10pt">introduces a barrier of entry for members and/or community to participate. We are such a wide ranging community, from highly skilled developers to </span><span style="font-size: 10pt">casual mappers to GIS users to people that have had no previous </span>experience with geospatial software<span style="font-size: 10pt">. </span><span style="font-size: 10pt">I do </span><span style="font-size: 13.3333px">realize</span><span style="font-size: 10pt"> that many in the community would welcome a move to Git/Markup, but f</span><span style="font-size: 10pt">or some (including myself) having to learn how to use Git and Markup will take some time, for others an insurmountable obstacle. If we were a </span>more<span style="font-size: 10pt"> technical focused </span>community<span style="font-size: 10pt"> (such as a </span>Python<span style="font-size: 10pt"> or R group) then I can see a move towards a more technical </span>solution making sense. </div><div><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt">We </span><span style="font-size: 13.3333px">have</span><span style="font-size: 10pt"> worked hard to lower </span><span style="font-size: 13.3333px">the</span><span style="font-size: 10pt"> barriers of entry to the FOSS4G and OSM communities, and in my mind it does not make sense to erect </span><span style="font-size: 13.3333px">technical</span><span style="font-size: 10pt"> barriers that may restrict members participation in </span><span style="font-size: 13.3333px">board</span><span style="font-size: 10pt"> and/or the organisation's affairs. </span><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt">Google Docs is not an ideal solution (both technically and</span><span style="font-size: 13.3333px"> p</span><span style="font-size: 10pt">hilosophically), and I do </span>acknowledge<span style="font-size: 10pt"> that we </span>should<span style="font-size: 10pt"> be seen to be 'eating our own dog food' so to speak, but it does work and has a very low barrier of entry (internet connection and </span>email<span style="font-size: 10pt"> address). I think our issue is more around 'housekeeping', and better managing volunteers time in insuring that </span>documentation<span style="font-size: 10pt"> is completed and a transparent process in managing and ratifying.</span></div><div><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt">I would really welcome more of the </span>communities<span style="font-size: 10pt"> thought on this topic!</span></div><div><span style="font-size: 10pt"><br></span></div><div><span style="font-size: 10pt">Greg</span></div><div><br></div><div><span style="font-size: 10pt"><br></span></div><div><br></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>On 11/20/2020 5:05:05 PM, Emma Hain <emmahain@gmail.com> wrote:</p><div style='font-family:Arial,Helvetica,sans-serif'><div dir="ltr">I agree <div>For me, the positive is that t will help get me used to the system as well. I may be asking some user notes on it but it is the way I want to go as I eventually (when I have time) I would like to get more on the documentation side of things. </div><div><br></div><div>Thanks</div><div>Em</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 20, 2020 at 8:27 AM Martin Tomko <<a href="mailto:tomkom@unimelb.edu.au">tomkom@unimelb.edu.au</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 lang="EN-AU" style="overflow-wrap: break-word;">
<div class="gmail-m_-6437209534521178773WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Philosophically, I agree.<u></u><u></u></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.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Let’s give it a try… <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">M.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="font-size: 12pt;color: black">From:
</span></b><span style="font-size: 12pt;color: black">Oceania-Board <<a href="mailto:oceania-board-bounces@lists.osgeo.org" target="_blank">oceania-board-bounces@lists.osgeo.org</a>><br>
<b>Date: </b>Friday, 20 November 2020 at 1:11 am<br>
<b>To: </b><a href="mailto:oceania-board@lists.osgeo.org" target="_blank">oceania-board@lists.osgeo.org</a> <<a href="mailto:oceania-board@lists.osgeo.org" target="_blank">oceania-board@lists.osgeo.org</a>><br>
<b>Subject: </b>Re: [Oceania-Board] Proposal: policy as code<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">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>
<a href="mailto:Oceania-Board@lists.osgeo.org" target="_blank">Oceania-Board@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/oceania-board" target="_blank">https://lists.osgeo.org/mailman/listinfo/oceania-board</a><u></u><u></u></p>
</div>
</div>
</div>
_______________________________________________<br>
Oceania-Board mailing list<br>
<a href="mailto:Oceania-Board@lists.osgeo.org" target="_blank">Oceania-Board@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/oceania-board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/oceania-board</a><br>
</blockquote></div>
_______________________________________________
Oceania-Board mailing list
Oceania-Board@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/oceania-board
</div></blockquote>
</div></body><img class="mailbird" width="1" height="1" style="border:0; width:1; height:1;" src="http://tracking.getmailbird.com:8000/opentrackingpixel/?messageId=Mailbird-51a4b932-9185-4156-a2ac-a96f12c596fb@gmail.com&senderHash=38A2B06F13C868980E8E5D98E6C576293FF094FB7BFEF8917BA94F0062959723&recipientHash=A5CADE333F52F01486A340F54EAB7B1DD5D8F96861246CCEB834FE705D8587F1&internalId=f07b53e3-a62b-40f0-9079-1bcac0897a51">