<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ks_c_5601-1987">
<meta content="text/html; charset=ks_c_5601-1987">
<meta content="text/html; charset=utf-8">
</head>
<body class="" style="word-wrap:break-word">
<div>I'm sending it again because I can't see it in the mailbox and in the archive...</div>
<div>Thanks.</div>
<div>Maria </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id="composer_signature">
<div style="font-size:85%; color:#575757">Sent from my Samsung device</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Maria Antonia Brovelli <maria.brovelli@polimi.it> <br>
Date: 16/09/2016 08:14 (GMT+01:00) <br>
To: Sanghee Shin <shshin@gaia3d.com>, Steven Feldman <shfeldman@gmail.com> <br>
Cc: OSGeo-Conf <conference_dev@lists.osgeo.org> <br>
Subject: RE: [OSGeo-Conf] MOTION : Conference Committee - Updating Membership Policies and Process
<br>
<br>
<div>
<div>-1 until the mechanism of voting has been revised. </div>
<div>Many thanks Steve!</div>
<div>Maria</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id="composer_signature">
<div style="font-size:85%; color:#575757">Sent from my Samsung device</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Sanghee Shin <shshin@gaia3d.com> <br>
Date: 15/09/2016 22:04 (GMT+01:00) <br>
To: Steven Feldman <shfeldman@gmail.com> <br>
Cc: OSGeo-Conf <conference_dev@lists.osgeo.org> <br>
Subject: Re: [OSGeo-Conf] MOTION : Conference Committee - Updating Membership Policies and Process
<br>
<br>
<div>+1 from me. Thanks Steven for your leading this and great efforts.
<div class=""><br class="">
</div>
<div class="">Cheers,
<div class="">
<div class="">½Å»óÈñ<br class="">
---<br class="">
Shin, Sanghee<br class="">
Gaia3D, Inc. - The GeoSpatial Company<br class="">
<a href="http://www.gaia3d.com" class="">http://www.gaia3d.com</a> </div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">2016. 9. 15., ¿ÀÀü 7:25, Steven Feldman <<a href="mailto:shfeldman@gmail.com" class="">shfeldman@gmail.com</a>> ÀÛ¼º:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="" style="word-wrap:break-word">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="">============================================================</div>
<div class=""><br class="">
</div>
<div class="">
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">4) Any committee member who has a potential conflict of interest is expected to withdraw from vote. A </span>member<span class="" style=""> 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="" style=""> 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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal">Conference Committee membership policy and process</div>
<div class="" style="margin:0px; line-height:normal">==========================================</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 class="Apple-style-span" style="border-collapse:separate; line-height:normal; border-spacing:0px">______<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" class="">shfeldman@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
Goals</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
=====</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<br class="">
</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
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="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<br class="">
</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
Role of the Committee and the broader community on the Conference_Dev list</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
============================================================</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<br class="">
</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="margin:0px; line-height:normal"><span class="" style=""><br class="">
</span></div>
<div class="" style="margin:0px; line-height:normal"><span class="" style="">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 class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; margin:0px; line-height:normal">
<span class="" style=""><br class="">
</span></div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; margin:0px; line-height:normal">
Conference Committee membership policy and process</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; margin:0px; line-height:normal">
==========================================</div>
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<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="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
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="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
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="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
<div class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px">
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="">
Conference_dev mailing list<br class="">
<a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">
http://lists.osgeo.org/mailman/listinfo/conference_dev</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</body>
</html>