Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Thanks a lot! ;)

Kürti László wrote on 2011-10-06 17:44:
Hi All,

here are my thoughts about organizing the Conf in general as my own experience is:
- time is running out fast but sponsorship deals are slow - so start early
- you (TDF) will need a detailed wish list (and a wish-not list)
- you (TDF) should be able to articulate clearly who is responsible for what (local team vs TDF)
- mind the PR! this IS the biggest OSS app and community
- both party have to describe theres own goal (why this place is good for the Conf and NOT because 
of the beautiful venue)


Laszlo


----- Original Message -----
From: "Sophie Gautier"<gautier.sophie@gmail.com>
To: marketing@global.libreoffice.org
Sent: Sunday, October 2, 2011 3:50:51 PM
Subject: Re: [libreoffice-marketing] call for location 2012

Hi all,

As per Florian request, I'm posting here the draft I made, feel free
to add your mandatory items to the list:

On Mon, Aug 22, 2011 at 1:22 PM, Simon Phipps<simon@webmink.com>  wrote:
[...]

I understood your proposal was to actually announce the new location in Paris. I think that's 
impractical. But I do think it's possible to start the call-for-location process now, promote it in 
Paris, and announce the new location in January. The timeline for 2012 would look something like:

September 1st  : Announce the Call for Location for 2012
October 1st:  PR about the process, announce details of the Selection Panel
Paris conference:  Plenary slot explaining the process and timeline
November  15th:  Applications close
December:  Selection Panel reviews applications
January 15th: Location announced

And for 2013:

September 1st: Mention in PR there will be a 2013 selection process
November 15th:  Announce the Call for Location for 2013
January 15th:  Include news of 2013 process in PR
March:  Promote 2013 Call for Location
May 31st: Applications close
June/July: Selection Panel reviews applications
August 30th: 2013 venue announced
October: @013 team attends and helps with 2012 conference




Points to take into account for the next proposal
+ main venue
- easy to access from international transports
- easy to access from accommodations
- at least 2 big rooms for conf hosting + one for meetings/others +
one place for community gathering

+ team
- at least 5 persons are necessary for the whole organization
- one should be dedicated to sponsor relations and to
invitations/visa, administrative tasks (it's very time consuming).
- have a local NGO for expenses and sponsoring and deal with the money

+ it could be along another event, but should have enough room/meeting
points for our own conf

-------------------------------
Questions for the proposal:
- describe the location
- describe your team
- why would you like to host the conf
- have you local sponsors/organizations
- ?

Kind regards
Sophie

--
Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff

--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.