Russell Keith-Magee wrote: > On 12/6/06, Lakin Wecker <[EMAIL PROTECTED]> wrote: >> I am also interested in helping with this situation. I've run into quite a >> few patches that are reportedly working for some people. How do we help >> get these triaged? >
> A well triaged patch has the following characteristics: > > - A clear, consise description of the problem > > - A clear, concise set of conditions and instructions for consistently > replicating the problem > > - A brief discussion of the merits of any alternatives for fixing the problem > > - A patch that meets Django's coding guidelines > > - If the patch is non-trivial [1], evidence that there has been > discussion on django-developers on the alternatives. > > - A regression test to prevent the problem in the future This is a very useful guideline. Maybe it should be incorporated into the doc on contributing[0]? > So - if you want to help, jump right in. Pick a problem and triage it. How do we avoid duplicating work? I'm not sure if it is necessary, but it could be useful to leave a message on a ticket when people start working on it. [0] http://www.djangoproject.com/documentation/contributing/ -- Matias Hermanrud Fjeld --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
