18:00:08 #startmeeting tor browser 18:00:08 Meeting started Mon Aug 7 18:00:08 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:12 hi all! 18:00:14 hi everyone! 18:00:24 let's get started as usual with the status updates 18:00:30 who wants to go first today? 18:00:53 hi! 18:01:05 * arthuredelstein can go 18:01:18 This past week I worked on #22343, 18:01:25 I worked on building Firefox/clang with ubsan for #12418, 18:01:35 I reviewed a couple of TBB patches, 18:01:41 I met with the Tor uplift team, 18:01:46 and I took 1.5 days off. 18:01:55 This week I want to continue to revise and hopefully finish #22343, 18:02:00 review a bunch of fingerprinting patches for the Mozilla team, 18:02:11 start writing patches for ubsan errors, 18:02:16 work on #22989, 18:02:22 and revise my patch for #23024. 18:02:28 That's it for me 18:02:55 you take #22989? okay, good 18:03:06 can you reproduce that one? 18:03:25 I haven't tried yet. 18:03:36 i remember that we had icon issues with https-e 18:03:46 yeah, it does sound kind of similar 18:03:56 which ultimately let to the mutation observer hack 18:05:04 right 18:05:20 i hope there is something cleaner available :) 18:05:26 okay. who is next? 18:05:42 me too :) 18:05:58 arthuredelstein: #10095 has that story 18:06:31 i can go i guess 18:06:31 * mcs will go next 18:06:36 or GeKo :) 18:06:40 ah, go mcs! 18:06:47 Last week, Kathy and I spent some more time preparing for the Tor Launcher UI changes. 18:06:51 As part of that effort, we created a bootstrap progress "wish list" for the Network Team: https://pad.riseup.net/p/tor-client-progress 18:06:55 We also reviewed and commented on linda's latest Tor Launcher UI proposal. 18:07:01 We reviewed the patch for #22343. 18:07:09 We helped with bug triage and user support. 18:07:12 Finally, we worked on #21542 and got something working. Unfortunately, we encountered a problem where tor startup is delayed. 18:07:17 This week we are going to spend some more time on #21542 to see if we can solve the delay problem (it is related to async functions and promises that do not get a chance to run). 18:07:25 But soon we need to switch over to working on the new Tor Launcher UI and moat integration (#23136). 18:07:29 That's all for now. 18:08:00 here is what i did: 18:08:20 i was traveling 1.5 days with little time to work 18:08:36 the remaining hours went into release preparations/building and signing 18:08:55 boklm: i think 7.0.4 and 7.5a4 should be properly signed in my build dir by now 18:09:04 ok 18:09:17 i spent time on code review and testing for #22618 and friends 18:09:24 mcs: brade: good stuff! thanks 18:09:54 GeKo: Thanks and we will produce a fixup patch soon. 18:09:59 i got occupied by hackerone bug triage, we got still good reports (luckily none as critical as the one for 7.0.3/7.5a3) 18:10:18 and i started to look into #22692 18:10:26 i plan to continue with that one this week 18:11:10 then i want to work on #21256 and #18101 and help with the releases 18:11:40 + there will be some code reviewing on my plate i guess 18:11:49 that's all from me 18:12:26 * boklm can go next 18:12:42 This past week I helped build the new releases, I fixed #22499 and #23075 18:13:04 I started a README.HACKING file to list the main things to know when doing changes on the new build system: https://gitweb.torproject.org/builders/tor-browser-build.git/tree/README.HACKING 18:13:26 This week I'm planning to publish the new releases. 18:13:29 I will see if we can reproduce a build made with rbm (and try to fix it if not). For that I will soon push a 7.5a4-build1 tag. 18:13:43 Then I'm planning to upstream an FPCentral patch, and look at the resolution issue FPcentral is reporting on mac (and see if it is related to #22989) 18:13:52 That's it for me 18:14:26 boklm: i can do the signed tag thing if we want to simulate a "real world" scenario 18:14:34 just ping me 18:14:36 ok 18:15:24 boklm: one thing for the release i think we can do #22651 while we are at it 18:15:44 the torbrowser-launcher folks should have had enough time to fix their stuff i think 18:16:04 that said: who else is here for a status update? 18:17:24 i guess no one. 18:17:40 what about items up for discussion? 18:17:45 i think i have three today 18:18:11 1) just as a reminder: think about questions for our interview candidates 18:18:21 this is going to get serious this week :) 18:18:45 2) another reminder: we should come up with session ideas for oct 11th 18:19:00 just in case we need to invite other folks to those 18:19:29 i guess we'll have roadmapping sessions and mozilla upstreaming sessions 18:19:41 but maybe there is more we want or should have 18:20:17 3) i'll be afk next monday (and the remainder of the week if all goes well) 18:20:30 so i guess we just skip the meeting next week 18:20:44 for 2) it may make sense to have a session on the new Tor Launcher UI and/or bridgedb integration… or maybe we won’t need such a session :) 18:20:52 and come together on aug 21 again 18:20:57 Or maybe those won’t fit on the team meeting day 18:20:59 ? 18:21:31 skipping the meeting seems fine 18:21:43 mcs: i actually think one can make a good case for having such a meeting on this day 18:21:47 good idea 18:22:28 If we can steal away some network team people plus linda it seems good to have such a session 18:22:33 We will know more in a month :) 18:22:43 agreed (to both) 18:22:44 :) 18:22:53 I'd also like to discuss toolbar/UX stuff at some point during the Montreal meeting. 18:23:10 jupp 18:23:10 But not sure what day is best for that 18:23:46 it might not be in a stage yet that it should be purely team-based 18:24:00 i.e. we might want to get input from more folks 18:24:06 but maybe not 18:24:35 but, yes, montreal seems definitely a good place/time to move those items forward as well 18:24:40 I think input from more folks is likely a good thing 18:26:21 do we have anything else for discussion today? 18:27:43 okay then. thanks for coming and happy tor-browser-improving! *baf* 18:27:46 #endmeeting