<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="">Jachym<div class=""><br class=""></div><div class="">Board</div><div class="">=====</div><div class=""><br class=""></div><div class="">Just to clarify 2) the board is only invited to vote in the selection of new conference committee members to ensure that we do not become a self perpetuating body. The board does not vote in the selection of the conference proposals 3) although it has the final right to approve or reject the recommendation of the conference committee.</div><div class=""><br class=""></div><div class="">Conflict of interest</div><div class="">==============</div><div class=""><br class=""></div><div class="">I agree with you.</div><div class=""><br class=""></div><div class="">This came up as a possible issue in the 2017 selection process and there was no clarity about whether a member of the committee could/should vote if they had an interest. The intention is that in the voting process a committee member should not vote if they are part of the bid team or employed by a company active in the bid. Usually we would expect a member to withdraw voluntarily but in the event that that did not happen or that there was dispute, the Chair has the ability to decide.</div><div class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; border-spacing: 0px;">______<br class="">Steven<br class=""><br class=""></span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 12 Sep 2016, at 11:42, Jachym Cepicky <<a href="mailto:jachym.cepicky@gmail.com" class="">jachym.cepicky@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: 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; -webkit-text-stroke-width: 0px;" class="">Hi Steve,<div class=""><br class=""></div><div class="">thank you for taking this action (we need this on every level of OSGeo, we lack on people with little bit free time).</div><div class=""><br class=""></div><div class="">Some issues inline: </div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">pá 9. 9. 2016 v 16:41 odesílatel Steven Feldman <<a href="mailto:shfeldman@gmail.com" class="">shfeldman@gmail.com</a>> napsal:<br class=""></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 style="word-wrap: break-word;" class="">This mail is aimed at the current members of the Conference Committee (we do not have a private list). <div class=""><br class=""></div><div class="">Only committee members can vote on these proposals, others on this list are welcome to comment and committee members will hopefully take note of those opinions when voting on the matters proposed.<br class=""><br class="">The current membership of the conference committee is listed at <a href="https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members" target="_blank" class="">https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members</a>. We have 19 members after Dave McIlhagga resigned and after we co-opted Till Adams as the chair of FOSS4G2016. There is currently no policy or rule for eligibility nor for requiring a member to retire after a period of time. <br class=""><br class="">I have suggested in the past that we needed to have an open and fair process for selecting members and limiting the maximum number of committee members. At the face to face it was agreed that I should propose a policy.<br class=""><br class="">I propose the following:<br class=""><br 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 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></div></blockquote><div class=""><br class=""></div><div class="">So far, it was Conference committee who gave "clue" to the Board and board did the final decision (after all, they are "sitting" on the money). I think, this works well. Board's voice was important only if Board would strongly disagree with Conference committee (never happen afaik), or when there was a tie (happend twice, AFAIK).</div><div class=""> </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 style="word-wrap: break-word;" class=""><div class=""><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></div></blockquote><div class=""><span style="line-height: 1.5;" class=""><br class=""></span></div><div class=""><span style="line-height: 1.5;" class="">Please define conflict of interest! It was FOSS4G 2014 vote (DC vs. Portland), where several members of LOC in DC were told, they might be in conflict of interest. Their relationship to LOC was only "supportive", they had no real relationship to any decision and in the matter of fact, they hoped to help the LOC and being connection betweeen LOC and OSGeo, if they are both - in Conference Committee and in LOC. This was (IMHO) one of biggest crises of OSGeo and it should be clearly stated for the future, that membership in LOC and Conference Committee is either to be seen as OK or conflicting.</span></div><div class=""><br class=""></div><div class="">Today I think: there is no reason for having one person in both - LOC and Conf. comm.</div><div class=""><span style="line-height: 1.5;" class=""> </span><br class=""></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 style="word-wrap: break-word;" class=""><div class=""><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="">==========================================</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=""></div></div></blockquote><div class=""><br class=""></div><div class="">... or any other member of LOC, suggested by the chair of most recent FOSS4G</div><div class=""> </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 style="word-wrap: break-word;" class=""><div 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) 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.<span style="line-height: 1.5;" class=""> </span></div></div></div></blockquote><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 style="word-wrap: break-word;" class=""><div class=""><div class=""><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.<br class=""><div class=""><span style="border-collapse: separate; line-height: normal; border-spacing: 0px;" class="">______<br class="">Steven<br class=""><br class=""></span></div></div></div></div></div><br class=""></blockquote><div class="">Jachym </div></div></div></div></div></blockquote></div><br class=""></div></body></html>