<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Thanks a lot Thomas!</div>
<div>Cheers</div>
<div>Maria</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id="x_composer_signature">
<div style="font-size:85%; color:#575757">Inviato dal mio dispositivo Samsung</div>
</div>
<br>
<br>
-------- Messaggio originale --------<br>
Da: thomas bonfort <thomas.bonfort@gmail.com> <br>
Data: 29/09/2016 11:27 (GMT+01:00) <br>
A: Cameron Shorter <cameron.shorter@gmail.com> <br>
Cc: "<conference_dev@lists.osgeo.org>" <conference_dev@lists.osgeo.org> <br>
Oggetto: Re: [OSGeo-Conf] Voting officer needed for FOSS4G 2018 selection <br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Ack. I will go for the email process.<br>
I will keep monitoring this list and will send out individual emails<br>
with voting instructions to the 16 committee members for both voting<br>
periods.<br>
Best regards,<br>
Thomas<br>
<br>
On 28 September 2016 at 13:11, Cameron Shorter<br>
<cameron.shorter@gmail.com> wrote:<br>
> Hi Thomas,<br>
><br>
> Yes, as Steven says, thanks for taking on the CRO role, and I'm fine with<br>
> your proposed process.<br>
><br>
> Cheers, Cameron<br>
><br>
><br>
><br>
> On 28/09/2016 6:45 PM, Steven Feldman wrote:<br>
>><br>
>> First off a big thank you to Thomas for taking on the roll of CRO. I am<br>
>> very grateful.<br>
>><br>
>> We have always used a CRO and email in the past, I have no hesitation in<br>
>> supporting that approach if it is Thomas’s preference. If Thomas wishes to<br>
>> trial a web voting system I am fine with that too.<br>
>><br>
>> The first vote is 17th/18th October - 16 voters (if all the committee<br>
>> votes) to select one Letter of Intent<br>
>> Second vote is 9th/12th December - 16 voters (if all the committee votes)<br>
>> to select one Proposal with second choice votes to be used in the event of a<br>
>> tie in the first round<br>
>><br>
>> I will leave it to Thomas to decide how to administer the voting<br>
>><br>
>> Thanks<br>
>> ______<br>
>> Steven<br>
>><br>
>><br>
>>> On 28 Sep 2016, at 08:21, thomas bonfort <thomas.bonfort@gmail.com><br>
>>> wrote:<br>
>>><br>
>>> Hi Cameron,<br>
>>> I believe the integrity of the vote is guaranteed by the "secret"<br>
>>> token, as each voter can check his vote was accounted for correctly.<br>
>>> This manual process does not however guarantee anonymity as the CRO<br>
>>> has access to each voter's choice.<br>
>>> My experience being cro with limesurvey for osgeo-fr was rather<br>
>>> negative as I had to spend much more time dealing with the survey<br>
>>> itself than I would have to manually deal with the process (and IIRC<br>
>>> at the time anonymity was not guaranteed as the survey admin could<br>
>>> correlate votes with voters through the voting token).<br>
>>> Best regards,<br>
>>> Thomas<br>
>>><br>
>>> On 28 September 2016 at 08:56, Cameron Shorter<br>
>>> <cameron.shorter@gmail.com> wrote:<br>
>>>><br>
>>>> Hi Thomas,<br>
>>>><br>
>>>> I suspect that Lime Survey provides the ability to guarantee the that<br>
>>>> the<br>
>>>> voting process hasn't been tampered with - ensuring that we can see who<br>
>>>> has<br>
>>>> voted, the results of the vote, but not how each person voted. (Jorge,<br>
>>>> can<br>
>>>> you please confirm this is the case).<br>
>>>><br>
>>>> Such a voting system is preferable to having a person acting as a CRO,<br>
>>>> where<br>
>>>> the integrity of the CRO might be questioned. (Thomas, this is more of a<br>
>>>> protection of the CRO, rather than a question of the CRO's integrity).<br>
>>>><br>
>>>> Warm regards, Cameron<br>
>>>><br>
>>>> On 28/09/2016 7:51 AM, thomas bonfort wrote:<br>
>>>><br>
>>>> Hi Jorge,<br>
>>>> Thanks for the offer.<br>
>>>> Given the number of voters from my point of view it seems easier to<br>
>>>> handle<br>
>>>> this manually than to setup and track a limesurvey. I'm fine to back off<br>
>>>> with my offer if the limesurvey proposal is preferred.<br>
>>>> Best regards,<br>
>>>> Thomas<br>
>>>><br>
>>>><br>
>>>> On Sep 27, 2016 11:35 PM, "Jorge Sanz" <jsanz@osgeo.org> wrote:<br>
>>>>><br>
>>>>> Hi Thomas,<br>
>>>>><br>
>>>>> At this very moment I'm happily working to set up the Board of<br>
>>>>> Directors voting on the LimeSurvey instance Geo-Spatial community set<br>
>>>>> up for OSGeo.<br>
>>>>><br>
>>>>> It's easy to use (and I can assist you) to give to the Conf Committee<br>
>>>>> a place to do the voting with reminders, tokens and everything, if you<br>
>>>>> think it's worth.<br>
>>>>><br>
>>>>> Best regards<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On 27 September 2016 at 22:46, thomas bonfort<br>
>>>>> <thomas.bonfort@gmail.com><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> I can volunteer to be cro for the votes. I will be more or less<br>
>>>>>> offline<br>
>>>>>> from Oct.24 to Nov.21 but that does not seem to interfere with the 2<br>
>>>>>> voting<br>
>>>>>> periods.<br>
>>>>>> With regards to accountancy, I propose that each voting member include<br>
>>>>>> a<br>
>>>>>> token known only to himself that will be published alongside the<br>
>>>>>> voting<br>
>>>>>> result, thus providing a way to be sure his/her vote was accounted for<br>
>>>>>> correctly.<br>
>>>>>> Regards,<br>
>>>>>> Thomas<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Sep 27, 2016 9:18 PM, "Steven Feldman" <shfeldman@gmail.com> wrote:<br>
>>>>>>><br>
>>>>>>> Hi<br>
>>>>>>><br>
>>>>>>> We need someone who is not a member of the conference committee to<br>
>>>>>>> act<br>
>>>>>>> as<br>
>>>>>>> Voting Officer for the 2 stages of voting to select the host for<br>
>>>>>>> FOSS4G<br>
>>>>>>> 2018. Full details of dates and voting procedure at<br>
>>>>>>> <a href="https://wiki.osgeo.org/wiki/FOSS4G_2018_Bid_Process">https://wiki.osgeo.org/wiki/FOSS4G_2018_Bid_Process</a><br>
>>>>>>><br>
>>>>>>> Any offers?<br>
>>>>>>><br>
>>>>>>> Steven<br>
>>>>>>><br>
>>>>>>> _______________________________________________<br>
>>>>>>> Conference_dev mailing list<br>
>>>>>>> Conference_dev@lists.osgeo.org<br>
>>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Conference_dev mailing list<br>
>>>>>> Conference_dev@lists.osgeo.org<br>
>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Jorge Sanz<br>
>>>>> <a href="http://www.osgeo.org">http://www.osgeo.org</a><br>
>>>>> <a href="http://wiki.osgeo.org/wiki/Jorge_Sanz">http://wiki.osgeo.org/wiki/Jorge_Sanz</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Conference_dev mailing list<br>
>>>> Conference_dev@lists.osgeo.org<br>
>>>> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Cameron Shorter<br>
>>>> M +61 419 142 254<br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Conference_dev mailing list<br>
>>>> Conference_dev@lists.osgeo.org<br>
>>>> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Conference_dev mailing list<br>
>>> Conference_dev@lists.osgeo.org<br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
><br>
><br>
> --<br>
> Cameron Shorter<br>
> M +61 419 142 254<br>
><br>
_______________________________________________<br>
Conference_dev mailing list<br>
Conference_dev@lists.osgeo.org<br>
<a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></div>
</span></font>
</body>
</html>