https://bugs.documentfoundation.org/show_bug.cgi?id=153131
--- Comment #69 from ady <adylo811...@gmail.com> --- (In reply to Mike Kaganski from comment #68) > (In reply to ady from comment #67) > > ... so the conflict should rather > > be investigated and solved (instead of simply staying passive and claiming > > some possible "not-our-bug"). > > Using this passive voice, do you mean that the conflict should do something > itself; or do you actually assign someone? Meaning, that you likely have > power to tell some volunteer developer to start working on this and that? > > Phrases like that are useless, and in fact rude. This bug wasn't set > "NOTOURBUG", nor any other "we won't work on it" resolution. You have a > point that it should be NEW - go ahead and change the status, since it is > enough a single independent reproducing report, and a confirmation that it > is indeed a problem (rather than expected behavior - which is obvious in > this case), to mark it as such. @Mike, I didn't mean that. After several comments and even dupes, the report is still set as unconfirmed. That seems strange to me, and I don't understand why. In that context, it would look as a passive attitude, in the sense of the practical consequence. But perhaps there is a reason not to set it as new(?). Sometimes, when "a group" shares something (as oppose to one person in particular), then no one actually takes responsibility or action or cares enough to do something (e.g. wasting energy in a public place). Regarding my "not-our-bug" comment, it is just a possibility, that some would suggest such status (considering that it is not set to new, and I still don't know why). Since the report was/is not set to new, maybe someone would think that all these symptoms should rather be solved by MS. Maybe the problem is really not at all a bug in LO, but IMHO it would be better to try to find some way to make it work anyway, for the reasons I mentioned before in my prior comment. I don't see anything rude in that. On the contrary, it is a humble and respectful "ping" about this report (starting by sincerely asking for the possible reasons for this report not to be set as new, with an attempt to summarize the current situation), but maybe I am too naive. -- You are receiving this mail because: You are the assignee for the bug.
