Hi all,
I'm sure you're all getting started on your plans for Document Freedom
Day (DFD), as it's just a month away (I'll have more on that later),
but I wanted to touch base briefly re Software Freedom Day (SFD).
Software Freedom Day is Sep 19th, and our Annual Conference starts on
Sep 23rd. For anyone travelling/preparing for the conference, these
two events are so close together that it might make it difficult to do
everything by yourself.
If you can, I suggest talking with your colleagues in Free Software in
your local area over the next few months (perhaps at the end of March,
after DFD events are done?) and working with them to get stuff prepare
ahead of time. In that fashion, you will hopefully be able to avoid a
mad scramble come September.
My method? I'm adding a reminder to my calendar for April 2nd. That
way I can ignore SFD until then.
Best,
--R
--
Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qubit@libreoffice.org
802-379-9482
--
To unsubscribe e-mail to: marketing+unsubscribe@us.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/us/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [us-marketing] Planning ahead: Software Freedom Day is right before the LibreOffice Annual Conference · Robinson Tryon
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.