<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi, </div><div class="gmail_extra"><div class="gmail_quote"><div class="gmail_default" style="font-size:small"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
2015. 12. 22., 오전 6:20, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> 작성:<br>
There is also good material from Jeff. The version with my commentary is here:<br>
<a href="https://lists.osgeo.org/pipermail/discuss/2015-November/015346.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/pipermail/discuss/2015-November/015346.html</a><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"></blockquote></blockquote></blockquote></div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">Thanks for all your comments to Jeff's material Cameron! I've reread it now and agree with you on many points, especially that we - using your words - do not <span style="color:rgb(0,0,0);white-space:pre-wrap">control a workforce, but only have </span><span style="color:rgb(0,0,0);white-space:pre-wrap">the ability to inspire volunteers.</span></div><br></div><div><div class="gmail_default" style="font-size:small">I don't quite agree with your statement on diversity - given that studies seem to show that our preconceptions lead us to believe that certain people are less or more qualified than they are, based on race or gender. Why not lead by example rather than wait for 50% of the OSGeo community to be female. But I don't want this to be my main focus!</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Currently our agenda <a href="https://wiki.osgeo.org/wiki/Board_Face_to_Face_Meeting_2016#Agenda">https://wiki.osgeo.org/wiki/Board_Face_to_Face_Meeting_2016#Agenda</a> reads:</div><div class="gmail_default" style="font-size:small;display:inline">- </div>review mission statement and revise it if necessary<br><div class="gmail_default" style="font-size:small;display:inline">- </div>develop core values of OSGeo to dictate behaviour and action around open source GIS<br><div class="gmail_default" style="font-size:small;display:inline">- </div>r<div class="gmail_default" style="font-size:small;display:inline"></div>eview foundation goals and set the vision of OSGeo<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review bylaws based on mission statement, core values and vision<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review relationships with other organisations based on mission statement, core values and vision<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review projects<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review branding (website etc.)<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review finances<br><div class="gmail_default" style="font-size:small;display:inline">- </div>review incubation progress<div class="gmail_default" style="font-size:small"></div><div class="gmail_default" style="font-size:small">... As is, this sounds very ambitious. I could easily imagine spending two days on reviewing projects alone!</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">We need to narrow things down. What does "review" mean in the context of this meeting?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I would go as far as suggest that reviewing projects, branding, and incubation should be moved off the agenda because it will leave us with too little time for the individual items if we leave them on.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Or are there urgent topics connected to these agenda items?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br><div class="gmail_quote">On Tue, Dec 22, 2015 at 1:35 PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">So I suggest be pragmatic, and keep goals simple and achievable.<br>Be careful asking the community for open ended questions which will take much time to think about and then articulate. You likely won't get a response.<br>Better to be targeted with questions.</blockquote><div><br></div><div><div class="gmail_default">Thanks Cameron! I think this is a very good point to keep in mind.</div></div><div class="gmail_default"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On 22/12/2015 1:26 pm, Sanghee Shin wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">we need to ask community members to actively participate in setting the agendas, expected outcomes of F2F meeting earlier rather than asking after F2F meeting. We may ask them to write down their own OSGeo’s mission statement/core values/visions there at wiki page.<br></blockquote></div></div></blockquote><div><br></div><div><div class="gmail_default">Based on Cameron's recommendation quoted above, I think that it might be more productive to ask the community to provide feedback on suggested clear actions (which should be based on or mission/values/vision) rather than more vague descriptions.</div></div><div class="gmail_default"><br></div><div class="gmail_default">An example could be concerning the code sprint topic:</div><div class="gmail_default">quote Jeff:</div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">></span><i style="color:rgb(0,0,0);white-space:pre-wrap"> OSGeo will actively promote its ability to support all code sprints of </i></div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">></span><i style="color:rgb(0,0,0);white-space:pre-wrap"> any size, no matter if there is only one project being enhanced.</i></div><div class="gmail_default"><i style="color:rgb(0,0,0);white-space:pre-wrap">quote Cameron:</i></div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">> I suggest that this statement should not be quite as Open Ended. As it </span></div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">> stands, this could be interpreted to mean that any code sprint will be </span></div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">> funded by OSGeo. There are limits to OSGeo's budget, and this should be </span></div><div class="gmail_default"><span style="color:rgb(0,0,0);white-space:pre-wrap">> acknowledged in the words we select.</span></div><div><br></div><div class="gmail_default">example of a possible action:</div><div class="gmail_default">We will add a position for code sprint support to the 2016 budget. Projects are invited via email to apply for a share of this budget at latest x months before the planned code sprint. Applications should contain <details>.</div><div class="gmail_default"><br></div><div class="gmail_default">Ideally, suggestions for actions should be discussed on list before the f2f to give the board a better understanding of the community position. After the f2f, I expect we'll have another feedback round on list before any voting.</div><div class="gmail_default"><br></div><div class="gmail_default">Imho, this list of planned actions will be the most tangible outcome of the f2f.</div></div></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Best wishes,</div><div class="gmail_default" style="font-size:small">Anita</div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br></div></div>