<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Read-only bar is unreadable when using dark theme" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103656#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Read-only bar is unreadable when using dark theme" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103656">bug 103656</a> from <a class="email" href="mailto:rq@akl.lt" title="Rimas Kudelis <rq@akl.lt>"> Rimas Kudelis</a> <pre>(In reply to Buovjaga from <a href="show_bug.cgi?id=103656#c5">comment #5</a>) > (In reply to Rimas Kudelis from <a href="show_bug.cgi?id=103656#c4">comment #4</a>) > > And of course, the LibreOffice QA team does not have resources of even one > > person to confirm this really trivial bug (all you have to do is switch on a > > dark GTK theme, even if just for a little while, and open a document from > > your e-mail, which triggers it being seen as read-only). > > > > What I don't understand is why you ask the original reporter to revisit the > > issues they file and "confirm" them by marking them UNCONFIRMED. Why should > > I be putting more effort into this than the QA team is putting? > > This sounds like you think we are getting paid for this. You should be > putting in as much effort as you can because we are peers. The border > between QA team and anyone else is nearly nonexistent. It is merely a > question of how much extra work one bothers to do. I'm making it sound like you're supposed to care a bit more than a casual user like me, since *you* are a member of the QA team, not me. I know quite well what open source is, but this mentality within LibreOffice QA team of some idealistic QA process being above everything else has annoyed me more than once already. I mean, if I wouldn't burst out like this, you (the LibreOffice QA and developers) would probably just ignore this bug until 4.4 is released, then ask me to confirm that the issue is still there, then ignore it again, then ask me to confirm that it's still there in 5.0, and so on and so forth. What is that supposed to tell me? If you don't think a particular bug deserves attention (low traffic, etc.), that's fine. But what's the point of asking submitters to re-test their bugs with each new release, if these bugs hadn't even been worked on?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>