Thanks for all the discussion!
You convinced me that focusing on particular project and being able to
detail it - not looking for the best one in meaning of usefulness is the
key here. Also I did not take into account variable number of slots.
However I'm going to review *all* projects again an
On Thu, Apr 18, 2013 at 6:42 PM, Russell Keith-Magee
wrote:
> So - the secret to getting into the GSoC isn't the project title you pick -
> it's the quality of your proposal.
This. A thousand times this.
I think there's a perception among people applying to GSOC that we're
judging the project. T
On Fri, Apr 19, 2013 at 3:52 AM, Alex Ogier wrote:
> I wouldn't claim to speak for Django GSoC mentors and what they will
> accept, but I can say that the "Improve Django's code/error handling"
> projects have been perennial on Django's Recommended Project list for a
> while now, I think without
I wouldn't claim to speak for Django GSoC mentors and what they will
accept, but I can say that the "Improve Django's code/error handling"
projects have been perennial on Django's Recommended Project list for a
while now, I think without any successful proposals (though "Improve
Django's security"
And how would you rate the chances that these projects will be selected for
GSoC? Or which of all proposed projects have the most priority to you? I'd
be very happy to join Django community and have chance to improving code
quality (not only adding new features) would also be great.
On Tuesday,
Yes - I was referring to error reporting. Although the same would be true
for 'best practices'.
Yours,
Russ Magee %-)
On Mon, Apr 15, 2013 at 3:22 PM, Damian Skrodzki wrote:
> Thanks for the answer.
>
> Just to be sure. As "Take the first project" you mean "2. Improved error
> reporting", correc
Thanks for the answer.
Just to be sure. As "Take the first project" you mean "2. Improved error
reporting", correct? I wrote the whole post in reversed order which could
confuse you.
On Monday, April 15, 2013 2:18:56 AM UTC+2, Russell Keith-Magee wrote:
>
>
>
> On Mon, Apr 15, 2013 at 7:51 AM,
On Mon, Apr 15, 2013 at 7:51 AM, Damian Skrodzki wrote:
> Hi,
>
> After looking through proposed ideas for the current GSoC i found 2 issues
> related close to the code quality which I'm interested in. These are:
>
>
>1. Best practices Updates
>2. Improved error reporting
>
> Both tasks ar
Hi,
After looking through proposed ideas for the current GSoC i found 2 issues
related close to the code quality which I'm interested in. These are:
1. Best practices Updates
2. Improved error reporting
Both tasks are a different but they are very closely related just to code
quality
