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


Hi Skyler,

On Tue, 2011-03-29 at 22:12 -0700, Skyler Hawthorne wrote:
On 03/29/2011 12:18 AM, Cedric Bosdonnat wrote:
Hi all,

this reminder is for both the students and the mentors: please apply now
on Google Melange.

http://www.google-melange.com/gsoc/org/show/google/gsoc2011/libreoffice

* Students applications can be filed from March 28th (yesterday) to
April 8th (less than 2 weeks).
* Mentors need to apply now too in order to be able to participate in
the applications selection process after that period.

Don't hesitate to tell me if you have any trouble to apply.

Hello, I will be applying to LibreOffice for GSoC. I haven't put 
together my proposal yet, because the wiki says that applicants need to 
fix a bug to be accepted. I'm still working on the "Print current page" 
Easy Hack, but I have midterms this week, so I haven't had much time to 
dedicate to that this week.

My question is this: Should I finish fixing my bug before making and 
submitting my proposal, or should I submit my proposal and just get my 
bug fixed ASAP?

You don't necessarily need to push the fix before filing the
application, but we will need it to review your application. This means
that you have up to April, 18th to provide the bug fix.

Regards,

-- 
Cédric Bosdonnat
LibreOffice hacker
http://documentfoundation.org
OOo Eclipse Integration developer
http://cedric.bosdonnat.free.fr


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.