Ticket #6320: 6320_remix.diff

File 6320_remix.diff, 2.8 KB (added by telenieko, 8 years ago)

New patch

  • docs/contributing.txt

    diff --git a/docs/contributing.txt b/docs/contributing.txt
    index 37c9196..1447c11 100644
    a b don't meet all the requirements of a `good patch`_. 
    220220
    221221One way to help out is to *triage* bugs that have been reported by other
    222222users. A couple of dedicated volunteers work on this regularly, but more help
    223 is always appreciated.
     223is always appreciated but, please, read this whole section before starting to
     224*triage* bugs.
    224225
    225226Most of the workflow is based around the concept of a ticket's "triage stage".
    226227This stage describes where in its lifetime a given ticket is at any time.
    We've got two roles here: 
    239240    * Core developers: people with commit access who make the decisions and
    240241      write the bulk of the code.
    241242
    242     * Ticket triagers: community members who keep track of tickets, making
    243       sure the tickets are always categorized correctly.
     243    * Ticket triagers: community members with proven criteria and expertice
     244      on the matter who keep track of tickets, making sure the tickets are
     245      always categorized correctly.
     246     
     247This does not mean you cannot triage tickets. Any help is always very welcome and Anybody
     248can help in this matter. In fact, the only difference between you and a triager is expertice.
     249While gainning this expertise, please, try to follow this tips:
     250
     251    * Do not close bugs as "wontfix", see the definition of "wontfix" below,
     252      but in general, it's a decission in hands of *core developers*.
     253
     254    * Do not promote tickets to "Ready for Checkin" unless you feel *very* confident
     255      about the patch provided and you are not related to the ticket itself
     256      (You know, it's not good to judge oneself's work).
     257
     258    * Only close tickets as "invalid" if those are clear cases like help requests
     259      which sould be placed to ``django-users`` (tell so when closing the ticket).
    244260
    245261Second, note the five triage stages:
    246262
    A ticket can be resolved in a number of ways: 
    295311        Used if the ticket is found to be incorrect or a user error.
    296312
    297313    "wontfix"
    298         Used when a core developer decides that this request is not
    299         appropriate for consideration in Django. This is usually chosen after
    300         discussion in the ``django-developers`` mailing list, and you should
    301         feel free to join in when it's something you care about.
     314        Used when a *core developer* or a *ticket triager* decides that this
     315        request is not appropriate for consideration in Django. This is usually
     316        chosen after discussion in the ``django-developers`` mailing list, and
     317        you should feel free to join in when it's something you care about.
    302318
    303319    "duplicate"
    304320        Used when another ticket covers the same issue. By closing duplicate
Back to Top