Join developers in Japan (http://djangoproject.jp/weblog/2013/02/14/djangosprint_13_2/), San Francisco (http://www.meetup.com/The-San-Francisco-Django-Meetup-Group/events/103886122/), Utrecht Netherlands (http://www.meetup.com/dutch-django-assocation/events/98331492/), Kraków Poland (http://sprint.pykonik.org/), and Córdoba Agentina (http://lanyrd.com/2013/sprint-django/) in working on Django.
What is a sprint?
Basically, a Django sprint is an excuse for people to focus their undivided attention, for a set time frame, on improving Django. It's a focused, scheduled effort to test, fix bugs, add new features and improve documentation.
Anybody, anywhere around the world, can participate and contribute. Most contributors will be at their own homes/schools/workplaces, but a number of people will gather together in person for camaraderie, improved communication and the other benefits of face-to-face interaction.
For more information, view Brett Cannon's introductory talk (http://blip.tv/file/2082162) from PyCon, or read Eric Holscher's blog post (http://ericholscher.com/blog/2009/nov/16/you-should-stay-sprints/).
*If you've never contributed to Django before, a sprint is the perfect chance for you to chip in.*
Preparing for the sprint
Here are a few easy things you can do ahead of time to make sure your time is spent effectively:
Checkout the "trunk" version of Django (http://docs.djangoproject.com/en/dev/topics/install/#installing-the-development-version) (aka the Django development version). Create an account in our ticket system (http://www.djangoproject.com/accounts/register/). This will allow you to claim tickets you're working on. Get some advice (https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/) if you are a new contributor. Check out the Django development dashboard (https://dashboard.djangoproject.com/) for some useful info and stats. Read our "Contributing to Django" document (http://docs.djangoproject.com/en/dev/internals/contributing/). In particular, you might want to familiarize yourself with: Running the test suite (https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#running-the-unit-tests) (hint: the second command that includes setting PYTHONPATH is probably what you want) Triaging tickets (https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/) Claiming tickets in Trac (https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#claiming-tickets) (do this before working on anything) Familiarize yourself with our ticket system and reports (http://code.djangoproject.com/wiki/Reports). You can also see the Roadmap (http://code.djangoproject.com/roadmap) for a list of tickets by milestone. Get an IRC (http://en.wikipedia.org/wiki/Internet_Relay_Chat) client, so that you can join us in the channel #django-sprint on Freenode. You can find out more here (https://code.djangoproject.com/wiki/Sprints).