13:14:47 #startmeeting 13:14:47 Meeting started Wed Jan 27 13:14:47 2016 UTC. The chair is colonelqubit. Plugin info at http://wiki.debian.org/MeetBot. 13:14:47 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:14:55 Hello, hello 13:15:07 UNCONFIRMED bugs are down to 606 13:16:11 I've heard from just a couple of people re: bugs that should be escalated to the ESC 13:16:52 And I got some good feedback and made some nice contacts (especially in education) at the SCALE conference in California this past week 13:17:46 colonelqubit: great for your contacts :) I'm not sure there is an ESC tomorrow, as everybody will be at the hackfest 13:17:59 sophi: ah yes, that makes sense 13:18:35 sophi: if not, that's fine -- we can punt those bugs until next week 13:19:18 ok 13:20:06 sophi: I've noted a number of persisting mail merge bugs. I don't use that particular feature extensively, but are you seeing any issues in our latest builds? 13:21:46 colonelqubit: didn't followed that topic, sorry, but I've not seen much feedback on the lists about it 13:22:12 beluga_away: mentioned a bug yesterday (actually a duplicate of one of jmux reported bugs) 13:22:27 DennisRoczek: something particularly bad? 13:23:01 News from tdfnew: [Bug 97393] English Dictionaries update - 2016 13:23:52 sophi: Here's the link: http://bit.ly/1POJrmp 13:24:09 7 open (6 in NEW) mail merge regressions 13:24:18 a crash, lemme check my logs 13:24:25 * colonelqubit nods 13:25:09 #97287 and tdf#90185 13:25:11 LibreOffice-Writer major/high NEW Writer crashes just as Mailmerge begins to send the first email. https://bugs.documentfoundation.org/show_bug.cgi?id=90185 13:26:22 DennisRoczek: 90185 is on that list; 97287 is not 13:27:48 you're welcome 13:27:53 :-) 13:28:31 colonelqubit: the jmux one should be the last of your list #96914 13:28:33 LibreOffice-Writer normal/medium UNCONFIRMED MAILMERGE crash on first run after DB registration https://bugs.documentfoundation.org/show_bug.cgi?id=96914 13:28:55 DennisRoczek: looks like beluga has at least mentioned 97287 on 90185; if it's confirmed and not a dupe, I'll make sure to bring it up to ESC 13:29:51 * colonelqubit really wishes we could avoid more regressions through unit tests 13:30:31 let's take a look at the pending items 13:30:34 #topic Pending Items 13:30:34 colonelqubit: write more unit tests :-D 13:30:40 oh some for you ^^ 13:31:47 DennisRoczek: (re: Unit Tests) -- yeah, at some point it probably makes a lot of sense to try to stop the bleeding from starting (via tests) than to just sop up the lost blood (by triaging bugs) 13:32:04 \offtopic /me is doing a great comparison on Calc/Apple's iWork Numbers function names (see https://wiki.documentfoundation.org/Functions_comparison_of_LibreOffice_Calc_and_Numbers ) 13:33:12 colonelqubit: well as some devs say: every bug / regression fix should include a tests for not introducing yet another the same test 13:33:13 DennisRoczek: is that related to your work comparing ODF software? 13:33:18 sophi, DennisRoczek: my bug is not directly mail merge related. There is already a fix for it in private/jmux/mm-cleanup 13:33:27 and depending on our frameworks, it shouldn't be so hard to get more tests in 13:33:41 (btw: do we take part of google code-in?) 13:33:42 jmux: ok, thanks 13:33:57 jmux: great to hear! 13:34:10 colonelqubit: totally unrelated. but I need to check iWorks if it finally is able to export/import ODF stuff 13:34:38 DennisRoczek: I'd be very interested to hear your results 13:35:04 obviously understanding what's out there in the ODF ecosystem is important 13:35:06 but it was fun (and will be fun for the rest) to check which spreadsheet software is isuperior in which area 13:35:09 And while testing stuff, I even found more bugs. I actually stopped opening new reports and just continued fixing the stuff I found. The patchset is already 25 patches long 13:35:09 we won :-p 13:35:38 if iWorks is struggling (or disagreeing) about how to handle ODF, then that's something that we should perhaps investigate 13:36:15 colonelqubit: scroll to the bottom of the link i gave: simple calculation + bug ticket in the introduction for dtardon ^^ 13:36:28 colonelqubit: well apple is crap 13:36:32 no odf :-( 13:37:32 well at least in iWork. in textedit and finder there is odf support -.- 13:38:03 DennisRoczek: a few years back when I asked people on the Apple forums whether Pages supported ODF and open standards, I got rather bellicose "The file format is XML! It's open -- just read it yourself" responses 13:38:24 colonelqubit: that WAS true. now it is binary 13:38:46 DennisRoczek: the fact that the "premier"/most office-suite-like stuff is the one that *doesn't* support ODF is absolutely hilarious 13:39:15 I will definitely make sure to let everyone know about that the next time I give a talk 13:40:03 DennisRoczek: we should wrap up the digression (although we are riffing on one of your pending items ;-), but is the binary format documented, or just some internal, proprietary thing? 13:41:15 colonelqubit: give me until tomorrow night. I do want to do some further tests regarding OS X 13:41:21 then I give you material to fire 13:41:30 * colonelqubit nods 13:42:15 thanks! 13:42:52 DennisRoczek: so to the topic at hand: Do you think that 'Comparison of ODF Software' should live under ODF/ somewhere? 13:43:54 well we have multiple comparison pages. no. i do not think so. moreover we have [[Category:ODF]] and it is linked on ODF under see also, too 13:43:55 colonelqubit: it's more 'coverage of ODF implementation' no? 13:44:03 sophi: not at this stage 13:44:23 for that you best talk to the devs of the ODF test suites 13:44:35 (the Netherland guys, I always miss the name(s)) 13:44:42 or was it dutch? 13:45:01 DennisRoczek: Jos 13:45:39 DennisRoczek: sure, and for the comparison pages, maybe they could all live under some hierarchy? (if they fit together at all...) 13:46:38 thx 13:46:54 It's like with the BugHunting Sessions -- I was thinking that instead of having each one be a top-level page (BugHunting_Session_5.1.0.0), we could have (BugHunting_Sessions/5.1.0.0) 13:47:17 colonelqubit: how do you want to map them together? Comparison/LibreOffice_vs.MSO? 13:47:30 colonelqubit: how do you want to map them together? Comparison/ODF_software? 13:47:37 colonelqubit: yes, you're right, that's more logical and easier to find 13:48:00 Marketing/comparison/OPC_software ? 13:48:04 *ODF 13:48:45 DennisRoczek: hmm...they seem somewhat disparate 13:49:11 DennisRoczek: if some hierarchy doesn't lend itself well, perhaps a sidebar or horizontal bar, like Wikipedia uses for a number of articles in a category? 13:50:03 DennisRoczek: Most of these comparison pages are pretty accessible by the userbase, I believe? 13:50:04 it's all possible. simply say (at best with an en.wikipedia example) what you want 13:50:18 hopefully they are 13:51:01 DennisRoczek: My biggest concern is that we'll have pages with good content that don't get used or viewed much, because there's no strong path to find them 13:51:31 * DennisRoczek hopes on google :-p 13:52:18 Let's see -- I haven't had a chance to look at that BHS stuff yet. Thanks for that, Dennis! 13:52:31 colonelqubit: well my function comparison was mostly because I do will implement the Numbers function mapping the week after the next as it seems (just got the framework from dtardon http://cgit.freedesktop.org/libreoffice/libetonyek/commit/src?id=e54e5817f7d56a5fac0e0dac2f1cfd1255355e44 13:52:32 libetonyek - allow to map function names 13:52:33 ^^ 13:53:01 brb 13:53:04 News from tdfnew: [Bug 97394] Format a sheet section CLEAR Function 13:56:42 DennisRoczek: I'm taking at look at the EasyHacks page as well --> you mentioned having trouble there previously? 13:59:48 DennisRoczek: yeah, looks like the Keywords piece is what's not working. IIRC I also ran into some caching issues with that plugin previously 14:00:41 #topic New Items 14:00:59 sophi: You mentioned investigating a new time for the QA meeting 14:01:38 (it's a perennial problem) 14:01:46 colonelqubit: yes, I think it's too early and maybe we should find a later time in the day to gather more team members 14:01:54 * colonelqubit nods 14:02:48 I'll send out an email with a link to one of those meeting-time-pickers 14:02:55 sophi: How late is too late for Europe? 14:04:24 I think it would be past 9 PM UTC 14:04:31 * colonelqubit nods 14:05:35 re, colonelqubit: well I have no clue how the plugin needs the keywords provided (in contrast to the whiteboads keywords) 14:05:54 I'd suggest that we keep it to a weekday, as well 14:05:56 dunno about the caching. it simply doesn't work 14:06:22 DennisRoczek: I'll dig into the code 14:06:25 colonelqubit: weekday is bad for me. 14:06:35 colonelqubit: yes I agree 14:06:41 19 utc+1 infra call and de-call sometimes 14:06:55 at 20:00utc+1 I'm away (always) 14:06:57 DennisRoczek: did you say you have a test VM for that wiki? 14:07:33 we have a testwiki, but not configured. no db etc. alex is doing it at fosdem so i can finally test the upgrade (this is important) 14:08:06 DennisRoczek: ah ok, that might make it faster to identify and fix 14:08:59 DennisRoczek: if we don't do weekend, what day(s) of the week would work well for you? 14:09:30 well for what? 14:09:38 oh i see 14:09:52 friday is bad. all other days should work mostly 14:10:10 (so mo, th, tu,) 14:10:11 colonelqubit: but it's important that the time fits for you too 14:10:21 sophi: oh, definitely 14:11:07 :-) 14:12:44 Okay, I've got some good rough parameters for meeting times. We'll look Mon-Thu from say 14:00 UTC - 20:00 UTC 14:13:14 And I'll block-off TDF and ESC call times 14:13:44 #action Set up doodle for new QA Meeting time 14:13:51 colonelqubit: I've no meetings on Tuesday, it's the only day of the week, and Wednesday is impossible 14:14:20 colonelqubit: how about the pending actions regarding BHS? have you all information you need? 14:14:21 sophi: so you'd prefer Tues, or would like to keep it clear? 14:14:45 colonelqubit: Tues is ok, no problem, it's fully available :) 14:14:54 * colonelqubit nods 14:15:05 DennisRoczek: I think I have info -- I'll email you if I have additional q's 14:16:51 Looks like our time is about up. 14:17:00 Any other New Items? 14:18:47 Okay, that wraps it up! 14:20:04 Thanks for attending. Our next meeting will be tentatively... February 10th, unless we change it based on that Doodle 14:20:29 hopefully we get a good number of responses! 14:20:31 #endmeeting