15:00:32 #startmeeting 15:00:34 Meeting started Tue Oct 30 15:00:32 2018 UTC. The chair is x1sc0. Plugin info at http://wiki.debian.org/MeetBot. 15:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:57 so let's start the QA meeting 15:01:07 anyone around ? buovjaga ? 15:01:32 yeah 15:01:45 Hola 15:02:04 yep 15:02:06 hello there 15:02:27 before we start it 15:03:13 I've just found https://nextcloud.documentfoundation.org/s/iTHS8NzoBF4bTDk 15:03:38 did you know about it ? 15:04:21 no 15:04:23 The shared directory? Yes, I had seen it before. 15:04:42 nope 15:04:50 first time I've been there 15:05:18 oh it has walrus graphics 15:05:23 in mascot 15:05:26 djredaux, did you use it for anything ? 15:05:29 News from tdfnew: [Bug 121062] The to cut a large amount of text including footnotes has increased from 15 tot 24 seconds 15:05:46 x1sc0: only to park a few files. 15:07:05 ok, now that we know it exists 15:07:14 we could use it more 15:07:29 actually it leads me to the topic I wanted to discuss 15:07:36 which I mentioned in the email 15:09:08 #topic monthly report 15:09:11 #topic monthly report 15:09:29 #link http://document-foundation-mail-archive.969070.n3.nabble.com/Libreoffice-qa-Request-for-content-to-the-next-monthly-report-td4251302.html 15:09:41 buovjaga, I really appreciate your email 15:10:08 i'm just wondering how we could get more people involved 15:10:15 and more collaborative 15:10:36 I think having a nextcloud document would be a good starting point 15:11:22 on the other hand, I'm afraid people stop adding things after a few months 15:11:37 actually, I haven't got any other email 15:11:39 x1sc0: I thought to just repeat the email to the list every month 15:12:10 I think the idea of summarizing closed issues during the last month is a good one. 15:12:13 list is the only mass-ping we can use sensibly :) 15:12:24 buovjaga: Agreed 15:12:46 buovjaga, should we add the link to the shared document in the email instead? 15:13:06 I mean, this way I could add new items to the document any time, so I don't forget about it 15:13:08 x1sc0: well, if you find it more convenient for you blog post construction :) 15:13:59 feel free to send the next monthly call for input with the link when it is time 15:14:59 Users do love bug fix highlights, which is proven by the KDE weekly blogging by Nate. But we should think of any interesting phenomena to add (giving hi fives to new people etc.) 15:15:17 or old people :) 15:16:39 yep, I agree bug fix highlights is a good idea, but I don't want to spend one morning summing up everything from las month 15:16:52 Along those lines of getting new people involved - it has always seemed to me that there was a missed opportunity with the hackfests and somehow QA functions could be worked into those. (a little off topic for today I suppose) 15:17:31 Ideally, I would love to just copy&paste what's in the document, created by many people 15:18:04 yes, I did not mean you should become Nate :) 15:18:26 that is why I want to try this crowd-sourcing thing and you can just click Publish 15:19:04 so everyone gives input on things they understand and care about, thus it will be high quality 15:19:13 buovjaga: 'just click publish' is that a reference to the blog platform or the NC/LOOL platform? 15:19:25 blog platform 15:20:01 I can even edit any links to HTML markup so you don't have to fiddle with linkifying in WP 15:20:14 just copy & paste & go 15:20:31 yep, that would be ideal 15:21:35 and regarding the content 15:21:44 would something like 'At least a dozen OOXML fixes were committed.' be to general ? 15:22:39 x1sc0: well, we can think about it as we go 15:22:45 and based on feedback 15:23:00 that could also be a place to collect NLP QA reports, would that be interesting? 15:23:21 I wanted to convey that interop is getting love, so users understand the general movement 15:24:10 sophi: do you mean like a monthly report? 15:24:42 buovjaga: yes, where we could collect what was done on QA in local groups 15:25:55 sophi, absolutely, we could add that info too 15:26:24 Anything that is narrative is interesting to users. The problem was having only statistics. 15:26:36 ok, thanks I'll pass a request to NLPs 15:26:49 sophi: xlsco: agreed 15:27:22 the good think about statistics is they are objective 15:27:58 the other way, we will always forget things to mention, but it's the way life is 15:29:03 the important thing is to generate interest and user engagement 15:30:56 buovjaga, I was checking nate's blog 15:31:24 x1sc0: is there a link for that - cause I don't know who Nate is? 15:31:36 #link https://pointieststick.wordpress.com/author/pointieststick/ 15:31:58 in the end it seems the blog is generated automatically as well 15:32:15 he just adds a screenshot or two 15:32:20 which is always a good idea 15:32:22 one main problem is that nobody read planet.documentfoundation.org blog 15:33:06 I read it :) 15:33:37 I had some hundreds views while on planet.kde.org I hat between 2.000 - 3.000 views 15:33:41 @AndreasKainz it is not a problem as we can link to posts to get publicity :) By linking the last post to Reddit, I got feedback and then this idea 15:34:07 Stats of TDF blogs are quite good 15:34:43 All I'd like to say is that the TDF planet is not really well known (or I had to boring blogs) 15:35:37 News from tdfnew: [Bug 121063] Dragging 3D fontwork or scroll past it or zoom in/out & in Writer is sluggish and a CPU hog 15:36:41 buovjaga, so just to have it clear, you would prefer to get rid of the current stats and talk about fixed bugs, or have both ? 15:36:53 In addition I also don't want to write blog posts for a 200 views e.g. 15:37:24 x1sc0: I never said anything about removing stats 15:37:45 "it would be nice to include some observations" 15:38:39 I'm not saying you said so, just to make sure 15:39:29 I would like to see something like next week we'd like to fix bugs for section x. Some taskforce bug triangle 15:40:12 and I do not want to talk about fixed bugs, but anything and everything that is interesting 15:40:49 for example 15:40:53 yep, I don't think we could list all fixed bugs either, the list would be too long 15:41:39 I like this ideea 15:41:42 x1sc0: maybe list fixed bugs with elevated severity rating 15:42:31 djredaux, yep, I was thinking the same, it's also easy too collect that info 15:43:56 the main idea is to get human touch in the blog posts :) 15:43:58 I write my blog for 100 views per day... 15:44:17 kompi is a blog businessman 15:44:31 do we have time for another topic? 15:44:39 lo-qa-tg: I kind of like that idea also - particularly for areas of functionality with a growing number of uncomfirmed reports. 15:44:56 the slide deck I just published on the members list has blog stats in it 15:46:25 buovjaga, yes, we have 15:46:32 Do you want read my blog?😊 15:47:03 so I've created a shared document for this month 15:47:08 #link https://nextcloud.documentfoundation.org/f/79818 15:47:17 x1sc0: thanks 15:47:28 I thought maybe it would make sense to have regular topics for the QA meeting. To kick ourselves in the butt in some things. Like, do we need to add people to the BZ contributors group? Do we need to update some wiki pages like QA/Team? 15:47:46 it would be wonderful if everyone present in this call could add a few lines on top of buovjaga lines 15:48:33 #topic regular topics 15:49:05 How many groups you want to make? 15:49:24 buovjaga, yep, I like the idea, it would also help to have an agenda ( sorry for that, I'm a horrible host ) 15:49:25 And what groups? 15:50:18 We need add achivement in BZ 15:50:32 @Kompilainenn the contributors group determines who can change priority & severity to the bigger values 15:50:35 For example: found 50 bugs 15:50:51 Need registration 15:51:24 x1sc0: looks like you have to click a magic button to share the file 15:52:01 Yes if you want to make it visible to non-registered users you must create a shared link. 15:52:04 I see djredaux is in the file 15:52:06 Buovjaga: our devs don't see on seveity and priority 15:52:59 Only if it's critical crash 15:53:25 your post should show also the dev's what's going on and what would be needed 15:54:08 x1sc0: sure because I already have an account. If you make a shared public link non-registered users could see it and download it, but not edit it. 15:54:52 but I believe there is a way to have it world-writable? 15:55:01 like a pad 15:55:15 buovjaga: yes, sorry, that is an option also 15:55:37 choice is made when the link is created. 15:55:53 I'm checking 15:57:16 You can also make multiple links to the same file, one with write authority, and one without and possibly one with an expiration date. 15:58:15 buovjaga, any other idea that we should make recurrent ? 15:58:18 correction - any of the links can also be setup with an expiration time. 15:58:42 x1sc0: no other ideas right now 15:59:04 I am sure we will get more ideas later :) 15:59:06 buovjaga, ok, for now I'll add those to the agenda, we can add new ones later on 15:59:16 yep, it's a good point 16:00:41 djredaux, I don't see those options, just the share sidebar 16:00:47 I have one item to add for an agenda in a future gathering, but I really want to think it through a bit more - I would prefer to just follow up on the ML 16:01:22 djredaux, sure 16:01:44 closing the meeting 16:01:44 #endmeeting