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


Hi All,

I wanted to see if anyone would be willing to make a quick flyer for me to post on my campus - we have a strong and large CS department and I thought maybe we could get some new devs/QA/etc... people involved. Ultimately I was thinking that perhaps if we do enough and I can make some contacts in the CS department I can see if we can get the school to get independent study credits to develop for LibreOffice.

I was hoping to have the following:
1: All skill levels welcome - but maybe encourage "advanced students" a bit more 2: Real world experience on a large open source project (possibly "great on resumes!", maybe even mention ~20,000,000 lines, largest open source project out there (that would need verified))
3: Fun and encouraging teams
4: mentors available
5: International group


Any other fun things that would encourage people. There are several places where I can post - I'm going to use myself as a contact since I'm on campus often enough. Thanks all!


Best,
Joel

--
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


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.