Ok. Thanks
Anubhav
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to dja
As far as I know, we have no plans to request further details from any of
our applications.
On Thursday, March 27, 2014 5:46:55 AM UTC-4, anubhav joshi wrote:
>
> I read on google melange:
> "mentoring organizations may request further proposal detail from the
> student applicant."
>
> My tests
I read on google melange:
"mentoring organizations may request further proposal detail from the
student applicant."
My tests are about to start so I want to know if and when should I be
expecting this.
Regards,
Anubhav
--
You received this message because you are subscribed to the Google Grou
On Wed, Mar 12, 2014 at 9:58 PM, anubhav joshi wrote:
> Well another thing I think I realize now is that I think is there seems to
> be problem of absence of common theme.
> To this I would say that if one would look closely at the issues covered
> up in the proposal are those which do report of b
Well another thing I think I realize now is that I think is there seems to
be problem of absence of common theme.
To this I would say that if one would look closely at the issues covered up
in the proposal are those which do report of bad error reporting not just
simple bugs. The issues do repor
Having replied to the potential questions above, I would like to summarize
here once again:
1.) I have a very clear idea of what area of code I will be dealing with.
2.) I have been in conversation with community members on IRC, and have
taken their say in fixing the issues mentioned in the prop
On Wednesday, March 12, 2014 5:57:23 PM UTC+5:30, Russell Keith-Magee wrote:
>
> Hi Anubhav,
>
> I've taken a look at your proposal, and I'm of two minds.
>
> On the one hand, you've identified a bunch of reasonably uncontroversial
> tickets - issues where there is a clear problem, a solution th
Hi Anubhav,
I've taken a look at your proposal, and I'm of two minds.
On the one hand, you've identified a bunch of reasonably uncontroversial
tickets - issues where there is a clear problem, a solution that seems
obvious, and in most cases indications of support from the core team. Your
proposal
I do keep updating gist upon getting feedback/reviews on IRC as well.
Please keep a track.
https://gist.github.com/coder9042/c505dfba9514a6e52fdc
Regards,
Anubhav Joshi
IIT Patna
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscri
Done the required.
https://gist.github.com/coder9042/c505dfba9514a6e52fdc
Regards,
Anubhav Joshi
IIT Patna
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Anubhav,
It'll be easier to review if you can include ticket numbers with each item
in the 2.X sections. e.g. "Unpickling Models and QuerySet from incompatible
version. (#X)" Ideally, the ticket number would be linked to Trac. Then
I would repeat these summaries & ticket numbers in each
Just realized that the proposal name is : Improving error reporting and
fixing up related issues.
Missed 'reporting' in the thread topic.
Anubhav Joshi
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and st
OK, will do.
Anubhav Joshi
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send emai
Yes, people can look elsewhere for the tickets, but it'd probably have more
*impact* if the tickets were referenced directly in the proposal. That way,
someone can dive into the deeper discussion for a particular bug (by
reading the comments on the ticket). The idea is that you don't want your
Please refer to the thread :
https://groups.google.com/forum/#!topic/django-developers/PDY8EEYaHao for
tickets...
Actually, all of a sudden there has been some problem in my laptop since
this morning and I can't open my hard disk currently. So, I request you all
to please view the proposal and
Just a brief comment. Perhaps it'd be useful to link to the appropriate
trac tickets in your proposal.
Regards,
Josh
On Saturday, 8 March 2014 15:59:27 UTC+11, anubhav joshi wrote:
>
> Hi all,
>My previous thread:
> https://groups.google.com/forum/#!topic/django-developers/PDY8EEYaHao
Hi all,
My previous thread:
https://groups.google.com/forum/#!topic/django-developers/PDY8EEYaHao ,
where I was told by Tim Graham to make all analysis and discussion on
tickets itself and then present here.
I did what I was told, I discussed issues and strategies on Trac and IRC
both.
17 matches
Mail list logo
