Django sprints

Basic sprint information

  • IRC Channel is #django-sprint on freenode.
  • Please assign tickets to yourself if you work on them and add the sprint keyword to the ticket. If you don't know the keyword, ask the organisers. Check that your patch meets the patch review checklist guidelines before sending a pull request.

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. (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.

For more information, view Brett Cannon's introductory talk from PyCon, or read Eric Holscher's blog post.

If you've never contributed to Django before, a sprint is the perfect chance for you to chip in.

Hosting

If you'd like to host a sprint, see SprintHostingHowto.

Upcoming development sprints

Latest development sprints

See PastSprints

Preparing for the sprint

Here are a few easy things you can do ahead of time to make sure your time is spent effectively:

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.

Attendees

If you plan to attending a sprint in person, please RSVP; each individual sprint page linked above will give you instructions about how to do so.

Last modified 8 years ago Last modified on Jul 4, 2016, 3:43:15 AM
Note: See TracWiki for help on using the wiki.
Back to Top