Changes between Version 2 and Version 3 of SprintIdeas


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

Added some links

Legend:

Unmodified
Added
Removed
Modified
  • SprintIdeas

    v2 v3  
    1717Pick 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.
    1818
    19  * Search for tickets in that '''component''' in Trac (one of the search filters is on the component type).
     19 * [http://code.djangoproject.com/query Search for tickets] in that '''component''' in Trac (one of the search filters is on the component type).
    2020 * Read through the ticket titles until you find something interesting and try to replicate the bug.
    2121 * Once you've found a ticket that interests you, [http://www.djangoproject.com/documentation/contributing/#claiming-tickets claim it], so that somebody else doesn't accidentally duplicate the work.
    22  * If possible, write a test to duplicate the problem. Django's tests are in the {{{tests/}}} directory. Copy existing tests as a start. If possible, look for an appropriate file to add your new test to, rather than starting a new file. But if you are working on a totally untested area, start a new file.
    23  * Write a patch, whether that is code or documentation to fix the problem.
     22 * If possible, write a test to duplicate the problem. Django's tests are in the {{{tests/}}} directory, and we have [http://www.djangoproject.com/documentation/contributing/#unit-tests some documentation about them]. Copy existing tests as a start. If possible, look for an appropriate file to add your new test to, rather than starting a new file. But if you are working on a totally untested area, start a new file.
     23 * [http://www.djangoproject.com/documentation/contributing/#patch-style Write a patch], whether that is code or documentation to fix the problem.
    2424 * Attach the patch to the ticket.
    2525
    2626You might want to search for tickets that have the ''patch needs improvement'' flag set and try to improve the patch (there will be something in the comments suggesting what improvement is needed). Or look for tickets with ''needs tests'' or ''needs documentation'' and try to fill in those gaps.
    2727
    28 Don't worry if it takes you longer than other people to write fixes initially. Some areas are genuinely harder than others. Some problems are disguised versions of something much bgiger, so it might take a couple of attempts to get something that satisfies the maintainers. Not to worry; any serious patch is better than no patch because it gives us something to start from and incrementally improve.
     28Don't worry if it takes you longer than other people to write fixes initially. Some areas are genuinely harder than others. Some problems are disguised versions of something much bigger, so it might take a couple of attempts to get something that satisfies the maintainers. Not to worry; any serious patch is better than no patch because it gives us something to start from and incrementally improve.
    2929
    3030== Areas requiring caution ==
Back to Top