<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">It would be very helpful if all of the currently listed conference committee members could estimate when they joined the committee and also indicate any FOSS4G Global or regional events that they have chaired or vice chaired. Please update the wiki page.<div class=""><br class=""></div><div class="">Thanks<br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">______<br class="">Steven<br class=""><br class=""></span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 15 Sep 2016, at 04:22, Helena Mitasova <<a href="mailto:hmitaso@ncsu.edu" class="">hmitaso@ncsu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">+1 from Helena<div class=""><br class=""></div><div class="">It is not quite clear to me who is supposed to step down when, but I assume that this will become clear as the new rules are implemented (I don't exactly remember for how long I have been on the conference committee but it has been a long time.) Anyway, I agree with what has been proposed here.<br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Sep 14, 2016 at 3:25 PM, Steven Feldman <span dir="ltr" class=""><<a href="mailto:shfeldman@gmail.com" target="_blank" class="">shfeldman@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">The period for comment has now closed. I have marginally changed the text to clarify a couple of items following comments from Eli, Till, Jachym and David.<div class=""><br class=""></div><div class="">If you have not voted you have until 18.00 GMT on Sunday 18th September. </div><div class="">As I have it recorded there are:</div><div class="">+1 from Eli, Cameron, Jeroen and Steven</div><div class="">Expressions of agreement but not a specific +1 from Till, David B, Jachym</div><div class="">0 or -1 from no one</div><div class=""><br class=""></div><div class="">Adjusted motion:</div><div class=""><br class=""></div><div class="">Goals</div><div class="">=====</div><div class=""><br class=""></div><div class="">The conference committee have the responsibility to run the selection process and voting for the global FOSS4G, to vote on other proposals submitted to the committee and to advise the board on other matters relating to FOSS4G events.</div><div class=""><br class=""></div><div class="">Role of the Committee and the broader community on the Conference_Dev list</div><div class="">==============================<wbr class="">==============================</div><div class=""><br class=""></div><div class=""><div style="margin:0px;line-height:normal" class=""><span class="">1) Everyday topics will be decided upon by an open vote of all list participants in a clearly designated separate mail thread (+1/-1) over a minimum of two business days with a minimum participation of 3 votes. Ideally we aim for consensus falling back on simple majority vote where necessary. The result will be clearly declared afterwards (or whatever is decided).</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">2) Election of conference committee is by secret vote and restricted to the remaining conference committee members and board members who are not members of the conference committee.</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">3) FOSS4G Selection - All Letters of Intent and subsequent proposals will be posted to the list for open comment by all list participants. The selection of the winning proposal is by secret vote of conference committee members only (for the avoidance of doubt the Board do not vote in the selection process but they do ratify the conference committee’s reccommendation). </span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">4) Any committee member who has a potential conflict of interest is expected to withdraw from vote. A </span>member<span class=""> of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude </span>themselves<span class=""> from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">Votes in 2 and 3 are to an online voting service or by email to an independent teller appointed by CC Chair</span></div></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class="">Conference Committee membership policy and process</div><div style="margin:0px;line-height:normal" class="">==============================<wbr class="">============</div><div class=""><br class="">1) The conference committee aims to retain up to 11 active members, preferably an odd number<br class=""><br class=""></div><div class="">2) The committee aims for half of these members to be chairs (or vice chairs) of the most recent FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member<br class=""><br class=""></div><div class="">3) The remaining membership is open, ideally attracting people from earlier past chairs or active LOC members from past Global, Regional FOSS4G or related conferences</div><br class=""><div class="">4) Each year (after FOSS4G) 3 committee members should retire from the committee:<br class="">a) The longest standing past FOSS4G chair<br class="">b) The longest standing 2 committee members remaining<br class=""><div class=""><br class=""></div><div class="">5) Each year, prior to releasing the Global FOSS4G RfP, the remaining committee members should fill available vacancies, using the above</div>criteria as voting guidelines. OSGeo Board members who are not on the conference committee will also be invited to vote.</div><div class=""><br class=""></div><div class=""><div class=""><div class="">6) Past committee members including those who have stood down due to length of service may stand for re-election<br class=""><br class=""></div><div class="">7) Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.<br class=""><br class=""></div></div></div><div class=""><div class="">
<span style="border-collapse:separate;line-height:normal;border-spacing:0px" class="">______<br class="">Steven<br class=""><br class=""></span>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 9 Sep 2016, at 15:41, Steven Feldman <<a href="mailto:shfeldman@gmail.com" target="_blank" class="">shfeldman@gmail.com</a>> wrote:</div><br class=""><div class=""><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">Goals</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">=====</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><br class=""></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">The conference committee have the responsibility to run the selection process and voting for the global FOSS4G, to vote on other proposals submitted to the committee and to advise the board on other matters relating to FOSS4G events.</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><br class=""></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">Role of the Committee and the broader community on the Conference_Dev list</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">==============================<wbr class="">==============================</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><br class=""></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div style="margin:0px;line-height:normal" class=""><span class="">1) Everyday topics will be decided upon by an open vote of all list participants in a clearly designated separate mail thread (+1/-1) over a minimum of two business days with a minimum participation of 3 votes. Ideally we aim for consensus falling back on simple majority vote where necessary. The result will be clearly declared afterwards (or whatever is decided).</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">2) Election of conference committee is by secret vote and restricted to the remaining conference committee members and board members who are not members of the conference committee.</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">3) FOSS4G Selection - All Letters of Intent and subsequent proposals will be posted to the list for open comment by all participants. The selection of the winning proposal is by secret vote of conference committee members only. Any committee member who has a potential conflict of interest is expected to withdraw from vote. In the event of a disagreement the committee chair will decide.</span></div><div style="margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="margin:0px;line-height:normal" class=""><span class="">Votes in 2 and 3 are to an online voting service or by email to an independent teller appointed by CC Chair</span></div></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;line-height:normal" class=""><span class=""><br class=""></span></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;line-height:normal" class="">Conference Committee membership policy and process</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin:0px;line-height:normal" class="">==============================<wbr class="">============</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><br class="">1) The conference committee aims to retain up to 11 active members, preferably an odd number<br class=""><br class=""></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">2) The committee aims for half of these members to be chairs (or vice chairs) of the most recent FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member<br class=""><br class=""></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">3) The remaining membership is open, ideally attracting people from earlier past chairs or active LOC members from past Global, Regional FOSS4G or related conferences</div><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">4) Each year (after FOSS4G) the 3 committee members should stand down:<br class="">a) The longest standing past FOSS4G chair<br class="">b) The longest standing 2 committee members remaining<br class=""><div class=""><br class=""></div><div class="">5) Each year, prior to putting out the Global FOSS4G RfP, the old committee should vote for their replacement committee, using the above criteria as voting guidelines. OSGeo Board members who are not on the conference committee will also be invited to vote.<div class=""><br class="">6) Past committee members including those who have stood down due to length of service may stand for re-election<br class=""><br class=""></div><div class="">7) Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.<br class=""><br class="">I would ask committee members (and list participants) to comment on this proposal by 18.00 GMT Wednesday 14th September. I will then call for a vote amongst committee members only, the vote will close at 18.00 GMT on Sunday 18th September. <br class=""><br class="">Once the membership policy has been agreed we will then need to apply the policy to the existing membership. I suggest that we ask all current members to confirm whether they wish to remain committee members and then hold an election (if needed). To this end it would be helpful if each committee member could update their record on the wiki page to show when they joined the conference committee (see my example). <br class=""><br class="">The intention is that a 2016-7 committee of 11 will have been selected before we vote on the LoI’s for 2018, which is likely to be before the end of October.</div></div></div></div></blockquote></div><br class=""></div></div><br class="">______________________________<wbr class="">_________________<br class="">
Conference_dev mailing list<br class="">
<a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">
<a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank" class="">http://lists.osgeo.org/<wbr class="">mailman/listinfo/conference_<wbr class="">dev</a><br class=""></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><span style="font-family:Helvetica" class=""><font size="1" class=""><div class="">Helena Mitasova</div><div class=""><div class="">Professor</div><div class="">Department of Marine, Earth and Atmospheric Sciences</div><div class="">North Carolina State University</div><div class="">1125 Jordan Hall</div><div class="">NCSU Box 8208</div><div class="">Raleigh, NC 27695-8208</div><div class=""><a href="http://www4.ncsu.edu/~hmitaso/" target="_blank" class="">http://www4.ncsu.edu/~hmitaso/</a></div><div class=""><a href="http://geospatial.ncsu.edu/" target="_blank" class="">http://geospatial.ncsu.edu/</a></div><div class=""><br class=""></div><div class="">email: <a href="mailto:hmitaso@ncsu.edu" target="_blank" class="">hmitaso@ncsu.edu</a></div><div class="">ph: 919-513-1327 (no voicemail)</div><div class="">fax 919 515-7802</div></div></font></span></div></div></div></div>
</div></div></div>
</div></blockquote></div><br class=""></div></body></html>