I was looking at the SponsorsQueue wiki page[1] the other day and
noticed that it doesn't mention the Triaged status at all.  I was going
to make the attached updates to the page but saw a warning at the top of
the page regarding making any changes to it.  

The changes basically indicate that people requesting sponsorship should
use "Triaged" but if unable use "Confirmed", and that sponsors should
always used "Triaged" instead of "Confirmed".  These changes are
appropriate since "Triaged" is considered further along in the bug life
cycle than "Confirmed".

What is a better place for the changes?

[1] https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue

Thanks,
-- 
Brian Murray                                                 @ubuntu.com
--- SponsorsQueue.orig	2009-08-11 11:52:23.000000000 -0700
+++ SponsorsQueue	2009-08-11 12:00:39.000000000 -0700
@@ -154,7 +154,7 @@ Before '''subscribing''' ubuntu-universe
  5 The Status and Assignment are correct
   * The Status should be "New" for sync requests
   * The Status should be "Incomplete" for freeze exceptions
-  * The Status should be "Confirmed" for bugs that represent a new candidate revision (e.g. bugfix uploads, merges.) In other words, use Status "Confirmed" when you have uploaded a debdiff that requires attention from a sponsor.
+  * The Status should be "Triaged" for bugs that represent a new candidate revision (e.g. bugfix uploads, merges.) In other words, use Status "Triaged" when you have uploaded a debdiff that requires attention from a sponsor.  However, if you are not a member of [[ UbuntuBugControl | Ubuntu Bug Control ]] the "Confirmed" status can also be used.
   * The Assignment should be "Nobody"
 
  6 The sponsors will use the status and assignment fields in their communications with you and other groups
@@ -162,7 +162,7 @@ Before '''subscribing''' ubuntu-universe
 
 == Note for Sponsors ==
 
-Once you have selected a bug, please use the following guidelines for disposition.  When selecting bugs, please limit yourself to "New", "Incomplete" and "Confirmed" bugs.
+Once you have selected a bug, please use the following guidelines for disposition.  When selecting bugs, please limit yourself to "New", "Incomplete", "Confirmed" and "Triaged" bugs.
 
 === All bugs ===
 
@@ -174,7 +174,7 @@ Once you have selected a bug, please use
 
   * If unset, set the importance. (default: "Wishlist")
   * If not present, add the "patch" tag
-  * Assign "Nobody" and set Status to "Confirmed"
+  * Assign "Nobody" and set Status to "Triaged"
   * Add a comment including the following:
    * That ubuntu-universe-sponsors has been unsubscribed.
    * That the package is in main
@@ -187,7 +187,7 @@ Once you have selected a bug, please use
   * If not present, add the "sync" tag.
 
   * If the sync is acceptable
-   * Set the Status to "Confirmed"
+   * Set the Status to "Triaged"
    * Assign to "Nobody"
    * Add a comment "sync request ACK'd"
    * Subscribe ubuntu-archive
@@ -211,7 +211,7 @@ Once you have selected a bug, please use
     * Ask in #ubuntu-motu for a second opinion
     * In the absence of a second opinion:
      * Add the motu-sru-verification tag
-     * unassign yourself, and set status to "Confirmed"
+     * unassign yourself, and set status to "Triaged"
 
   * If additional changes to the source are planned (soon)
    * Add comment that you are working on additional changes
@@ -228,7 +228,7 @@ Once you have selected a bug, please use
 === Bugs without debdiffs ===
 
   * If there is a patch, and no patch tag, add the patch tag
-  * Assign "Nobody" and Set status "Confirmed"
+  * Assign "Nobody" and Set status "Triaged"
   * (optional) Set the Importance
   * Add a comment including the following:
    * That ubuntu-universe-sponsors has been unsubscribed

Attachment: signature.asc
Description: Digital signature

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Reply via email to