QA Field in FDO - What's the Purpose (discussion)

During our last QA call we had a continuing discussion about the QA field
that Rainer began a few weeks back [1]

Basically the conversation is "what's the point of the QA field"

There are multiple opinions:

1. QA Field should represent exactly what Dev field represents, ie. QA
contact is responsible for everything QA related, if further testing is
asked for, bibisect etc...QA contact should do it

2. QA contact is just a way to signal "QA has looked at this, priority has
been set (most of the time)" but there is no obligation for the QA contact
to monitor bug further - usually they will as they are receiving emails and
are familiar with the bug but other QA people are able to update and get
further details to devs.

3. QA contact is a combination of #1 and #2, they should do "everything in
their power" to keep up with the bug and if they are unable to provide
something, should find someone who can.

There are pros and cons to each. One of the biggest points IMO is that if
it's #1, QA contact may just not be used because we can "easily" become QA
contact for 10 bugs per day and just get overwhelmed with being responsible
for each bug. Just got give an idea I am currently QA contact on 170+ bugs,
I tend to follow rule #3 but when I get really busy triaging I go to #2 ;)

We need consensus on this one to move forward, input greatly appreciated.

Best,
Joel

[1]
https://wiki.documentfoundation.org/index.php?title=QA-FAQ&oldid=64417#What_does_it_mean_if_Bugzilla_Field_QA_Contact_is_not_empty.3F


-- 
*Joel Madero*
LibreOffice QA Volunteer
jmadero.dev@gmail.com