https://bugs.documentfoundation.org/show_bug.cgi?id=145037
--- Comment #14 from Eyal Rozenberg <[email protected]> --- (In reply to Telesto from comment #13) (In reply to Telesto from comment #13) > There is also the bug tracker issue > 1) If you propose a specific fix for alleged problem, shooting down the > proposal means, shooting down the 'bug' (annoyance/ design issue). Ah, but you often propose more than a fix - you propose a change which will be detrimental to other workflows. For example, in 145034 - you didn't say you wanted to be able to have the effect kinds sorted alphabetically, you wrote you wanted to change it for everyone. Those are two different requests. > 2) If I put forward a genetic description of the perceived problem - to > avoid people shooting on the solution - it will be soon to vague (lacking > direction) Well, you can: 1. Ask for help with making it concrete. 2. Write the mailing list (or soon the discourse forums). 3. Try to make the problem more concrete by describing your workflow, and be more exact about what's problematic/annoying to you. I also have this problem sometime, and am frustrated by, uhm, certain people repeatedly not understanding my bug reports. 4. Ask Heiko to put some subject on the design meeting agenda (if it's a UI/design issue). > Sometimes people ... don't see something which need to > addressed. There no problem at all: like it isn't a bug, but a feature. Or > seeing it as a trivial/unimportant drawback. My courses of action above should be relevant in those cases too. Of course, it may be the case that they're mostly right and what you want is a niche use case (happens to me occasionally). > However a single person having to come up with ideas, and others shooting on > it isn't much fun. I feel your pain, my friend ! T_T -- You are receiving this mail because: You are the assignee for the bug.
