ubuntu-bugcontrol team mailing list archive

[Alberto Salvia Novella <es20490446e@xxxxxxxxx>]

Alan Pope:
> Assigning a bug to someone is one way to ensure we have someone
> working on a feature/bug.

---------------------------------------
 WORK ON DESK IS NOT WORK GETTING DONE
---------------------------------------

One person can work in one thing at a time: the rest of assigned work is 
just accumulated in a place that says "don't touch".

Look, it told this same thing to the Ubuntu One developers five months 
before the project was closed. Nearly every bug had an assignee from 
Canonical, but nobody really was able to work on most reports.

So this approach was making difficult to contributors to fix the 
software, as they were implicitly told not to do. As result the service 
was very flawed and gave very little monetary returns; because nobody 
was interested in, for example, their files to be wiped consistently or 
to be unable to access the service from the phone because the captcha 
being unreadable.

In fact I reported a step by step guide on how to make Ubuntu One to 
wipe files by accident, what had being happening to me for two years, 
and a bug this critical never got fixed; just it got very soon someone 
saying to be working on it.


---------------------------------------------
 THINKING FOR EVERYONE IS BLOWING YOUR MIND!
---------------------------------------------

Instead of assigning the work to the person who knows how to do it, 
better to make obvious how it can be done; so anyone can take it and you 
get as much work-force as possible. And let the specialist come in only 
if there's a very atypical irregularity.

Good management is not about assigning tasks, but about empowering 
people. So it is more related with training and building smart systems, 
than with administration.


That's all! Now I will have my gazpacho, Popey.