<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">Hi all,</div><div style="direction: inherit;">This proposal looks good to me. +1</div><div style="direction: inherit;">I'll immediately take a step to make the reduction of the committee size easier by stepping down. It was great to work with you. </div><div style="direction: inherit;">Cheers,</div><div style="direction: inherit;">Jeroen</div><br><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer, MapServer, PostGIS and GeoNetwork. Visit <a href="http://geocat.net">http://geocat.net</a> for details. </span></div>_________________________<div>Jeroen Ticheler</div><div>GeoCat bv</div><div>Veenderweg 13</div><div>6721 WD Bennekom</div><div>Tel: +31 (0)6 81286572</div><div><a href="http://geocat.net">http://geocat.net</a></div></div><div><br>Op 9 sep. 2016 om 23:10 heeft Eli Adam <<a href="mailto:eadam@co.lincoln.or.us">eadam@co.lincoln.or.us</a>> het volgende geschreven:<br><br></div><blockquote type="cite"><div><span>This sounds good. Specifics below.</span><br><span></span><br><span>On Fri, Sep 9, 2016 at 7:41 AM, Steven Feldman <<a href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>> wrote:</span><br><blockquote type="cite"><span>This mail is aimed at the current members of the Conference Committee (we do</span><br></blockquote><blockquote type="cite"><span>not have a private list).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Only committee members can vote on these proposals, others on this list are</span><br></blockquote><blockquote type="cite"><span>welcome to comment and committee members will hopefully take note of those</span><br></blockquote><blockquote type="cite"><span>opinions when voting on the matters proposed.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The current membership of the conference committee is listed at</span><br></blockquote><blockquote type="cite"><span><a href="https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members">https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members</a>. We have 19</span><br></blockquote><blockquote type="cite"><span>members after Dave McIlhagga resigned and after we co-opted Till Adams as</span><br></blockquote><blockquote type="cite"><span>the chair of FOSS4G2016. There is currently no policy or rule for</span><br></blockquote><blockquote type="cite"><span>eligibility nor for requiring a member to retire after a period of time.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I have suggested in the past that we needed to have an open and fair process</span><br></blockquote><blockquote type="cite"><span>for selecting members and limiting the maximum number of committee members.</span><br></blockquote><blockquote type="cite"><span>At the face to face it was agreed that I should propose a policy.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I propose the following:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Goals</span><br></blockquote><blockquote type="cite"><span>=====</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The conference committee have the responsibility to run the selection</span><br></blockquote><blockquote type="cite"><span>process and voting for the global FOSS4G, to vote on other proposals</span><br></blockquote><blockquote type="cite"><span>submitted to the committee and to advise the board on other matters relating</span><br></blockquote><blockquote type="cite"><span>to FOSS4G events.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Role of the Committee and the broader community on the Conference_Dev list</span><br></blockquote><blockquote type="cite"><span>============================================================</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>1) Everyday topics will be decided upon by an open vote of all list</span><br></blockquote><blockquote type="cite"><span>participants in a clearly designated separate mail thread (+1/-1) over a</span><br></blockquote><blockquote type="cite"><span>minimum of two business days with a minimum participation of 3 votes.</span><br></blockquote><blockquote type="cite"><span>Ideally we aim for consensus falling back on simple majority vote where</span><br></blockquote><blockquote type="cite"><span>necessary. The result will be clearly declared afterwards (or whatever is</span><br></blockquote><blockquote type="cite"><span>decided).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>2) Election of conference committee is by secret vote and restricted to the</span><br></blockquote><blockquote type="cite"><span>remaining conference committee members and board members who are not members</span><br></blockquote><blockquote type="cite"><span>of the conference committee.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>3) FOSS4G Selection - All Letters of Intent and subsequent proposals will be</span><br></blockquote><blockquote type="cite"><span>posted to the list for open comment by all participants. The selection of</span><br></blockquote><blockquote type="cite"><span>the winning proposal is by secret vote of conference committee members only.</span><br></blockquote><blockquote type="cite"><span>Any committee member who has a potential conflict of interest is expected to</span><br></blockquote><blockquote type="cite"><span>withdraw from vote. In the event of a disagreement the committee chair will</span><br></blockquote><blockquote type="cite"><span>decide.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Votes in 2 and 3 are to an online voting service or by email to an</span><br></blockquote><blockquote type="cite"><span>independent teller appointed by CC Chair</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Conference Committee membership policy and process</span><br></blockquote><blockquote type="cite"><span>==========================================</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>1) The conference committee aims to retain up to 11 active members,</span><br></blockquote><blockquote type="cite"><span>preferably an odd number</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>2) The committee aims for half of these members to be chairs (or vice</span><br></blockquote><blockquote type="cite"><span>chairs) of the most recent FOSS4G global events. The chair of the most</span><br></blockquote><blockquote type="cite"><span>recent FOSS4G event will automatically be invited to become a member</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>3) The remaining membership is open, ideally attracting people from earlier</span><br></blockquote><blockquote type="cite"><span>past chairs or active LOC members from past Global, Regional FOSS4G or</span><br></blockquote><blockquote type="cite"><span>related conferences</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>4) Each year (after FOSS4G) the 3 committee members should stand down:</span><br></blockquote><blockquote type="cite"><span>a) The longest standing past FOSS4G chair</span><br></blockquote><blockquote type="cite"><span>b) The longest standing 2 committee members remaining</span><br></blockquote><span></span><br><span>This might be better phrased and thought of as as "expired terms"</span><br><span>rather than an active "stand down." (Or this might be an American</span><br><span>English vs. British English thing.)</span><br><span></span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>5) Each year, prior to putting out the Global FOSS4G RfP, the old committee</span><br></blockquote><blockquote type="cite"><span>should vote for their replacement committee, using the above criteria as</span><br></blockquote><blockquote type="cite"><span>voting guidelines. OSGeo Board members who are not on the conference</span><br></blockquote><blockquote type="cite"><span>committee will also be invited to vote.</span><br></blockquote><span></span><br><span>You wrote "old committee" could this be clarified? Do you mean:</span><br><span>"remaining committee members"? How is this phrasing:</span><br><span></span><br><span>Each year, prior to releasing the Global FOSS4G RfP, the remaining</span><br><span>committee members should fill available vacancies, using the above</span><br><span>criteria as voting guidelines. OSGeo Board members who are not on the</span><br><span>conference committee will also be invited to vote.</span><br><span></span><br><span></span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>6) Past committee members including those who have stood down due to length</span><br></blockquote><blockquote type="cite"><span>of service may stand for re-election</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>7) Votes will be secret either using an online voting system or by email to</span><br></blockquote><blockquote type="cite"><span>a designated teller who is not a voter. The mechanism will be selected by</span><br></blockquote><blockquote type="cite"><span>the committee chair.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I would ask committee members (and list participants) to comment on this</span><br></blockquote><blockquote type="cite"><span>proposal by 18.00 GMT Wednesday 14th September. I will then call for a vote</span><br></blockquote><blockquote type="cite"><span>amongst committee members only, the vote will close at 18.00 GMT on Sunday</span><br></blockquote><blockquote type="cite"><span>18th September.</span><br></blockquote><span></span><br><span>I like a clear schedule of activity here. We discuss until 18.00 GMT</span><br><span>Wednesday 14th September, then (after any revisions from the</span><br><span>discussion) you call for a vote which will close 18.00 GMT on Sunday</span><br><span>18th September.</span><br><span></span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Once the membership policy has been agreed we will then need to apply the</span><br></blockquote><blockquote type="cite"><span>policy to the existing membership. I suggest that we ask all current members</span><br></blockquote><blockquote type="cite"><span>to confirm whether they wish to remain committee members and then hold an</span><br></blockquote><blockquote type="cite"><span>election (if needed). To this end it would be helpful if each committee</span><br></blockquote><blockquote type="cite"><span>member could update their record on the wiki page to show when they joined</span><br></blockquote><blockquote type="cite"><span>the conference committee (see my example).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>I've updated the wiki and enjoy contributing to the committee and am</span><br><span>happy to continue as a member for another term.</span><br><span></span><br><span>Best regards, Eli</span><br><span></span><br><blockquote type="cite"><span>The intention is that a 2016-7 committee of 11 will have been selected</span><br></blockquote><blockquote type="cite"><span>before we vote on the LoI’s for 2018, which is likely to be before the end</span><br></blockquote><blockquote type="cite"><span>of October.</span><br></blockquote><blockquote type="cite"><span>______</span><br></blockquote><blockquote type="cite"><span>Steven</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>Conference_dev mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a></span><br></blockquote><blockquote type="cite"><span><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></span><br></blockquote><span>_______________________________________________</span><br><span>Conference_dev mailing list</span><br><span><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a></span><br><span><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></span></div></blockquote></body></html>