As Alberto said, and James and Jacob, I don't see enough value for
Django.  The key here is to define a project that results in a usable
code contribution by the end of the summer *for the project*.  Not for
Python3k, but for Django.  If you want to port Django to Python3k for
Python 3.0's benefit, where Django is simply an example code base,
well, submit that to the Python folks.

In addition, one of the side benefits is to get another contributor of
code to the project, right?  Is the student in question willing to
commit to working on a project that doesn't finish over the summer?
It's much easier to maintain a finished project of reasonable scope
than it is to continue working on a project of larger size once the
initial time commitment and incentive have lapsed.

I'm not arguing against porting Django, I think it's a good idea.  And
I like the sound of "Django3k".  :)  I would encourage the student to
commit to that project, just not under the aegis of SoC.  Do it
because it is useful, but do it on the side.  Do something else for
SoC, of a more reasonable scope and immediate payoff.

Regards,

---Peter

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
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