On 28/03/2012, at 7:29 AM, Alex Ogier wrote:

> On Tue, Mar 27, 2012 at 7:13 PM, Russell Keith-Magee 
> <[email protected]> wrote:
> There's also a very recent, relatively active thread discussing our options 
> with auth.User, which has a lot of overlap with this change. The wiki 
> discusses all the options, and makes specific mention of the need (and 
> possible migration approaches) for EmailField [1]. Given that these two 
> topics are closely related, I'd rather try and keep the discussions in one 
> place.
> 
> [1] 
> https://code.djangoproject.com/wiki/ContribAuthImprovements#Parallelconcerns
> 
> Yours,
> Russ Magee %-)
> 
> Perhaps the wrong thread to ask this, but is there a way to politely 
> encourage a BDFL decision on the matter sooner rather than later? I would 
> like to submit a GSoC application around implementing the fix, and the April 
> 6 deadline is coming up fast. I don't know the usual timeframe on 
> controversial decisions like this, so if it is unlikely that a BDFL will put 
> their foot down significantly before the deadline then that is also good to 
> know. I could then apply with a looser definition of the project contingent 
> on an eventual decision.

There was an improptu IRC discussion on django-dev last week that involved 
Jacob; unfortunately, it didn't go anywhere because he didn't especially like 
any of the options :-) 

In particular, the sticking point was whether User needed to be pluggable *at 
all* -- i..e, is  there a solution (admittedly with huge migration 
requirements) that would allow us to avoid the need for settings, decisions 
about User contracts, and so on. Unfortunately, I haven't yet had a chance to 
document this part of the discussion on the wiki. 

I should be speaking with Jacob tomorrow; I'll give him a poke then.

Yours,
Russ Magee %-)



-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
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