18:00:25 #startmeeting tor browser 18:00:25 Meeting started Mon Jul 10 18:00:25 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:31 hi all 18:00:40 hi 18:00:43 hi 18:00:44 and welcome back to our regular meeting schedule 18:00:57 let's start with our usual status updates 18:01:06 who wants to go first today? 18:01:25 * mcs can go first 18:01:36 Last week, Kathy and I were on vacation and afk most of the time. 18:01:41 During the prior two weeks, we finished #18913 (thanks to GeKo for his review and for landing the patch). 18:01:47 We spent a little time on #22618, #22659, and #22731. 18:01:55 We participated in the localization AMA session on June 23rd. 18:02:02 Finally, we provided some feedback on Linda’s proposed Tor Launcher redesign and on June 30th we attended the meeting that she organized on that topic. 18:02:07 This week, first we will catch up on what we missed while we were out. 18:02:12 Then we will take a fresh look at the download prompt problem (#22471 and similar tickets). 18:02:17 Maybe we can fix https://bugzilla.mozilla.org/show_bug.cgi?id=440892 or come up with a different workaround that is compatible with ESR 52. 18:02:22 That's all for us. 18:02:46 I found a self rando bug, and I am horrified that people writing a linker don't understand the Linux system call calling conventions. 18:02:46 mcs: welcome back 18:02:48 the end 18:02:54 i hope you had a nice time afk :) 18:02:56 GeKo: thx 18:03:17 fwiw: there is #20105 and #17670 waiting for your input 18:03:32 GeKo: ack 18:03:35 but upstream fixed it 18:03:40 so yay I guess 18:04:17 yes, we'll use that new commit (or a later one) in our next alpha release 18:04:40 which should give us selfrando for 32bit linux builds as well if all goes as expected 18:05:43 okay, i can go next i think 18:05:51 last work week was short for me 18:06:17 i caught up with my backlog and ticket triaging 18:06:24 i helped getting 7.5a2 out 18:06:39 i worked on the begin-of-the-month team admin part 18:06:50 and started to update the design doc for the 7.0 series 18:07:04 this week i plan to continue that and get back to my work on #16010 18:07:13 i plan to do reviews 18:07:48 and try to find tickets for our browser job application 18:08:03 that's it 18:08:28 oh i forgot i encountered #22832 and debugged that a bit 18:08:45 begin-of-the-month-reproducibility ftw! 18:08:58 who else is here for the status update? 18:09:00 My report is shorter: Aside from the Mozilla All Hands and stuff from that; I have been making (more) progress on getting MinGW into taskCluster, but it is still not there :) 18:10:36 thanks. do we have an arthur here today? 18:10:44 arthuredelstein: ^ 18:10:50 Yup, hi! 18:10:52 boklm is afk this week 18:10:54 hi! 18:11:09 Hi everyone -- since last time I wrote a patch for mingw-w64 to deal with #22563 and #22584. 18:11:16 The mingw-w64 folks have accepted the patch into their master branch, so I will try to write a step applying that patch into our build. 18:11:20 I also fixed my patch up for #21999, 18:11:35 and I worked on #22343, but it still needs more work. 18:11:56 This week I will try to finish that last ticket and then look at more tbb-7.0-must tickets and tbb.7.0-issues. 18:12:04 Also I want to look at a couple of security flags in our build. That's it for me. 18:13:18 arthuredelstein: you are still interested working at some hardening deliverbles, right? 18:13:34 GeKo: Yes, for sure 18:13:41 if so have a look at https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor4 18:13:54 3.2 activity 1 and 2 18:13:58 if you look for areas 18:14:14 i think there are tickets for almost all of those things in our bug tracker 18:14:39 (i got reminded of that due to recent activity on the CFI and UBSan tickets) 18:15:01 okay, anyone else here for a status update? 18:15:02 OK, great. 18:15:51 arthuredelstein: while thinking about your RWX page work (good stuff!) i was wondering whether we could make tests for that 18:15:55 GeKo: CFI isn't mentioned there; would that still count toward our general hardening deliverables? 18:15:57 which we could run in our test suite 18:16:29 GeKo: Yeah, I was thinking about that. I do think it's possible and maybe something we could uplift to Mozilla as well. 18:16:54 neat. care to file a ticket and making boklm aware of that? 18:16:56 I'll open a ticket 18:16:59 :) 18:17:36 re CFI i think we could argue that it is covered by the 3.2 activity 2 18:17:44 s/the// 18:18:44 okay. let's move on to the discussion part 18:18:49 i have two items: 18:18:49 OK, cool :) 18:19:18 1) if any of you finds tickets or has some in mind that would be cool to have for browse dev candidates 18:19:35 please file them and/or tag them with `tbb-interview` 18:19:57 the sooner we have a bunch of those tickets the better 18:20:21 if there are questions/concerns with the whole process feel free to raise them as well 18:20:26 be it here or via email 18:20:58 2) I was wondering whether we want to try to test gitlab for code review like the network people are doing 18:21:39 there will be a meeting tomorrow 1400 UTC in #tor-project about moving things related to trac and code review tools forward 18:22:02 and it might be helpful if we decided we want to be part of that testing period or not 18:22:19 boklm indicated slight interest in trying this tool out 18:22:31 what do other folks think? 18:23:35 I do not know a lot about gitlab but am willing to try it. I would not want to use it if it is “process heavy” or adds a lot of overhead. 18:24:02 okay, arthur? 18:24:31 Yeah, I'd like to try it too. 18:24:48 okay. then let's do that. 18:25:15 i think the way to get started it talking to hiro for account to our tpo instance 18:25:38 anything else up for dicussion today? 18:26:15 How many candidates do we want to do tbb-interview tickets do you think? 18:26:28 is the AF_LOCAL firefox bug going to be fixed anytime soon 18:27:46 Yawning: i doubt we get to that this month; having an upstream bug might speed things up though 18:28:04 arthuredelstein: i think three at least 18:28:21 Sounds good 18:28:34 geko anytime 18:28:49 :) 18:29:22 okay. thanks for the meeting then *baf* 18:29:25 #endmeeting