Changes between Version 4 and Version 5 of SprintIdeas


Ignore:
Timestamp:
09/13/2007 02:44:46 PM (8 years ago)
Author:
adrian
Comment:

Some more edits

Legend:

Unmodified
Added
Removed
Modified
  • SprintIdeas

    v4 v5  
    99Our 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.)
    1010
    11 == The long answer ==
     11== The longer answer ==
    1212
    1313If you're in doubt about what to work on, consider these pieces of advice:
     
    1515 * '''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.
    1616
    17 == "Big" items ==
     17 * '''Choose noncontroversial tickets.''' Some issues are intrinsically controversial, such as the question of how (or whether) to implement auto-escaping in templates. For the sake of your own sanity, avoid these tickets during the sprint.
    1818
    19 If you are going to work on a really big item, either individually or as a group, remember to respect normal practices. Post a summary of any big discussions you have to the [http://groups.google.com/group/django-developers/about django-developers] mailing list.
     19 * '''Zero in a particular component you're familiar/comfortable with.''' It's overwhelming to browse the [http://code.djangoproject.com/query full list of open tickets], so do yourself a favor and narrow it down by component. (Do this by selecting "Add filter" on the right side of the page.) Example components are "Documentation" or "RSS framework." The nice thing about this approach is that, once you've fixed one or two tickets, you'll get on a roll and will have learned enough about that particular component that subsequent tickets for the same component will be easier to fix.
    2020
    21 Remember that not everybody is going to be online all the time and those that are may well be busy on other things. So large changes or things requiring community input will have to go through the usual, archived channels. That being said, an online or in-person discussion can get a lot further quickly and then you can post a more comprehensive plan and summary than normal. So there are advantages to doing some design work in a sprint setting.
     21== How to handle "big" tickets ==
     22
     23If you're going to work on a really big item, either individually or as a group, remember to respect normal practices. Post a summary of any big discussions you have to the [http://groups.google.com/group/django-developers/about django-developers] mailing list, and leave a comment on the ticket with a link to the discussion.
     24
     25Remember that not everybody is going to be online all the time, and those that are may well be busy on other things. Large changes or things requiring community input will have to go through the usual, archived channels. That being said, an online or in-person discussion can get a lot further quickly, and then you can post a more comprehensive plan and summary than normal. So there are advantages to doing some design work in a sprint setting.
    2226
    2327== Working on smaller items ==
    2428
    25 The biggest contribution everybody can make during a sprint is to help confirm bug reports, write patches, review proposed solutions and help get the tickets closed.
     29The biggest contribution anybody can make during a sprint is to help confirm bug reports, write patches, review proposed solutions and help get the tickets closed.
    2630
    27 Pick an area you are interested in or wish to learn more about. The general procedure is choose a ticket, replicate the problem, write a test, write a fix, go back to start.
     31Pick an area you're interested in or want to learn more about. The general procedure is choose a ticket, replicate the problem, write a test, write a fix, go back to start.
    2832
    2933 * [http://code.djangoproject.com/query Search for tickets] in that '''component''' in Trac (one of the search filters is on the component type).
Back to Top