Le dimanche 25 mai 2008 à 18:33 +1000, Sarah Hobbs a écrit : <snip> > There seems to be an attitude of "screw the developers, we are the > mighty bug squad, and can do what we like" here. The contrary can be true as well, but that's absolutely not the point here. ;-)
> But really, isn't the job of the bug squad to get bugs into a good state > of triage, so they can be dealt with by the developers? Does it not > make sense, therefore, to listen to what the developers want the bug > squad to do to the bugs, in a general sense, and then for the bug squad > to go away and deal with the specifics? > > I don't think the bug squad should have the right to say "we will make > the rules, everyone else must follow them", as, while there are many bug > squad people (yes, developers are still bug squad too), the bug squad > does not put real bugs (ie, not invalid, etc) in a final state, so > someone always has to come after them, and touch the bugs afterwards. > This is not the case for developers. I don't see the need here to oppose bug triager and developers here - yes, developers are members of the bug squad too, and the only aim of all these groups is to make Ubuntu work right. For this we need rule the best cooperation between all classes of contributors. And bug triagers are a really diverse group, from which you cannot expect to master every Ubuntu trick. The bug squad is not here to serve developers, but precisely to get needed information so that bugs are made useful to them. Developers also should make the life of bug triagers easier since their own work depends on the bug squad efficiency. As Henrik Nilsen Omma summed it up [1], there's just a need to find better conventions in order to make special bugs (sync requests...) conform to the general convention. No need to hurt anyone here: developers could simply use "Confirmed" instead of "Incomplete" when waiting for more information that *they will get by themselves*, and not from any user; "Triaged" and "In progress" are still here for more advanced states. And surely assigning bugs when somebody is taking care of a bug, even if no work is going on would help, since other developers that may want to work on the bug will know what kind of "special tricks" are involved. Hope we can find a common rule 1: http://lists.ubuntu.com/archives/ubuntu-bugsquad/2008-May/000854.html -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
