<div dir="ltr">Cameron,<div><br></div><div>It should be in both. If we are expecting a future event to comply it *must* be in the RFP.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 20, 2016 at 1:30 PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with Eli that we should write a best practice policy statement over use of email addresses. I suggest storing in the FOSS4G Cookbook rather than the RFP. Someone want to volunteer to write this section once this email thread completes?<br>
<br>
<a href="https://wiki.osgeo.org/wiki/FOSS4G_Handbook" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/FO<wbr>SS4G_Handbook</a><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 21/12/2016 5:36 AM, Eli Adam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
The email list which has been accumulated since 2007 or before has<br>
been one of the primary inputs that leads to annual success of FOSS4G.<br>
Each year it has been passed on. Boston should get the list from 2015<br>
if not 2016. Also, let's change the 2019 RFP to include list<br>
continuity.<br>
<br>
On Tue, Dec 20, 2016 at 4:27 AM, <<a href="mailto:till.adams@fossgis.de" target="_blank">till.adams@fossgis.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Steven, ConfComm, @Boston-team,<br>
<br>
(I included BLOC, as they are the directly affected)<br>
<br>
@Steven, thanks to jump in here. I digged a little deeper and although the<br>
system we used for registration is not available any more, I am quite sure<br>
(and found some text drafts for this), that we declared not to hand over the<br>
personal data for registration to anybody else. So this excludes your<br>
proposed first option and also to hand over the full list to Boston. Sorry<br>
for that.<br>
<br>
</blockquote>
This page seems to allow contact by email as well as transfer.<br>
<a href="http://2016.foss4g.org/registration.html#tac" rel="noreferrer" target="_blank">http://2016.foss4g.org/registr<wbr>ation.html#tac</a><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think we could do the following:<br>
We, Bonn team, will write one last email, reaching out all the attendees,<br>
give them some last facts about F4G'16, include links on articles about F4G<br>
2016 on several platforms, attach a few selected but really nice pictures<br>
and thank them all for their attendance. In this email we will hint the<br>
people to Boston and the possibility to actively ask for news about F4G'17.<br>
So people can actively get in touch with the Boston team and request for<br>
further information about F4G'17.<br>
</blockquote>
The Bonn LOC can decide what to do but they should do whatever they<br>
can to pass on the list (or at the very least encourage people to<br>
re-subscribe).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Personally I do not like the platforms, where I have to un-check the<br>
pre-checked box "Please send me advertising and further information", even<br>
if you have the opportunity to optout. The end of the story is:<br>
You have to be aware and active, otherwise you get the<br>
information/advertising/whatev<wbr>er-spam.<br>
I prefer the other way around: If people do nothing, they do not get<br>
anything.<br>
<br>
</blockquote>
In 2014, we considered the annual global FOSS4G to be the same event<br>
as previous years and subsequent years. We specify this in our policy<br>
making it entirely clear, "Your personal information is shared with<br>
future FOSS4G events and these are considered to be the same entity,<br>
even though they are run by a different committee.",<br>
<a href="http://2014.foss4g.org/about/privacy-policy/index.html" rel="noreferrer" target="_blank">http://2014.foss4g.org/about/p<wbr>rivacy-policy/index.html</a><br>
<br>
I also consider 2016 to be the same global FOSS4G event. The LOC was<br>
merely the caretaker for one year.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So for the general proceeding on this topic I would propose the following:<br>
First, I would ask BLOC (I like this and really wonder, why we did not have<br>
this idea before ;-)) to deliver an "optin" link and leave the technical<br>
proceeding on this to them.<br>
</blockquote>
Real changes will happen in the 2019 RFP. We can ask things of BLOC<br>
but they are largely free to do what they want.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Second we can ask BLOC to include a(n un-)checked checkbox in their<br>
registration form "Keep me up to date about upcoming F4G events" which<br>
includes to at least pass over their email-adress to future teams. In any<br>
information any future F4G team send out, people get the chance to optout.<br>
</blockquote>
I strongly disagree with this. Global FOSS4G is the same event and<br>
people should be automatically signed up for information on the same<br>
event. Email continuity from year to year for the same event. If the<br>
Bonn LOC was running the conference again, surely the list would be<br>
reused since it is the same event.<br>
<br>
Yes, definitely on an easy and obvious optout/unsubscribe from every<br>
communication. That is just basic good practice and probably the law<br>
in most places.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For the technical stuff I see the problem you lined out. That should be<br>
solved in either way.... just some thoughts on this:<br>
The mailchimp also needs kind of "administrator" ....<br>
A perhaps not perfect but very easy and easy-to-realize solution would be to<br>
create a new mailing list "FOSS4G News" and ask people to register, if they<br>
want get the news-feed.<br>
So every future team can use this address to post their news on their event.<br>
<br>
<br>
Any comments?<br>
</blockquote>
Lots, :). I think the fundamental discussion is whether the annual<br>
global FOSS4G event is the same event or not. Determining this will<br>
help us decide on the path forward. Once we decide, we can clarify in<br>
the RFP for future years. What are your thoughts on whether it is the<br>
same event? Separate from any obligations the Bonn LOC may have<br>
created for themselves and have to fulfill.<br>
<br>
Best regards, Eli<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards, Till<br>
<br>
<br>
<br>
Am 2016-12-20 12:11, schrieb Steven Feldman:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We went through this discussion last year and I’m not sure whether<br>
we reached a conclusion.<br>
<br>
I am in favour of passing 2016 names to 2017 team but I recognise that<br>
data protection rules are a constraint. I see 2 options (others may<br>
chip in with more)<br>
<br>
* Provide the names of all people that ‘ticked the box’ in 2016 -<br>
possibly Boston team should send their first mail to this group with<br>
an explanation of why they are receiving the mail and an optout<br>
* Send one mail to all of the 2016 names saying that we would like<br>
to<br>
pass their details to Boston team and giving them the option to opt<br>
out by replying ‘unsubscribe’ plus they will always have the<br>
option to opt out in the future<br>
<br>
It would be much easier if OSGeo had a mailchimp or equivalent service<br>
that could handle lists and opt outs etc and track mailings, the<br>
service could be used by all our global and regional events. A mail<br>
chimp account would cost $50/month for up to 5,000 mail recipients (<<br>
2,000 is free)<br>
______<br>
Steven<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 20 Dec 2016, at 10:21, <a href="mailto:till.adams@fossgis.de" target="_blank">till.adams@fossgis.de</a> [1] wrote:<br>
<br>
Dear ConfComm,<br>
<br>
I want to discuss and listen to your opinions regarding the<br>
following issue:<br>
Boston asked me to share our attendee list with them, so they can<br>
contact our attendees and deliver their news to them.<br>
<br>
As all non-americans among us might know, we have strict privacy<br>
laws here in Europe. So this is one point and another one is, that<br>
we do not know, whether participants of F4G 2016 are happy to get<br>
contacted by the Boston team. Some of them may, some not. It's even<br>
unsure that those, that registered for Bonn and checked the box,<br>
that they want to get updates from us really like to get contacted<br>
from the next team.<br>
And - as said - I am kind of unsure, how the legal position is, when<br>
I pass the list over...<br>
<br>
Do not understand me wrong: I support the Boston team on all<br>
questions and I am happy to help them, but before passing over the<br>
list, I'd like to know about your positions.<br>
Perhaps we also can derive some rules on how to proceed with the<br>
attendees lists in the following years?<br>
<br>
Kind regards & happy Chrismas to everybody,<br>
<br>
Till<br>
______________________________<wbr>_________________<br>
Conference_dev mailing list<br>
<a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a> [2]<br>
<a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/conference_dev</a><br>
</blockquote>
<br>
<br>
<br>
Links:<br>
------<br>
[1] mailto:<a href="mailto:till.adams@fossgis.de" target="_blank">till.adams@fossgis.de</a><br>
[2] mailto:<a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.os<wbr>geo.org</a><br>
</blockquote>
<br>
______________________________<wbr>_________________<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="http://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/conference_dev</a><br>
</blockquote>
______________________________<wbr>_________________<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="http://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/conference_dev</a><br>
</blockquote>
<br></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
Cameron Shorter<br>
M <a href="tel:%2B61%20419%20142%20254" value="+61419142254" target="_blank">+61 419 142 254</a></font></span><div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<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="http://lists.osgeo.org/mailman/listinfo/conference_dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/conference_dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">************************************<br>David William Bitner<div>dbSpatial LLC</div><div>612-424-9932</div></div>
</div>