<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">1) Over a year ago we tried to agree procedures to manage the size of the committee, the adoption of new members, quorums etc. That generated a lot of heat and subsequently we adopted the process/rules that are in the wiki at <a href="https://wiki.osgeo.org/wiki/Conference_Committee#Decisions" class="">https://wiki.osgeo.org/wiki/Conference_Committee#Decisions</a> and <a href="https://wiki.osgeo.org/wiki/Conference_Committee#Membership" class="">https://wiki.osgeo.org/wiki/Conference_Committee#Membership</a><div class=""><br class=""></div><div class="">The main (or only) role that is reserved for Committee Members is the selection of the Team/Location for the annual FOSS4G all other discussion and activities e.g. wiki maintenance, maintaining/updating the RfP docs and process, organising the Travel Grant Programme (anything else?) are open to anyone who participates on the Conerence_Dev list. </div><div class=""><ul class="MailOutline"><li class="">I suggest that we do need to keep the number of Committee Members to a manageable number to ensure that we get a quorum from the active members (we initially failed to have a quorum for the LoI phase this year) and were quite light for the final phase</li><li class="">The selection of the global FOSS4G is the most significant (and risky) decision that OSGeo takes each year. The surpluses are the principal source of funding for the foundation and when we offer a guarantee and seed funding to an LOC there is potential for substantial exposure for OSGeo. To me it makes sense that this selection is made by people who have relatively recent experience of running a FOSS4G and the challenges and finances involved. I agree with those who have said that even a large regional event is not comparable.</li><li class="">For these reasons I have voted in another thread to support Guido and Michael and mildly against (but not vetoing) Gerard</li></ul><div class=""><br class=""></div></div><div class="">2) I thought the thumbs up/down process for selecting LoIs worked well it allows all of the good proposals to go to the next stage while allowing us to reject a proposal that fails to impress more than half the voting members</div><div class=""><br class=""></div><div class="">3) I am in favour of mandating a standard response format for the full proposals (much as many of us who tend for public sector contracts have grown used to)</div><div class=""><br class=""></div><div class="">May the FOSS be with you</div><div class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px;">______<br class="">Steven<br class=""><br class=""></span>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 23 Jan 2018, at 11:33, Till Adams <<a href="mailto:till.adams@fossgis.de" class="">till.adams@fossgis.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Conference comittee,<br class=""><br class="">this is a general reminder on some decisions/discussions, that I have on<br class="">my list we have to talk about in the following weeks. This email serves<br class="">just as a general list-up with the hope, that you'll find some time to<br class="">think about some of my issues. If you have your own things to bring in,<br class="">feel free to share!<br class=""><br class="">I will list these points as seperate issues below and would be happy if<br class="">we start a discussion:<br class=""><br class="">1. Voting Members<br class=""><br class="">For the last RfP, where we nominated Bucharest as venue for the 2019<br class="">conference, we had a weak quorum, because quite some members did not<br class="">vote. I sent out personal emails to the non-voters and received feedback<br class="">from 3 of the 5 non-voters. These 3 excused themselves, they had reasons<br class="">and they are willing to stay on board and that makes me happy.<br class=""><br class="">Leads me to the question, that I still did not get any feedback from the<br class="">other 2. Now it's already some weeks ago that I contacted them,<br class="">including a remembering mail.<br class="">I don't know if we have an official trial to rule out people and<br class="">personnally I wouldn't like to do that, because I know at least one of<br class="">the 2 personally.<br class="">On the other side, we can't be sure, that they will appear back once<br class="">upon a time. Not re-appearing means that we have to fear more weak<br class="">quorums in the future.<br class=""><br class="">Issue 1: How do we act here?<br class=""><br class="">This directly leads me to question 2: I will nominate Guido Stein and<br class="">Michael Terner as new members for the CC later. I think as former chairs<br class="">of a successful global FOSS4G conference, it is without question clear,<br class="">that we need them as new members in CC. Also there was a request of<br class="">Gerald Fenoy back this summer, where he asked for participation as member.<br class="">I am little unsure here, because I fear, that we will have a huge CC<br class="">within a few years, when we also nominate all past chairs of regional<br class="">events. In my eyes (without rating!!!) organizing a regional event is a<br class="">cmletely different game than having a global FOSS4G. And our job is to<br class="">vote on proposals for global conferences venues. On the other side, of<br class="">course, having some more active members inside CC wouldn't be the badest<br class="">idea.<br class=""><br class="">Issue 2: Accept nomination of Gerald Fenoy (and potential other regional<br class="">chairs?) ?<br class=""><br class=""><br class="">2. Voting process<br class="">We discussed to alter the voting process, so that for step 1 (LOI<br class="">acceptance) of the RfP 2019 we had this new "thumbs up"/"thumbs down"<br class="">vote. I will soon call for a vote, whether we want to keep this<br class="">procedure or go back to the old "one vote per member" also for step 1.<br class=""> <br class=""><br class="">3. Bid process<br class="">I do not know, how you felt in the last RfP. I had problems in comparing<br class="">the two proposals, because one of them was very close to the draft we<br class="">gave out and the Sevilla one was, let's say, "freely interpreted" ;-).<br class="">I don't want to limit the teams' individual imagination, but perhaps it<br class="">would be easier for comparing the proposals, if all proposals would have<br class="">the same agenda. This also would save the teams from spending money on a<br class="">marketing agency for layout things (I do not want to impute, that this<br class="">happened in 2019, but this *might* happen in the future in order to put<br class="">one proposal in a better light). I wil call for a vote on this issue<br class="">soon as well.<br class=""><br class=""><br class="">So far, have a nice day!<br class=""><br class="">Till<br class=""><br class=""><br class=""><br class=""><br class=""> <br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br 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="">https://lists.osgeo.org/mailman/listinfo/conference_dev</div></div></blockquote></div><br class=""></div></body></html>