Re: GitHub migration planning

Paul, I meant no offense. I should have been more clear that I meant my question to explore what makes Trac ideal for Django. My apologies for any misunderstandings. Daniel: Indeed, BitBucket was considered. There's a thread about it from pretty recently here: http://python.6.n6.nabble.com/Moving

Re: GitHub migration planning

Luke, maybe I don't understand something about Trac, but some of the issues raised by you or those you quoted seem easily fixed. Consider: "- there isn't a notion of "component", so there's no way to ask "give me > the list of all contrib.auth tickets, so I can find the duplicate > quickly";" Wh

Re: auth.user refactor: the profile aproach

Hello! The page you linked, Tom, concludes with this line: "Discussion on django-developers suggests that complete consensus is unlikely; Currently awaiting BDFL mandate." Since we have the BDFL mandate, shouldn't we update the page?

Re: auth.User usernames

I and some folks in my area (Boston/Cambridge, MA) are thinking of ways to provide a solution to this problem that neither requires schema migration nor breaks backwards compatibility. David, if you (or anyone on this mailing list) is interested, email me and let's coordinate our efforts. Alternat

Re: start using less (and bootstrap!)

The point about admin's appeal to new people is important, but externalizing it and keeping new people from ever seeing it are very different. Consider: admin isn't even enabled by default. You have to follow the tutorial on how to enable it. If admin weren't included in Django proper, we could jus