#8267 NORM Not Tri: trac wishlist : 2 items

[Zarro Boogs per Child]

#8267: trac wishlist : 2 items
--------------------------+-------------------------------------------------
 Reporter:  sj            |         Owner:               
     Type:  enhancement   |        Status:  new          
 Priority:  normal        |     Milestone:  Not Triaged  
Component:  not assigned  |       Version:  not specified
 Keywords:                |   Next_action:  design       
 Verified:  0             |     Blockedby:               
 Blocking:                |  
--------------------------+-------------------------------------------------
 I recently filed a blocker that was by default assigned to coderanger (it
 was a trac bug, like this one :).  which made me think of two things:
   a) we should have a bug priority for bugs that aren't just blockers,
 they should be resolved by anyone who can resolve them, as soon as
 buildings are no longer on fire
   b) high priority bugs (perhaps just these urgent-blockers) should be
 assigned to people who are very likely to be using trac and see the
 assignment, rather than by component.

 For b, perhaps there could be a subset of trac users to whom blockers
 could be applied, every component would be required to have both an owner
 and a blocker-owner (the latter might be someone who is only processing
 the urgent bugs, for a component that is usually long-term opportunity
 bugs).  Or for a softer method, there could be a special flag/view for
 blocking bugs that aren't owned by anyone on that subset/whitelist of
 active trac users.

-- 
Ticket URL: <http://dev.laptop.org/ticket/8267>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system