Code

Changes between Version 21 and Version 22 of SprintIdeas


Ignore:
Timestamp:
09/13/07 20:28:25 (7 years ago)
Author:
adrian
Comment:

Small edits

Legend:

Unmodified
Added
Removed
Modified
  • SprintIdeas

    v21 v22  
    1414'''Work on whatever you like.''' 
    1515 
    16 If you want some suggestions, there are some at the [http://code.djangoproject.com/wiki/SprintIdeas#Suggestions bottom of this page] 
     16Our 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.) 
    1717 
    18 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.) 
     18== What to work on? The concrete answer == 
     19 
     20See the [http://code.djangoproject.com/wiki/SprintIdeas#Suggestions suggestions at the bottom of this page]. 
    1921 
    2022== What to work on? The longer answer == 
     
    5557== Things for people not confident squishing bugs == 
    5658 
    57 If you're not confident fixing bugs in the core code then there are still other ways to contribute. 
    58  * Triage the [http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&order=priority&stage=Unreviewed unreviewed tickets] - try to confirm them, or handle them according to the [http://www.djangoproject.com/documentation/contributing/#ticket-triage triage guidelines] 
    59  * Confirm existing bugs or work out how to repeat them 
    60  * Look for tickets in the unreviewed state and see if you can repeat the problem 
    61  * If the explanation of the bug isn't clear, work out what the reporter is talking about and add that in a comment on the original ticket 
     59If you're not confident fixing bugs in the core code, there are still other ways to contribute: 
     60 
     61 * Triage the [http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&order=priority&stage=Unreviewed unreviewed tickets] -- try to confirm them, or handle them according to the [http://www.djangoproject.com/documentation/contributing/#ticket-triage triage guidelines]. 
     62 * Confirm existing bugs or work out how to repeat them. 
     63 * Look for tickets in the unreviewed state and see if you can repeat the problem. 
     64 * If the explanation of the bug isn't clear, work out what the reporter is talking about and add that in a comment on the original ticket. 
    6265 * Look for tickets needing documentation or needing improved documentation and try to complete them. 
    6366