<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I favour a time out after say 3/4 years, or on some other basis, with the option to stand for re-election if a member wishes to continue on committee<br><br><div id="AppleMailSignature">Regards<div>Steven</div><div><br></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><br></span></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">+44 (0) 7958 924101</span></div><div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Sent from my iPhone</span></div></div></div><div><br>On 12 Sep 2018, at 21:26, Guido Stein <<a href="mailto:gstein@appgeo.com">gstein@appgeo.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>Folks,</div><div><br></div><div>To Stevens point about thinning the committee members to make sure that we can get quorum:</div><div><br></div><div>I agree that the committee should be made up of people who are active. I know that many of the past chairs have been interested and supportive of the process and that some have gotten too busy or moved on from this community. I think it's would help to setup some rule about participation to help determine who is on the committee. </div><div><br></div><div>If for example a committee member has been absent from a vote more than 3 years, they probably don't have any interest in voting in the next year. It would make sense to remove them from the committee.</div><div><br></div><div>Would people be willing to set a activity flag for removing inactive committee members?</div><div><br></div><div>-Guido</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 12, 2018 at 5:56 AM Steven Feldman <<a href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would like to publicly oppose the proposal (oppose not veto). I wish to stress that my opposition to the proposal does not in any way signify an objection to Gerard per se, it is a concern about the membership criteria of the Conference Committee.<br>
<br>
The Conference Committee (as opposed to the mailing list which is open to everyone) has, until recently, had only one task - to run the process to select the team to run the Global FOSS4G event. The open list can review the LoI’s and ask questions of the bidders but voting is restricted to CC members. In the last 2 years the CC has also been entrusted with running the FOSS4G Travel Grant Programme.<br>
<br>
I believe that the CC has grown too large and that without a process to retire members (I believe we have a mechanism in the current terms of reference which could/should be activated before this motion is considered) we are in danger of failing to have a quorum for decisions.<br>
<br>
In the 2019 selection process last year we failed to reach a quorum of >50% in the final vote and the CRO had to request the chair of CC to encourage additional members to vote. CC is now larger than 2017 and there is a proposal to vote on accepting another member, theoretically anyone could propose further regional chairs or any other person to be appointed to CC, this is not sustainable in my opinion. Membership of CC should not be an honour that is bestowed upon former chairs of regional events (Charter Membership is our way of honouring people who have made a strong contribution to our community). <br>
<br>
CC’s principal task is running the global FOSS4G selection, I believe that the membership should have experience of running a global FOSS4G. This does not prevent other interested people from expressing opinions or asking questions on the list it just reserves the most important financial decision that OSGeo makes each year (OSGeo offer financial guarantees and loans of up to $80k to a FOSS4G LOC) to people who have experience of running previous events with budgets of ca $500k. The invitation of past chairs of global FOSS4G to join the CC ensures that we retain our communal knowledge, experience and judgement.<br>
<br>
I previously proposed that we reduce the size of CC to 11 members and have a mandatory retirement and re-election process. That proposal gained a lot of support but was vetoed, I will not propose it again but I do ask CC members to suggest an alternative way forward that will not lead to an ever growing CC, a dilution of expertise and further potential inquorate votes.<br>
<br>
BTW if others want to be more involved in CC activities, the TGP team struggled to get volunteers to run the Dar TGP or to assist on regional events. We need volunteers, the TGP work is quite time consuming and the burden currently falls on 2 or 3 people. You do not need to be a member of CC to participate in the TGP.<br>
______<br>
Steven<br>
<br>
<br>
> On 12 Sep 2018, at 07:59, Till Adams <<a href="mailto:till.adams@fossgis.de" target="_blank">till.adams@fossgis.de</a>> wrote:<br>
> <br>
> Dear ConfComm,<br>
> <br>
> last topic today: Membership in CC.<br>
> <br>
> Past chairs of a global conference are automatically asked to become<br>
> members of CC. If they agree, they are proposed as new members to CC and<br>
> voted. If there are proposals for other, non-former-global chair people<br>
> as new members, please propose them on the list after the global<br>
> conference is over and prior to the RfP for the next FOSS4G (maybe this<br>
> year we make an exception and extend this phase until the end of September).<br>
> <br>
> There has also been some discussion on the election procedure. I would<br>
> propose the following procedure:<br>
> <br>
> We are currently 19 members. If a candidate receives at least 10 "+1"<br>
> votes on the mailing list within 7 days after being proposed, the<br>
> candidate will be accepted as a new member. With this procedure you can<br>
> actively vote *for* a candidate, but you don't have to actively vote<br>
> *against* someone. Of course, the right of a veto ("-1") is retained,<br>
> but, as always, a "-1" must be justified and if possible, an alternative<br>
> proposal must be given. If this does not happen, the veto will be ignored.<br>
> <br>
> Regarding the election procedure, I have the following proposal: If you<br>
> want to vote publicly, you can do so just by sending an email to this<br>
> list. Alternatively, in case of a proposed candidate, I will name 2<br>
> election assistants, to whom a vote can be sent by e-mail. At the end of<br>
> the election period we receive only the number of the "+1" votes without<br>
> names of the voters from them.<br>
> <br>
> Vetoes must be publicly justified.<br>
> <br>
> <br>
> Please vote on ths proposal until 19th of September, if we agree in this<br>
> procedure, I can do the changes in the WIKI [1].<br>
> <br>
> <br>
> Till<br>
> <br>
> <br>
> [1] <a href="https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members</a><br>
> <br>
> _______________________________________________<br>
> Conference_dev mailing list<br>
> <a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
<br>
_______________________________________________<br>
Conference_dev mailing list<br>
<a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/conference_dev</a></blockquote></div>
<br>
<span style="color:rgb(128,128,128);font-family:'Courier New';font-size:10px;background-color:rgb(255,255,255)">This e-mail message and any attachments may contain confidential or legally privileged information. If you are not an intended recipient or otherwise authorized to receive this message, you should not use, copy, distribute, disclose or take any action based on the information contained in this e-mail or any attachments. If you have received this message and material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you on behalf of Applied Geographics, Inc. (AppGeo).</span></div></blockquote></body></html>