| 5 | | If you are in doubt about what to work on, choose to fix existing bugs, rather than add enhancements. Bugs are cases where we know something is not working correctly or as documented. Enhancements require a bit more of a judgement call from the maintainers about whether to include the feature and one big goal of the sprint is to try and ''reduce'' the number of open tickets by getting patches committed and tickets closed. |
| | 5 | == The short answer == |
| | 6 | |
| | 7 | '''Work on whatever you like.''' |
| | 8 | |
| | 9 | Our development process during the sprint will fundamentally be no different from standard Django development -- that is, contributors scratch their own itches, solve the problems they want to solve, and generally do what they want to do. The difference in the sprint, of course, is that a lot of people are going to be in more-or-less real-time contact, which makes it easier for ''more'' contributions to happen ''faster''. (Some sprinters will be in the same physical location and the IRC channel will be available for more rapid feedback.) |
| | 10 | |
| | 11 | == The long answer == |
| | 12 | |
| | 13 | If you're in doubt about what to work on, consider these pieces of advice: |
| | 14 | |
| | 15 | * '''Fix existing bugs, rather than adding enhancements.''' Bugs are cases where we know something is not working correctly or as documented. Enhancements require a bit more of a judgment call from the maintainers about whether to include the feature, and one big goal of the sprint is to try and ''reduce'' the number of open tickets by getting patches committed and tickets closed. |