Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Apologies in advance about not including Julien's message, I'm still not
quite sure how to deal with direct email response vs. nabble response so
here is my response to not needing it.

I agree right now there isn't truly a need but as we grow I think that
recognizing who is QA and who isn't will become an issue. I've been
actively and aggressively seeking new QA members and I can say for sure
there are at least 2-3 who have either already started basic triaging or
have shown serious interest. There are also cases where I'm not quite sure
if a user is QA or not (the most notable here is Sasha something who I see
ALL THE TIME in FDO but I never can figure out his role....)

Maybe...just maybe....we can just start using the QA Assigned to? I don't
see the need quite yet but I see that as a potential solution. This way we
can also have a really clear list of who is triaging -- this will also make
future "bug triaging parties" and other mass QA events much easier to
coordinate with a list of email addresses and names who have helped in the
past X months.

My two cents. Happy Monday everyone.


Best Regards,
Joel


On Mon, Sep 17, 2012 at 12:05 PM, Joel Madero <jmadero.dev@gmail.com> wrote:

What about adding some kind of whiteboard status (I know....more....not
good), that is like "verified and prioritized by a member of QA", then in
the future when we're cleaning the NEW bugs and prioritizing them we know
when an experienced user has already done the triaging (vs. the user just
trying to get us to look at their minor bug faster).

Best Regards,
Joel

On Mon, Sep 17, 2012 at 11:58 AM, Michael Meeks <michael.meeks@suse.com>wrote:

Hi Joel,

On Mon, 2012-09-17 at 08:56 -0700, Joel Madero wrote:
I know that this is a touchy subject and needs a lot of discussion
but, how difficult is it to make it so you need permissions to change
priority and severity of a bug? My goal is to at least "kind of" deal
with priorities in the coming months but it's pretty much impossible
if a regular user can go in and set a bug as CRITICAL - HIGHEST
because of a minor alignment issue -- and this is pretty common.

        Heh ;+) in that case they need a support contract clearly ;-)

 I think we should start discussing if it's time to close off certain
things in FDO to regular users and start talking about who gets
permissions to do these.

        My suspicion is that the other freedesktop projects would hate
that,
and that this is something that we'd need to share with them; making it
rather difficult to fix.

        Hence the most-annoying tracker for 'blockers' and so on - I
guess we
could introduce other trackers for important-but-not-MAB type things
but ... there are clearly diminishing returns in interest from very long
lists.

        ATB,

                Michael.

--
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.