18:00:57 #startmeeting tor browser 18:00:57 Meeting started Mon Oct 17 18:00:57 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:03 hi all! 18:01:07 Hey! 18:01:20 hi everyone! 18:01:27 let's get started with the usual statuts update thing 18:01:33 who wants to go first today? 18:01:42 hi 18:01:47 I'll start I only have one thing to say really 18:02:16 go! 18:02:25 I filed #20375 which seems like a good stop-gap solution until #12977 is implemented 18:03:52 The window size warning works when tor browser is fullscreen, I tested 18:04:27 I'm going to look into working on it this week 18:04:31 That's it for me 18:04:36 cool, thanks 18:04:50 yes, it might be worthwhile at a stopgap 18:05:11 although i still have not lost hope to see the real thing (#14429) land one day ;) 18:05:22 Me too :) 18:05:51 yeah, thought so :) 18:06:51 i can go 18:07:14 so last week i spent quite some time to get our nightlies going again 18:07:51 i did not finish the debugging yet but felt i am closer to understand what goes wrong with the vm creaton on ln5's machine 18:08:06 meanwhile i used my regular build machine to get some nightlies going 18:08:23 which turned out to be a good idea as i discovered that the move to GCC 6 is premature 18:08:40 see #20381 for the details 18:08:56 the good thing is that we found it before we started releasing things 18:09:25 the bad thing is that i spent a ton of work to get a deliverable finished which we need to back out now :( 18:09:48 apart from that i had the pleasure to work on the next OTF proposal 18:10:01 we submitted v4 on friday 18:10:14 we'll see whether it survives this time 18:11:18 then i spent time on reviewing and merging tickets #20244, #20304, #20373, #18093 18:11:26 and i started with #20111 18:11:45 i hope this time it survives my testing 18:12:19 then i spent quite some time testing yawning's sandboxing efforts and started making plans to work on getting this into gitian 18:12:29 #20352 18:13:08 this week i plan to work on #20352, get another pile of reviews done and am hopefully able to get our nightly builds going again 18:13:21 i think that's it for me for now 18:14:01 * mcs will go next 18:14:16 Last week, Kathy and I spent most of our time on Unix domain socket work. 18:14:21 We posted a revised patch for #20111 and created a patch for #20185. 18:14:28 We also reviewed some patches and spent some time looking at the new (proposed) security slider text. 18:14:35 This week our focus will be on MacOS sandboxing (#20121), code reviews, and any remaining Unix domain socket work. 18:14:40 That’s all for us. 18:14:58 * arthuredelstein can go 18:15:06 This week I wrote patches for #20373 and #19459, 18:15:11 I revised #20244, 18:15:15 I reviewed #20111, 18:15:25 I met with the Mozilla folks, and I worked on #16622 (not done yet) 18:15:36 This week I will try to finish #16622, and help with any SponsorU items as well as the Mozilla uplift. 18:15:44 That's it for me. 18:15:53 * boklm can go 18:16:05 This past week I have been mainly working on #19067, and made a patch for #20210 18:16:08 This week I'm planing to continue working on #19067, and on #20186 18:16:22 That's it for me 18:17:18 re #19067 18:17:33 i think the plan looks good 18:18:07 ok 18:18:22 this is a deliverable and there is not that much time left so, it might be smart to think about 18:18:31 different stages we want to reach 18:18:52 where, say, stage two is the full plan you outlined 18:19:07 but satage one would be enough to meet the deliverable 18:19:29 e.g. i guess makeing those things reproducible could be for stage 2 18:19:48 yes 18:19:50 i.e. is not critical to get done before oct 31 etc 18:20:36 so maybe it would be helpful to create new tickets for the things in stage 2? 18:21:01 while the stuff we definitely want to have for the deliverable could be done in #19067? 18:21:17 ah, yes, I can do that 18:21:24 might be easier to keep track on what got done as must-have 18:21:29 okay, good. 18:22:20 oh, and please keep #15138 on your radar 18:22:28 ok 18:22:41 i think this requires only one or two additional tests for the testsuite 18:22:56 but is a thing we need for sponsoru as well 18:23:00 ok 18:23:54 okay, anyone else here for a status update 18:23:56 ? 18:25:06 then let's start the discussion time 18:25:21 does anybody have items? 18:25:31 While thinking about window size I wondered how a tabs to the side tor browser would look, and installed the mozilla test addon tab center. it ground tor browser and my computer to a complete halt. But I personally think it's an idea worth testing, maybe with a different extension though, so we keep the content the same size but give more space to the interface and tabs etc. 18:28:13 https://testpilot.firefox.com/experiments/tab-center <- that one? 18:29:17 We would be taking away horizontal space instead of vertical. I am nit sure if that would be better, but people are used to “tabs on top.” 18:29:27 s/nit/not/ 18:30:11 yes, i had the same feeling 18:30:47 amyway, interesting experiment i guess 18:30:51 *anyway 18:31:24 Or multiple rows on top even would be better 18:31:39 one item i have is that we should be aware for OS X users on older systems (at least 10.6) showing up and complaining after we ship #20204 18:32:17 it seems that the fix leads to issues with scrolling down on a website 18:32:55 i grab the scrollbar now i am dragging down the whole window instead of scrolling down 18:33:16 i can still scroll down with the keyboard though 18:33:54 Is there a Firefox bug about that? I guess Mozilla dropped support for 10.6, right? 18:34:03 not sure if other pre 10.9 systems are affected 18:34:21 yes, mozilla dropped support for 10.6, 10.7 and 10.8 with firefox 46 18:34:49 Do you know if 10.9, 10.10, and 10.11 are okay? 18:34:52 newere firefox versions are not even running on pre 10.9 systems anymore 18:35:00 newer 18:35:04 actually, no 18:35:25 i did only some guessing here 18:35:42 if you have the hardware i can upload a bundle for testing 18:36:29 i actually suspect the fix for #20204 only 18:36:39 but 6.5a3 is working fine 18:36:57 and since then not many patches have landed on our 45.4.0esr 18:37:04 and only osx is affected 18:37:31 Kathy and I can check some other OSX systems but I don’t think we have access to systems with each OS. Maybe we are missing 10.7, 10.8,and 10.10 (I will double check) 18:39:22 okay. i'll upload the bundle after the meeting 18:40:12 anything else for today? 18:41:01 What are the dates for our next TB releases? 18:42:45 I think 2016-11-08 and 2016-12-13 18:43:21 Thanks. 18:43:45 the same as on https://wiki.mozilla.org/RapidRelease/Calendar 18:44:12 yes, unless things are severely exploding before then 18:44:23 or in-between 18:44:42 alright. thanks for the meeting *baf* 18:44:45 #endmeeting