The deadline for student applications is 19:00 UTC on Friday 6th April:
http://www.google-melange.com/gsoc/events/google/gsoc2012
That's just over 36 hours away as I write this.
The deadline is sharply enforced by the melange software, and you
won't get an extension, so don't leave it until the last few seconds, as
you might have an unexpected internet outage.
There's also no need to leave it so late - if you've submitted before
then, you can update your application up to the deadline. Once the
deadline has passed, you can no longer update the proposal, but you can
add comments.
We'll try to comment on proposals received before the deadline to give
you a chance to improve them in response to feedback, but if you leave
it too late, we won't have time to. At least 24 hours is useful; 12 is
probably the realistic minimum, at least for me.
We get an email when a proposal is submitted or updated, so there's
no need to ping us on the list or by IRC too.
There's also some general guidance at:
http://trac.xapian.org/wiki/GSoC2012
So have a read through that first, and you'll avoid some of the common
mistakes in your initial application. I've already seen a few timelines
which look rather like the example of how *NOT* to do it.
Cheers,
Olly
Hi I changed my schedule in the proposal with more details. Could please see it? Yours sincerely Riadh 2012/4/5 Olly Betts <olly at survex.com>> The deadline for student applications is 19:00 UTC on Friday 6th April: > > http://www.google-melange.com/gsoc/events/google/gsoc2012 > > That's just over 36 hours away as I write this. > > The deadline is sharply enforced by the melange software, and you > won't get an extension, so don't leave it until the last few seconds, as > you might have an unexpected internet outage. > > There's also no need to leave it so late - if you've submitted before > then, you can update your application up to the deadline. Once the > deadline has passed, you can no longer update the proposal, but you can > add comments. > > We'll try to comment on proposals received before the deadline to give > you a chance to improve them in response to feedback, but if you leave > it too late, we won't have time to. At least 24 hours is useful; 12 is > probably the realistic minimum, at least for me. > > We get an email when a proposal is submitted or updated, so there's > no need to ping us on the list or by IRC too. > > There's also some general guidance at: > > http://trac.xapian.org/wiki/GSoC2012 > > So have a read through that first, and you'll avoid some of the common > mistakes in your initial application. I've already seen a few timelines > which look rather like the example of how *NOT* to do it. > > Cheers, > Olly > > _______________________________________________ > Xapian-devel mailing list > Xapian-devel at lists.xapian.org > http://lists.xapian.org/mailman/listinfo/xapian-devel >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20120405/1defa2e7/attachment-0001.html>
On Thu, Apr 05, 2012 at 09:53:21PM +0200, riadh chtara wrote:> I changed my schedule in the proposal with more details. > Could please see it?As I said in the message you replied to:> > We get an email when a proposal is submitted or updated, so there's > > no need to ping us on the list or by IRC too.I'll be looking over all the updates that have come in so far in the next few hours. Cheers, Olly
On Thu, Apr 05, 2012 at 07:36:44AM +0100, Olly Betts wrote:> The deadline for student applications is 19:00 UTC on Friday 6th April:The deadline has now passed - here are some statistics about the proposals we received: http://survex.com/~olly/blog/xapian/xapian-gsoc-applications-for-2012.html We are likely to be asking questions about some of the proposals by adding comments, so please keep an eye out for email notifications. These sometimes end up in spam filters (even on gmail, ironically). You can't change the text of your proposal, but you can add comments to it if you want to provide additional information. I would encourage applicants to continue to investigate - check out the code and get it to build if you haven't already, and find the areas you'd be working on. If you can show us a patch you've written for Xapian, that helps us feel confident you'll be able to get to grips with the project, and make it more likely we'll select you. The patch could be a first step towards your project, or a prototype of some sort, or a fix for a bug, or a new little feature. You can find some relevant links here: http://trac.xapian.org/wiki/GSoC2012#Checkingoutandbuildingthecode Cheers, Olly