Re: [libreoffice-design] Minutes from the UX/design meeting 2023-Feb-15

I was making a point about procedure and conduct, but - I'll bite :-)

* I use the term "bug" because we use "bugzilla" where everything is a 
"bug". I was referring to issues more generally - either bugs or RFEs.

* The question whether something is a proper bug or an RFE is often up 
for debate (i.e. "does this _have_ to change or would it only be 
_better_if this changed").

* You're assuming that issues discussed in design committee sessions 
take into account what's said on the bug page. That is often not the 
case. Session participants often did not read the bug page when it comes 
up for discussion, or only skimmed it, or only read the first comment. 
That is how one often finds comments in the minutes which are, in fact, 
already addressed on the bug page.

* When a bug/issue is missing a significant piece of information, say 
not addressing a major likely downside - that may be because of lack of 
rigor by the reporter; or because they had failed to notice such a 
downside; or possibly because the downside is actually unlikely (or not 
a downside), and was perceived only due to a misunderstanding / 
miscommunication.

* Issue reporters should absolutely not be expected to demonstrate an 
understanding of how and why the current state of affairs exists. This 
typically (not always) helps when reporting a bug or RFE, but it 
perfectly acceptable to file issues based solely on user experience 
and/or common-sense reasoning, without getting inside the head of 
whoever set the current state of affairs.



On 16/02/2023 1:39, toki wrote:
> On 15/02/2023 21:41, Eyal Rozenberg wrote:
>
> > objections or claims which I would probably be able to convincingly 
> > rebut or disprove are stated and accepted with no retort or objection.
>
> An RFE masquerading as a bug report has to stand on its own merits.
> It has to provide a number of datapoints:
> * What the benefits of the enhancement are;
> * What the downsides of the enhancement are;
> * How to minimize the negative impact of those downsides;
> * How to minimize the negative impact of the enhancement;
> * Reasons why the enhancement would be declined;
> ** Explain why the reasons for declining the enhancement are 
> insufficient to warrant doing so;
> * Present multiple use-cases showing how the enhancement aids usage;
> * Provide alternative choices of action to attain the desired outcome(s) 
> that the RFE requests;
> * Demonstrate an understanding of how and why the current framework exists;
>
> jonathon

--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy