Hi Jean,
Jean Weber wrote (02-07-13 10:30)
I've looked at the flyers, but what I want for this conference is
something with more specific information, to hand to people who
express an interest or ask questions I can't answer. So I'm looking
again at what I might be able to pull out of the website or wiki.
Things like: what language LO is coded in and and what tools are
commonly used. As well as licensing & whatever other info a hacker
might want to know up front.
OK, I understand that.
On the one hand: hackers often are faster in finding something on the
internet that you can tell'm. But that is of course not always true.
So indeed, basic info over language, licence and opportunities to join
(EasyHacks) are good to have at hand.
Maybe it's enough to just add:
" C++ (for most parts), cgit repository, GNU LGPL3 licence, copyleft "
and the QR code maybe can better link to this page
https://wiki.documentfoundation.org/Development/GetInvolved
Best,
--
- Cor Nouws
- http://nl.libreoffice.org
- The Document Foundation Membership Committee Member
--
To unsubscribe e-mail to: marketing+unsubscribe@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
- Re: [libreoffice-marketing] Re: Developer-specific brochure (continued)
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.