On Tue, Apr 6, 2010 at 1:48 PM, elayne <[email protected]> wrote:
> Thank you Alex!
>
> Just one question remains: you said you dont know how many students you'll
> be able to select until the application process finishes. How does it work?
>
> And one more thing: is there any critical part of Django that needs
> housekeeping?
>
>
> Thanks again.
>
> Elayne.
>
> On Tue, Apr 6, 2010 at 2:15 PM, Alex Gaynor <[email protected]> wrote:
>>
>> On Tue, Apr 6, 2010 at 11:58 AM, Elayne Morais <[email protected]>
>> wrote:
>> > Hello!
>> >
>> > This is my first time at GSoC and I'm sure that coding for Django will
>> > be very interesting. As I don't have experience with Django I thought
>> > the best project for me would be doing some housekeeping, which at the
>> > same time would give me a wider understanding of Django inside out.
>> > However, I read others students had the same idea, so here are my
>> > questions:
>> >
>> > - how many students Django will be able to select?
>>
>> We don't know until after the application process finishes.
>>
>> > - will be possible more than one student working at the same project?
>> > (like 2 students doing housekeeping on different parts of the code)
>>
>> Maybe.  Housekeeping would probably be ok to have multiple students on
>> (especially if they were in different parts of the codebase).
>>
>> > - do I need to be specific on what part of the code I'll be doing the
>> > housekeeping, or I can just say I'll be doing a general housekeeping?
>> > My concern is about the timeline: how will I be able to say I have
>> > finished coding?
>>
>> Yes, your proposal should specify what areas of DJango you'll be doing
>> housekeeping in, including references to specific tickets where
>> possible.
>>
>> As for how to know when you're done on this project it'd probably just
>> be until you've either run out of bugs (god help us ;)) or the time is
>> over, housekeeping is obviuosly a little open ended so you're project
>> would mostly be judged by how well you're doing at finding and closing
>> tickets.
>>
>> > - can I keep on coding for Django after GSoC if I want?
>> >
>>
>> Absolutely, one of the major goals of GSOC is to get students involved
>> in open source even beyond the end of their project.
>>
>> > Thank you all.
>> >
>> > Elayne.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Django developers" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to
>> > [email protected].
>> > For more options, visit this group at
>> > http://groups.google.com/group/django-developers?hl=en.
>> >
>> >
>>
>> Alex
>>
>> --
>> "I disapprove of what you say, but I will defend to the death your
>> right to say it." -- Voltaire
>> "The people's good is the highest law." -- Cicero
>> "Code can always be simpler than you think, but never as simple as you
>> want" -- Me
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

Google assigns us some number of slots.  From my memory: 2 years ago
is was 3/4 slots, last year we had 6.  We don't know how many we'll
get this year.

As for "critical" it's a bit hard to say, if anything were truly
violently broken we wouldn't be preparing for a release ;)  that being
said the admin and the ORM tend to have the most open bugs of any
component, mostly because they are 2 of the most prominent parts of
the framework.  THe best way to tell is to browse through trac's
ticket browser: http://code.djangoproject.com/query

Alex

-- 
"I disapprove of what you say, but I will defend to the death your
right to say it." -- Voltaire
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you
want" -- Me

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to