[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-design] RFE process between QA and UX


Hi Kendy,
Le 16/12/2014 18:50, Jan Holesovsky a écrit :
> Hi Sophie,
>
> Sophie píše v Út 16. 12. 2014 v 16:57 +0100:
>
>> Discussing with QA team today, there has been a lot of bug reports
>> concerning minor enhancements these last days.
>> It would be better is those enhancements would be first discussed by the
>> UX team before going to QA for triage because most of the time they
>> don't have the requested info regarding bug filling then QA team has to
>> spend a lot of time to reproduce them and this is not up to the QA team
>> to discuss UX enhancements.
>
> Please can you send few examples to have a better idea? :-)

https://bugs.freedesktop.org/show_bug.cgi?id=87360
https://bugs.freedesktop.org/show_bug.cgi?id=87357
or see this list:
https://bugs.freedesktop.org/buglist.cgi?bug_status=NEW&component=ux-advise&email1=philipz85%40hotmail.co&emailtype1=substring&list_id=505514&product=LibreOffice&query_format=advanced

Asking
> because:
>
>> So it would be much more efficient for both teams to:
>> - first discuss the enhancement here or on redmine (I don't know your
>> process :)
>
> If it is something small that is obviously the right thing to do (like
> some wording fix or so) - then it would be awesome to encourage the
> reporter to fix it himself / herself & send a patch via gerrit.

yes, but if the patch is reverted or not needed, it will be frustrating
either for the implementer and for the developers. Not every idea is
good to put on BZ or in a patch, a little discussion before would help
to see if it's need, could be implemented or not :)
>
> If it is something bigger, then sending the bug id here to the ML is OK
> of course; or add it to the weekly hangout agenda, so that we discuss it
> there.
>
>> - then fill a RFE when it's consolidated with all the needed info for
>> the QA team
>> - let the UX team confirm it quickly so it goes out the QA review
>> process and stats.
>
> I'd say - either confirm (if the idea sounds interesting), or close as
> wontfix ;-)

Yes, but that is a lot of work for bug triagers. If you well know the
functionality, it's easy to discriminate, but for QA people who do not
have that knowledge, the lack of steps to reproduce, examples, etc. is
very time consuming plus the fact that he won't know what to do with it
(50% of users would like to have it and the other 50% won't), when it
can be solved quickly by discussing a little bit.

Cheers
Sophie

--
Sophie Gautier sophie.gautier@documentfoundation.org
Tel:+33683901545
Co-founder - Release coordinator
The Document Foundation

--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Follow-Ups:
Re: [libreoffice-design] RFE process between QA and UXJan Holesovsky <kendy@collabora.com>
References:
[libreoffice-design] RFE process between QA and UXSophie <gautier.sophie@gmail.com>
Re: [libreoffice-design] RFE process between QA and UXJan Holesovsky <kendy@collabora.com>
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.