<p dir="ltr">Fyi - Till has shared the twitter account credentials with me and we will update the account profile towards the end of the month. We are also processing after an amazing event and will ramp up with marketing later this month.</p>
<p dir="ltr">Thanks again to Jeff, for keeping the ball rolling, and Till , for being so proactive.</p>
<p dir="ltr">Guido </p>
<br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 2, 2016, 15:46 Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello 2016 team,<br>
<br>
At the end of each FOSS4G, it's important to take a few moments and make<br>
sure that important information is archived and shared, for future<br>
FOSS4G local committees (yes I send this message each year, some listen<br>
to me, some do not).<br>
<br>
Till, you must have been psychic, because this morning when I woke up I<br>
made some tasks for 2016, and one of them I see you are tackling this<br>
afternoon (lessons learned). Great minds think alike :)<br>
<br>
1) Lessons Learned Wiki<br>
<br>
It's important to fill in any of your thoughts (and this applies to<br>
everyone involved in the local organizing team, not only the chair). The<br>
template is online (Till made a good hack on it today), but others from<br>
all committees are invited to add to it (program committee, workshop<br>
committee, code sprint committee, volunteer committee, etc).<br>
<a href="https://wiki.osgeo.org/wiki/FOSS4G_2016_Lessons_Learned" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/FOSS4G_2016_Lessons_Learned</a> Feel free to add<br>
any sections that are missing. (login with your OSGeo user ID, which<br>
you can create at <a href="http://www.osgeo.org/osgeo_userid" rel="noreferrer" target="_blank">http://www.osgeo.org/osgeo_userid</a> That page also has<br>
links to reset your password etc.)<br>
<br>
2) Archive documents through OSGeo's SVN repository<br>
<br>
I've been archiving FOSS4G documents, since 2004, at<br>
<a href="https://svn.osgeo.org/osgeo/foss4g/" rel="noreferrer" target="_blank">https://svn.osgeo.org/osgeo/foss4g/</a> It has become a great resource for<br>
logos, past sponsor documents, program templates; but some years are<br>
empty (chairs did not agree with my insistence I guess ha). Please,<br>
whether you are on the website committee, program committee, volunteer<br>
committee, code sprint committee, marketing any committee, please be<br>
sure to commit your raw files into<br>
<a href="https://svn.osgeo.org/osgeo/foss4g/2016/" rel="noreferrer" target="_blank">https://svn.osgeo.org/osgeo/foss4g/2016/</a> (use the same OSGeo ID as<br>
mentioned above, and let me know if your user needs write access, I can<br>
approve that fast). Things like the code behind the Community Review<br>
instance, are always looked for by the next year's committee, and if it<br>
is easily accessible in SVN they won't have to search.<br>
<br>
3) Submit the bill for the closing party to Mike Smith, OSGeo Treasurer.<br>
I spoke with Venka that day (Saturday) as you were heading to your<br>
final dinner, and we agreed that this little dinner is a small way that<br>
we can thank you, the whole OSGeo community thanks you, for all your<br>
hard work.<br>
<br>
4) Passing control of @foss4g twitter account<br>
<br>
Usually each year we wait until videos and other news items are<br>
announced by the recent FOSS4G local committee. Your team has been fast<br>
with videos, but there is always a few little items to share in social<br>
media after. I would say after next week, at the end of next week the<br>
Twitter account should be handed over to the 2017 team. (if this seems<br>
too soon we can discuss this) I had the master password, but likely Till<br>
should just let @guidos know privately the account info.<br>
<br>
5) After you have recharged your batteries, plan a 'meeting' of the<br>
local committee again, often this is done a few weeks after the event,<br>
at a pub or a casual dinner place. This to me is very important. I<br>
know, this year you did it on the weekend after, but, I find that you<br>
can REALLY enjoy getting together a few weeks later (even a month<br>
later), and sit down with each other and laugh (and cry ha), and be<br>
proud of what you did. Really, I think this is important. You did it,<br>
you went through it all together, and you will always be bonded by this.<br>
<br>
That's all I can think of right now.<br>
<br>
Thank you to the whole Bonn team, for making FOSS4G 2016 so memorable.<br>
I've followed every step of the way, and I could not be more proud of<br>
your work and passion. It will never be forgotten.<br>
<br>
#boatdrinks<br>
<br>
-jeff<br>
<br>
<br>
<br>
_______________________________________________<br>
FOSS4G2016 mailing list<br>
<a href="mailto:FOSS4G2016@lists.osgeo.org" target="_blank">FOSS4G2016@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/foss4g2016" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g2016</a><br>
</blockquote></div>