Date: prev next · Thread: first prev next last


Dear Community,

next weekend, from September 2nd to 4th, the first LibreOffice Hackfest will take place in the city of Munich, Germany.

The Hackfest is the gathering of LibreOffice developers from all around the world, where experienced coders and interested developers meet and work on the code, fix bugs and implement new features. Plus, it is a great chance to see many faces from the community in the wonderful setting of Bavaria’s capital city.

Participation is free of charge, and the best is, we still have free seats available!

If you want to contribute code to LibreOffice, or get in touch with members of our community, the LibreOffice Hackfest is the place to be! And for those not so experienced in developing, we will host a special session on hacking pasta. ;-)

More details on the planned agenda and on the venues are available in our wiki at

http://wiki.documentfoundation.org/Hackfest2011

Looking forward to hacking with you in Munich!

Florian
on behalf of the Hackfest organizers

--
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 announce+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
List archive: http://listarchives.documentfoundation.org/www/announce/

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.