18:00:03 #startmeeting tor browser 18:00:03 Meeting started Mon Jul 31 18:00:03 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:07 hi all! 18:00:18 welcome to a new tor browser meeting 18:00:27 let's start with the status updates as usual 18:00:41 hi 18:00:50 hi! 18:00:56 GeKo: oh you're right, in high-sec mode also not much is working (with JS disabled) 18:02:06 * isabela is lurking a bit 18:02:25 who wants to go first today? 18:02:57 * mcs can go first 18:03:03 hi everyone! 18:03:05 Last week, Kathy and I created a patch for #22592. 18:03:13 We reviewed patches for #13398, #21321, and #23044. 18:03:22 We did some testing for #22434 and confirmed that we do not have a regression. 18:03:33 We did some miscellaneous bug triage / research. 18:03:43 We reviewed the Tor Launcher UI proposal, provided feedback, and participated in a meeting about it. 18:03:48 Finally, we started to look at #21542. 18:03:54 This week we will work more on #21542. 18:03:58 We will review linda's latest Tor Launcher UI proposal. 18:04:03 Also, we will create a "wish list" of what we need from the tor daemon in order to build the proposed Tor Launcher progress bar experience. 18:04:07 That's all for now. 18:04:44 thanks 18:04:50 who is next? 18:05:50 i guess that's me then 18:06:13 okay. we had to deal with #23044 which did cost me almost two days :( 18:06:32 but thanks to boklm's help we got releases out fairly quickly i think 18:06:48 even though we had to do a bunch of novel things 18:07:04 like just releasing for one platform, doing the releasing in sekrit etc. 18:07:35 then i worke on some reviews 18:07:51 for #22563, #23024, #22362 18:08:12 and #22542 18:08:31 i am currently looking at a bunch of other tickets marked with TorBrowserTeam201707R 18:08:49 hopefully we get many of them in the next alpha/stable 18:09:49 i did the usual bug triage and a bunch of meetings 18:10:05 this week i try to get things ready for the upcoming releases 18:10:21 the plan is to start the building on thursday morning UTC 18:10:30 hopefully we have a mozilla tag by then 18:11:24 i hope i find time to work further on #16010, #22692 and #21256 as well 18:11:30 that's it for me for now 18:12:13 who is next? 18:12:16 * arthuredelstein can go 18:12:26 Since last time, I posted a new patch for #22343. 18:12:39 and I worked on #12418 (ubsan). 18:12:51 I met with the UX team regarding security slider/NoScript UX. 18:12:59 And I met with Mozilla's tor uplift teacm and I reviewed some bugzilla uplift patches. 18:13:23 This week I plan to work on #22616 and continue work on #12418, and look at revisions to my hardening flags patches. 18:13:39 That's it for me 18:14:02 arthuredelstein: the most important things for this week would be helping with reviews 18:14:11 we need a second one for #21321 18:14:24 (i think it should go into the stable if all looks well) 18:14:42 and for #22618, too 18:15:07 Sounds good. I'll have a look at those and any other tickets needing review 18:15:27 and you might want to have a look at the one for #13398 even if it just is for seeing how one of the candidates writes coce 18:15:34 *code 18:15:41 yes 18:15:42 thanks 18:16:04 Oh, I forgot to mention I will be afk on part of Wednesday and all of Friday 18:16:27 * boklm can go 18:16:45 This past week I helped with the security bugfix release. I reviewed #20848 and #20929, and I worked on #22499 which is now almost ready. 18:16:54 This week I'm planning to finish #22499, try to compare rbm and gitian builds, help building the new releases, and work on the fpcentral setup. 18:17:04 That's it for me. 18:17:42 thanks. who else is here for some status update 18:17:43 ? 18:19:33 GeKo: boklm: thanks for your quick work on #23044 18:19:38 okay, discussion time 18:20:05 heh, yeah. luckily the patch was not so tricky and easily to test 18:20:57 arthuredelstein: this kind of issue is one of the things to keep in mind for the proxy-bypass-framework thing 18:21:15 i guess i'll mention that on the respective mozilla ticket 18:21:41 yes, definitely 18:21:53 mcs: before i forget it, i think i could need some help tracking #23064 down 18:22:06 like giving the user some useful things to try to get debug info 18:22:20 GeKo: okay 18:22:36 i currently don't have a mac anymore i could use and don't know the most efficient ways on OS X to get the information we need 18:22:53 One point of discussion could be code reviews via oniongit. Aside from the JS requirement that has come up, Kathy and I do not like the lack of integration between the bug tracker and code review comments. 18:23:09 isabela: ^ 18:23:13 (it will be harder to learn the history of a fix later) 18:23:33 mcs: I agree 18:23:33 hm. that's a good point 18:23:58 and just duplicating the comments does not make much sense 18:24:17 agreed. I wonder how the designers of that system intend for it to be used? 18:24:33 maybe it works better if you also use their issue tracker 18:24:45 but mozilla's mozreview seems to be something similar, right? 18:24:55 a different review tool and a bug tracker 18:25:16 or am i missing some integration they have that bridges the gap? 18:25:18 Mozilla seems to have some of the same issues. At least it seems to me that some people like the separation and some people do not. 18:25:35 ah, okay, that could be it 18:25:37 I think Mozilla has some integration but I don’t know all of the details. 18:25:48 mozreview comments get pasted back into the ticket generally speaking 18:26:18 aha, nifty 18:26:35 yeah, having that would be neat, i agrree 18:26:37 (with a few lines of source code for context) 18:26:40 *agree 18:27:02 there will be a meeting at the 7th 18:27:19 where we should bring up all the things we learned so far 18:27:52 Right. I will try to attend. 18:28:07 1400 UTC in #tor-project 18:28:52 okay. just as an announcement from me: i'll probably be afk on wednesday as i'll be traveling 18:29:14 and i plan to take another week of (8/14-8/18) 18:29:26 although i'll have internet in that one for emergencies 18:29:54 any other thing that's noteworthy or should be up for discussion? 18:30:33 if not, then thanks all! *baf* 18:30:36 #endmeeting