Hello Florian, hello Marc,
I don't really care and this decision should not only be mine. What I want
is to have information, registration and the cfp online asap :-)
Le 23 mai 2011, 6:35 PM, "Florian Effenberger" <
email@example.com> a écrit :
Marc Paré wrote on 2011-05-12 15.18:
In the meantime, I have also reserved the "http://www.libOCon.com" >
domain which now points te...
thanks a lot for your kind offer and support, that is really appreciated!
Sorry for stepping in so late with this.
My first idea when we announced the conference of course was "LibOCon", as
this was the natural abbreviation. :) So, from my side, I would be happy to
use this and the domain names.
Charles, as the organizer of this years conference, what do you think? If we
were to use libocon.org, the right time would be now, otherwise we'd better
stick with conference.libreoffice.org
Florian Effenberger <firstname.lastname@example.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
email@example.comPosting guidelines + more: ...
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
- RE : Re: [libreoffice-marketing] LibOCon.com domain -- proposal · Charles-H. Schulz
Impressum (Legal Info)
: 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