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