| 3 | | On Friday, Sept. 14, 2007, we're going to have a sprint to try and reduce the open ticket count. See the [http://groups.google.com/group/django-developers/msg/c1b25ec884c35947 original announcement] to django-dev for some details. |
| 4 | | |
| 5 | | Developers around the world, both new and experienced, have already expressed much interest in participating, so there should be people available to help in most time zones. |
| 6 | | |
| 7 | | We'll use the IRC channel [irc://irc.freenode.net/django-sprint #django-sprint] on Freenode to coordinate activities. Watch this space for more information. |
| | 3 | We're holding a Django sprint on Friday, Sept. 14, 2007. This page provides information about what that means and how you can contribute. |
| 11 | | Basically, a Django sprint is an excuse for people to focus their undivided attention, for a set time frame, on improving Django. We'll communicate via the Internet, and the people in Chicago and Mountain View (if, indeed, that option pans out) will just have a focused place to gather, along with better communication and the other benefits of |
| 12 | | face-to-face interaction. |
| 13 | | |
| 14 | | Anybody can participate and contribute, and there's no obligation or expectation. If you've never contributed to Django before, this is the perfect chance for you to chip in. |
| | 7 | 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. |
| | 8 | |
| | 9 | 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. |
| | 10 | |
| | 11 | If you've never contributed to Django before, this is the perfect chance for you to chip in. |
| | 12 | |
| | 13 | == How to contribute == |
| | 14 | |
| | 15 | 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. |
| | 16 | |
| | 17 | Of course, with more than 100 people around the world signed up to help, good communication is essential. We're currently planning the best way to manage contributions. |
| | 18 | |
| | 19 | == Preparing for the sprint == |
| | 20 | |
| | 21 | Here are a few easy things you can do ahead of time to make sure your time is spent effectively: |
| | 22 | |
| | 23 | * Read our [http://www.djangoproject.com/documentation/contributing/ "Contributing to Django" document]. |
| | 24 | * [http://www.djangoproject.com/documentation/install/#installing-the-development-version Install the "trunk" version of Django] (aka the Django development version). |
| | 25 | * [http://www.djangoproject.com/accounts/register/ Create an account in our ticket system]. This will allow you to claim tickets you're working on. |
| | 26 | * Familiarize yourself with our [http://code.djangoproject.com/wiki/Reports ticket system and reports]. |
| | 27 | * Get an [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] client, so that you can join us in the channel [irc://irc.freenode.net/django-sprint #django-sprint] on Freenode. |