15:00:48 <x1sc0> #startmeeting
15:00:48 <IZBot> Meeting started Tue Jul 31 15:00:48 2018 UTC.  The chair is x1sc0. Plugin info at http://wiki.debian.org/MeetBot.
15:00:48 <IZBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:01:01 <x1sc0> so let's get started
15:01:29 <x1sc0> #topic roll call
15:01:37 <x1sc0> anyone here for the QA meeting?
15:01:38 <bearon> here
15:01:57 <x1sc0> @Kompilainenn ?
15:02:01 <x1sc0> hi bearon
15:02:13 <bearon> hey
15:02:38 <x1sc0> buovjaga is on vacation I think
15:03:58 <x1sc0> taking into account it's July, I was already expecting less people than usual
15:04:27 <IZBot> News from tdfnew: [Bug 119017] [META] Signature lines bugs and enhancements <https://bugs.documentfoundation.org/show_bug.cgi?id=119017>
15:04:31 <bearon> what's on the table for today's meeting?
15:05:35 <x1sc0> Kompi mentioned something the other day about highlighting enhancements in Bugzilla
15:05:46 <x1sc0> I told him to discuss it in today's meeting
15:05:53 <x1sc0> but he's not around I think
15:06:52 <bearon> he wants to make them green instead of grey?
15:06:57 <x1sc0> from my side, now that the QA blog is up and running, I would like to discuss about it, ideas, comments, suggestions...
15:07:20 <x1sc0> yep, but I don't have more details
15:07:46 <bearon> is the blog a good place for discussions?
15:08:03 <bearon> comments are possible, but will interested people read it and comment?
15:08:04 <x1sc0> no no, I would like to discuss about the blog here
15:09:01 <x1sc0> also ask who would like to participate
15:09:07 <x1sc0> and have access to write
15:09:12 <bearon> ah, ok
15:09:21 <bearon> that makes more sense than what i thought :D
15:10:16 <x1sc0> also ask for ideas about which topics we should talk about in it
15:10:31 <x1sc0> kind of brainstorming
15:10:36 <bearon> yeah, the problem is, now it has to be filled with content :D
15:10:54 <x1sc0> yep ;-)
15:11:13 <x1sc0> I think it's good a good place to announce pre-releases
15:11:36 <x1sc0> I remember a couple of years ago, an email was sent, but not anymore
15:12:05 <x1sc0> so we can announce it with a blogpost at least
15:12:38 <x1sc0> not all I guess, but at least the most relevant ones
15:13:09 <bearon> well, an e-mail on the QA list would still be possible to do, right?
15:13:28 <x1sc0> yep
15:14:23 <x1sc0> both things can work, of course
15:15:33 <bearon> for reference, e-mails were like this: https://lists.freedesktop.org/archives/libreoffice-qa/2015-December/009262.html
15:15:42 <bearon> maybe cloph has more information? :)
15:16:51 <cloph> well, not more info than that really, we are now faster in moving from pre-releases to mirrors, so extra announcement of buils on early-testing didn't seem to be necessary anymore
15:16:52 <x1sc0> anyway, the people in the qa mailing list normally do qa, that's why I put the banner in Bugzilla
15:17:03 <x1sc0> so we don't annoy people with new releases every week
15:17:06 <lo-qa-tg> <Kompilainenn> I'm here
15:17:19 <cloph> previously buidls were done/triggered by multiple people, and builds were ready with sometimes multiple days in betweeen...
15:17:42 <x1sc0> @Kompilainenn hi there
15:18:01 <lo-qa-tg> <Kompilainenn> X1sc0: yes, i offer highlight enhacement in BZ
15:18:21 <lo-qa-tg> <Kompilainenn> It may be green color of font
15:19:02 <x1sc0> #topic highlight enhacements
15:19:15 <x1sc0> #idea <Kompilainenn> It may be green color of font
15:19:28 <x1sc0> it's grey right now, why would you like to change it ?
15:20:51 <lo-qa-tg> <Kompilainenn> Because gray is previously visited link for me
15:21:30 <lo-qa-tg> <Kompilainenn> And elae one: gray over white is bad for vision
15:22:33 <x1sc0> in my case, I get the id number changed to maroon when I have already visited the bug with Firefox
15:23:36 <x1sc0> I'm wordering if green can give problems to colour blind people
15:24:46 <x1sc0> @Kompilainenn, so in your case, you don't distinguish it at all ?
15:27:24 <bearon> feels like this should be a personalized setting... if that's possible at all
15:28:04 <bearon> probably not
15:28:43 <x1sc0> seems not
15:28:50 <x1sc0> I'm checking
15:29:23 <bearon> well, there's skinning possibility, maybe there?
15:29:58 <bearon> not user customizable, but can you check whether you could add a modified skin or something?
15:30:01 <x1sc0> I'm checking that, but they are stil grey
15:31:10 <bearon> x1sc0: https://wiki.mozilla.org/Bugzilla:Modifying_Your_Installation#CSS
15:32:35 <x1sc0> thanks
15:32:46 <bearon> https://bugzilla.mozilla.org/show_bug.cgi?id=36013
15:33:11 <bearon> Each entry in buglists have the bug severity as a class name (e.g. severity "normal" becomes class="bz_normal"), so everyone is free to edit e.g. their chrome/userContent.css CSS file and add their prefered style in it (if using Firefox. No idea about IE).
15:33:53 <bearon> @Kompilainenn, can you see if you can customize your colors based on that? ^
15:34:01 <bearon> if it works, we can add details to the wiki
15:35:28 <x1sc0> yep, good idea
15:35:29 <lo-qa-tg> <Kompilainenn> Hm. How I can change CSS file for site on my side?!
15:35:56 <lo-qa-tg> <Kompilainenn> I didn't understand
15:36:02 <x1sc0> I guess you change the userContent.css
15:36:18 <lo-qa-tg> <Kompilainenn> Where is this file?
15:36:25 <bearon> which browser are you using?
15:36:33 <x1sc0> #info https://superuser.com/questions/318912/how-to-override-the-css-of-a-site-in-firefox-with-usercontent-css
15:36:46 <lo-qa-tg> <Kompilainenn> Chrome and FF and Opera ;-)
15:36:54 <bearon> :)
15:36:57 <bearon> let's return to this after the meeting
15:37:09 <lo-qa-tg> <Kompilainenn> Ok
15:37:31 <lo-qa-tg> <Kompilainenn> If you will write instruction in wiki would be cool
15:38:17 <x1sc0> ok, let's try this after the meeting
15:38:49 <x1sc0> #todo check bearon solution to edit cssContent.css. If works, add it to the wiki
15:39:13 <lo-qa-tg> <Kompilainenn> But, would be very nice have options for customize our BZ
15:40:19 <x1sc0> i think that should be implemented by the Bugzilla team
15:40:55 <x1sc0> I could change it, but it would change for everyone
15:41:31 <x1sc0> and in that case, I prefer to use the individual solution (userContent.css one )
15:41:49 <lo-qa-tg> <Kompilainenn> I want ask you: we have many old uncobfirmed bugs. But there are many posts from many people in these bugs. Why these bugs have status unconfirmed? IMHO, need close it or make status to NEW...
15:42:51 <x1sc0> we shouldn't put it to NEW unless someone can confirm it and triage it
15:43:14 <x1sc0> even if there are many comments
15:44:25 <x1sc0> anyway, 95-98% of unconfirmed bugs are less than 1 year ago
15:44:32 <x1sc0> so not a big problem imho
15:46:53 <x1sc0> bearon, going back to what we were talking before, in my experience from the past, sending an email with every new pre-release made me ignore those emails
15:47:13 <bearon> fair enough
15:47:54 <bearon> so, back to the blog
15:48:25 <lo-qa-tg> <Kompilainenn> New QA blog?
15:48:50 <x1sc0> https://qa.blog.documentfoundation.org/
15:51:13 <x1sc0> maybe we can move the topic to the next meeting
15:51:18 <x1sc0> hoping more people will show up
15:51:29 <bearon> yeah, makes sense
15:52:12 <x1sc0> will look into the .css thing now
15:52:20 <x1sc0> I think I can close the meeting
15:52:35 <x1sc0> bearon, Kompi, thanks for attending
15:52:45 <bearon> thanks!
15:53:21 <x1sc0> #endmeeting