I wrote that BooleanFields without defaults patch! I'm glad that the warning has been seen by at least one person!
The ./manage.py validate command has been replaced with ./manage.py check in Django 1.7. The new system checks framework [1] is extensible, so third party apps will be able to add their own checks.
Hello, I'm interested in contributing to django, could you please give me a few pointers ? The django ticket list is daunting for a newcomer, that I don't know what to start with. My email's in the profile, and I'll be checking this comment as well. Thanks.
It took me quite a while to find tickets and patches that I could work on. I started with a couple of really trivial documentation fixes, and am building from there. I agree that the ticket list can be a bit daunting, so don't give up!
Searching the tickets that require documentation [1] or unit tests [2] can be a good place to start. It's a sign that a bug or new feature has been accepted, and that the patch can be accepted with some improvement. If a ticket is assigned to somebody, but hasn't been worked on for a few weeks, then don't be afraid to pick it up and improve it.
If there are any sprints happening near you, then go along. Daniele Procida runs a workshop Don't Be Afraid to Commit, which covers a lot of the basics you need to write your first Django patch (git/sphinx/...). The workshop is online [3].
There's a low traffic Django Core Mentorship mailing list [4] that you could join, or #django-dev on IRC might be helpful.
The ./manage.py validate command has been replaced with ./manage.py check in Django 1.7. The new system checks framework [1] is extensible, so third party apps will be able to add their own checks.
[1]: https://docs.djangoproject.com/en/dev/ref/checks/