Code

Ticket #6320: 6320.diff

File 6320.diff, 2.9 KB (added by telenieko, 6 years ago)

The third role

Line 
1diff --git a/docs/contributing.txt b/docs/contributing.txt
2index 37c9196..6ce3d38 100644
3--- a/docs/contributing.txt
4+++ b/docs/contributing.txt
5@@ -220,7 +220,8 @@ don't meet all the requirements of a `good patch`_.
6 
7 One way to help out is to *triage* bugs that have been reported by other
8 users. A couple of dedicated volunteers work on this regularly, but more help
9-is always appreciated.
10+is always appreciated but, please, read this whole section before starting to
11+*triage* bugs.
12 
13 Most of the workflow is based around the concept of a ticket's "triage stage".
14 This stage describes where in its lifetime a given ticket is at any time.
15@@ -234,13 +235,28 @@ Since a picture is worth a thousand words, let's start there:
16    :width: 590
17    :alt: Django's ticket workflow
18 
19-We've got two roles here:
20+We've got three roles here:
21 
22     * Core developers: people with commit access who make the decisions and
23       write the bulk of the code.
24 
25-    * Ticket triagers: community members who keep track of tickets, making
26-      sure the tickets are always categorized correctly.
27+    * Ticket triagers: community members with proven criteria who keep track
28+      of tickets, making sure the tickets are always categorized correctly.
29+     
30+    * Community triagers: community members that, while not being officially
31+      recognised as triagers, help out categorizing tickets, commenting on them
32+      and, in general, doing almost the same like a "Ticket triager" with some
33+      exceptions:
34+
35+        - Do not close bugs as "wontfix", see the definition of "wontfix" below,
36+          but in general, it's a decission in hands of *core developers*.
37+
38+        - Do not promote tickets to "Ready for Checkin" unless you feel confident
39+          about the patch provided and you are not related to the ticket itself
40+          (You know, it's not good to judge oneself's work).
41+
42+        - Only close tickets as "invalid" if those are clear cases like help requests
43+          which sould be placed to ``django-users`` (tell so when closing the ticket).
44 
45 Second, note the five triage stages:
46 
47@@ -295,10 +311,10 @@ A ticket can be resolved in a number of ways:
48         Used if the ticket is found to be incorrect or a user error.
49 
50     "wontfix"
51-        Used when a core developer decides that this request is not
52-        appropriate for consideration in Django. This is usually chosen after
53-        discussion in the ``django-developers`` mailing list, and you should
54-        feel free to join in when it's something you care about.
55+        Used when a *core developer* or a *ticket triager* decides that this
56+        request is not appropriate for consideration in Django. This is usually
57+        chosen after discussion in the ``django-developers`` mailing list, and
58+        you should feel free to join in when it's something you care about.
59 
60     "duplicate"
61         Used when another ticket covers the same issue. By closing duplicate