Hi Satinderpal -
Thanks for your effort! Unfortunately, I think you've still got a long
way to go.
Your proposal is fundamentally quite vague. You seem to understand
some of the problems with the current forms API, but I really can't
tell exactly what you plan to do about it. The actual meat of your
proposal ("Goal") is a scant two paragraphs that doesn't really go
into any detail about what you're proposing. There's something about
additional attributes, and then a vague notion about dynamic forms,
but that's it. You need to be a *lot* more specific and in depth.
There's been quite a bit of discussion around forms these last few
days -- see especially the posts the by Carl and Russ -- but you
haven't really addressed the concerns raised in those threads. Again,
you need to really demonstrate you understand what you're proposing to
do.
A previous summer of code forms project failed; what have you learned
from that, and what makes your proposal different?
Moving on to the timeline, you need to be more specific here, as well.
For example, you say you need to spend two weeks "adding the template
widgets". OK, so what about that project takes two weeks? What does
"adding widgets" mean? Which widgets? Is there an order to what you
plan to add? Some groundwork to lay first? Etc. You need more detail
here, too.
Then you go on to say that you plan to spend two months on
"miscellaneous work". I'm sorry, but we're not going to mentor a
project that sets aside two months for "miscellaneous".
One week is about *minimum* amount of granularity you should have
here; anything rougher shows you haven't thought through the steps
clearly enough.
You've also left testing and documentation until the end, which also
isn't OK. If you've spent any time around the Django project you
already know that testing and documentation are something we take
incredibly seriously. They have to be do at the same time as the code;
they're *not* an afterthought. You should writing tests and docs along
with -- or even before -- your code.
I hope this gives you some good ideas on how you might be able to
improve your proposal into something we could accept. As I've said
before, this is an area that really needs some work, so I would love
to see a GSoC project tackle it. But I can't accept a proposal on
faith; I need to see that it's something with a realistic chance of
success.
Good luck,
Jacob
On Thu, May 2, 2013 at 8:36 AM, Satinderpal Singh
<satinder.goray...@gmail.com> wrote:
> Given below is the link for my proposal for the GSoC 2013, please give
> me the feedback about the proposal.
> https://docs.google.com/document/d/1SirpfF0KXGq-GGU9iAhuEi1IbVOuXNzj8LKrLG1_1zQ/edit
>
> --
> Satinderpal Singh
> http://devplace.in/~satinder/wordpress/
> http://satindergoraya.blogspot.in/
> http://satindergoraya91.blogspot.in/
>
> --
> 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 django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
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 django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
