Changes between Version 2 and Version 3 of SprintIdeas

Timestamp:

Sep 13, 2007, 2:28:04 PM (17 years ago)

Author:

Adrian Holovaty

Comment:

Added some links

SprintIdeas

@@ -17 +17 @@
 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.
 
- * Search for tickets in that '''component''' in Trac (one of the search filters is on the component type).
+ * [http://code.djangoproject.com/query Search for tickets] in that '''component''' in Trac (one of the search filters is on the component type).
  * Read through the ticket titles until you find something interesting and try to replicate the bug.
  * 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.
- * 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.
- * Write a patch, whether that is code or documentation to fix the problem.
+ * 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.
+ * [http://www.djangoproject.com/documentation/contributing/#patch-style Write a patch], whether that is code or documentation to fix the problem.
  * Attach the patch to the ticket.
 
 You 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.
 
-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.
+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 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.
 
 == Areas requiring caution ==