<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
font-family:"Calibri",sans-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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{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;}
/* List Definitions */
@list l0
{mso-list-id:385417456;
mso-list-type:hybrid;
mso-list-template-ids:-1688820772 1605548426 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:13;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">HI all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I have been keeping away from chipping too much into this discussion, as governance is not my strong point ( and I do like a bit of anarchy, but…). SO here a brief chip in.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I strongly support Alex’s and John’s points. I think the guidelines, or bylaws or whatever, are here to guide us in the bad times, not in the good times. I would not worry about an overzealous steering committee – I think
anyone who wants to be involved hands on would be on a LoC anyway.<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">I think the point of the steering committee is :<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span lang="EN-GB">Continuity and transfer of knowledge<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span lang="EN-GB">Financial oversight, as a means to assure the community their money is spent wisely, and any surplus ( not profit) is re-invested either in the next conference,
or the community (immediately – as a means to achieve participation of disadvantaged/underrepresented groups – or in the data and software projects themselves, judiciously). I agree with the points of Alex here, although maybe we do not need a hard $ limit
on the decisions, but one that will be set for any instance of the conference by the steering committee, in agreement with the LoC.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I think that if we peg in a rotating membership ( for at least apart of the Steering committee) of the poast, current and next Conference chairs, any miscommunications will be minimal and if they would happen, this would
be a clear indication something is amiss.<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">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Martin<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"><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"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">FOSS4G-Oceania <foss4g-oceania-bounces@lists.osgeo.org> on behalf of Alex Leith <alexgleith@gmail.com><br>
<b>Date: </b>Tuesday, 11 December 2018 at 8:43 am<br>
<b>To: </b>John Bryant <johnwbryant@gmail.com><br>
<b>Cc: </b>foss4g-oceania <foss4g-oceania@lists.osgeo.org><br>
<b>Subject: </b>Re: [FOSS4G-Oceania] Fwd: Governance<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hey folks<br>
<br>
Perhaps the one thing that needs to be concrete is the financial delegation, or approval guidelines.<br>
<br>
So, for example, approval of the conference budget should be with the Board. Delivery of the budget is the CC. Spending that is less than, say, $1,000 that is within the agreed budget is the CC’s responsibility, anything greater needs the treasurer’s sign off
or potentially approval by the Board.<br>
<br>
There needs to be wording around agreed budgets, as a budget should aim for a reasonable surplus, and if its looking like exceeding that greed surplus, then there’s discretion around spending on extras, as we did. But if the budget isn’t likely to exceed the
agreed target, there shouldn’t be optional extra spending....<br>
<br>
This process ensures that the group that is responsibility for financial longevity is in the loop when it comes to big financial decisions, while the group running the event is empowered to make decisions still.<br>
<br>
Other than that, I can only think of guiding statements really, and each individual conference committee gets to make their stamp on process and format.<br>
<br>
Cheers,<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, 11 Dec 2018 at 8:25 am, John Bryant <<a href="mailto:johnwbryant@gmail.com">johnwbryant@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Yep, all makes sense. I agree that strong communications should resolve any tension there.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think you're dead right re: the relationship between a strong conference proposal/concept and more independence, will be something we can evolve towards. If we can use a statement of guidance to the board in this first iteration, I hope
it will serve the immediate purpose and leave us room to grow.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One key point is that we don't set any stalemate traps by leaving too much vagueness in the lines of reporting. To actually delegate authority to the committee, it seems like we would need to get quite detailed about how this would work
ie. lots of what ifs.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My feeling is that <i>formal</i> authority would only need to be invoked if
<i>informal</i> authority isn't cutting the mustard... if we focus on nurturing a strong & healthy & engaged community, perhaps we can keep the need for formal authority at bay.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I've added the guidance statement to the doc so we can consider whether it meets the need. Have at 'er!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">John<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
FOSS4G-Oceania mailing list<br>
<a href="mailto:FOSS4G-Oceania@lists.osgeo.org" target="_blank">FOSS4G-Oceania@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/foss4g-oceania" target="_blank">https://lists.osgeo.org/mailman/listinfo/foss4g-oceania</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Alex Leith <o:p></o:p></p>
<div>
<p class="MsoNormal">0419 189 050<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>