Version 11 (modified by 16 years ago) ( diff ) | ,
---|
Django development sprints
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 fix bugs, add new features and improve documentation.
Anybody, anywhere around the world, can participate and contribute. (See the "How to contribute" section below for details.) 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.
If you've never contributed to Django before, a sprint is the perfect chance for you to chip in.
Upcoming sprints
- July 10 - July 12 at EuroPython 2008, focusing on newforms-admin.
- July 18 in Sausalito, CA, focusing on Django 1.0 alpha.
- August 1, in Washington, DC, focusing on Django 1.0 beta.
- August 8, Lawrence, KS, focusing on Django 1.0 beta 2.
- August 15, Austin, TX, focusing on Django 1.0 rc.
- August 22, Portland, OR, focusing on Django 1.0 final.
How to contribute
It's easy: Pick something to work on and do it. All sorts of tasks are available, from hard-core hacking to improving documentation to fixing small bugs.
Volunteers looking to get an early start should take a look at the SprintIdeas page.
Preparing for the sprint
Here are a few easy things you can do ahead of time to make sure your time is spent effectively:
- Read our "Contributing to Django" document.
- Install the "trunk" version of Django (aka the Django development version).
- Create an account in our ticket system. This will allow you to claim tickets you're working on.
- Familiarize yourself with our ticket system and reports.
- Get an IRC client, so that you can join us in the channel #django-sprint on Freenode.
Attendees
If you plan to attending a sprint in person, please RSVP; each individual sprint page linked above wil give you instructions about how to do so.