[maemo-developers] bugs.maemo.org and moving bugs from UNCONFIRMED to NEW

[From: Anderson Lizardo]

On Mon, May 4, 2009 at 4:37 AM, Andre Klapper <aklapper at openismus.com> wrote:
> You need canconfirm permissions to move a bug from UNCOMFIRMED to NEW
> state. Other option: 3 persons voting for a specific UNCONFIRMED bug
> report will also automatically confirm the bug and change it to NEW.

Ok, that's clear now. The bug in case was one that the developer
(myself) detected and fixed even before somone voted on it.

> The wikipage mentioned to "ask the Bugsquad members to provide editbugs
> permissions to you so you have gain much more power to change things and
> work efficiently".

Well, even though I saw this note, I didn't really understand exactly
what "editbugs permissions" would give me, because I don't have these
permissions :).

> I've added more information about UNCONFIRMED->NEW; I hope it's clearer
> now.

I think it would also be nice to fix the text in
https://bugs.maemo.org/page.cgi?id=fields.html#status too (it is the
page that's shown when you click on the "Status" link in the bug
report page), as it says:

"UNCONFIRMED

This bug has recently been added to the database. Nobody has validated
that this bug is true. Users who have the "canconfirm" permission set
may confirm this bug, changing its state to NEW. Or, it may be
directly resolved and marked RESOLVED."

Should it be "editbugs" instead of "canconfim" ?

Regards,
-- 
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil