Two quick points:
Firstly -- the fact that you've given some biographical detail at the
bottom, and that this biographical detail says your a student,
suggests that this is a GSoC proposal? Is this the case? If so --
that's a pretty big detail to omit. Django-developers is a general
list for discussing the development of Django; if you're proposing a
GSoC project, you need say so.
Secondly -- This is a reason that this project is listed as a high
complexity project on the GSoC wiki page. It's deceptively difficult,
and there's *lots* of prior art. A proposal that starts with
introducing 3 new settings, and finishes with the phrase "create a
datamigration script" is essentially a non-starter for reasons that
are well documented historically.
If you're interested in this project, I *strongly* suggest that you
spend a couple of days familiarizing yourself with the historical
discussions about the idea. There was a lengthy discussion around last
year's GSoC; a student was proposing work on this project, but
ultimately backed out because of the complexities involved. At the
very least, it should give an indication of what will and won't be
accepted.
Yours,
Russ Magee %-)
On Wed, Mar 23, 2011 at 4:32 AM, Rohan Jain <rohanj...@gmail.com> wrote:
> These are some auth settings and models I propose to account for the
> generally
> raised questions for auth.User flexibility.Two quick points:
Firstly -- the fact that you've given some biographical detail at the
bottom, and that this biographical detail says your a student,
suggests that this is a GSoC proposal? Is this the case? If so --
that's a pretty big detail to omit. Django-developers is a general
list for discussing the development of Django; if you're proposing a
GSoC project, you need say so.
Understood - in which case, scratch my first comment.
However, my second point stands. This proposal doesn't reference any
of the prior discussion related to this topic, or address any of the
issues that those prior discussions have raised. In the case of
suggesting migrations, it specifically violates a design consideration
that has been repeatedly stated in the past.
I agree that this is definitely a pain point that many people have
with Django, and it is something that I'm hoping to look at in the 1.4
development cycle. If you want to help out, I suggest you familiarize
yourself with the historical discussion.
Yours,
Russ Magee %-)