18:00:30 #startmeeting tor browser 18:00:30 Meeting started Mon Sep 18 18:00:30 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:39 hi everyone 18:00:43 hi all 18:00:46 hi all and welcome to our tor browser meeting 18:01:01 as ususal let's start with a status update so everyone is on the same page 18:01:08 who wants to go first today? 18:01:22 hi 18:02:01 * mcs will go first 18:02:08 Last week, Kathy and I made more progress on #23262. 18:02:14 Integrating the progress bar within the setup wizard and network settings window turns out to be more work than expected, but we are getting close to done. 18:02:27 Along the way we have also been improving the UX for display of errors. 18:02:33 Last week we also investigated #23393 and created a patch. 18:02:38 And we reviewed the Moat API design and gave Isis some feedback. 18:02:43 This week we plan to continue working on #23262. 18:02:48 That’s all for us. 18:03:00 okay, thanks. who is next? 18:03:55 let me go then 18:04:28 this week i stumbled over #23393 or something quite similar while looking for something else 18:05:04 i reduced the issue as much as i was able but then my debugger failed me. it seems i can't attach to a running firefox process on my linux machines 18:05:10 and i have not figured out what is wrong 18:05:28 thanks to mcs/brade for picking things up 18:05:45 i spent time on #23409 and #23396 18:06:12 and with the help from bobowen i think i found a way to fix #16010 18:06:40 right now my test build is working on windows with sandboxing enabled and even usable 18:06:57 i try to upload a fresh build and link to it from the ticket later today 18:07:07 awesome! 18:07:24 and then if nothing serious comes up we can squeete it into the alpha which comes out next week 18:07:51 i did a bunch of reviews #22343, #23025, #23513, #23526, #23029, #23104 18:07:58 yay for sandboxing 18:08:03 and triaged all tbb-gitian and tbb-hardened tickets 18:08:10 yay indeed :) 18:08:28 and i moved the mobile browser dev hiring forward 18:08:45 Cool. 18:09:01 this week i'll finish #16010 and #23396 18:09:19 and make progress on #21256 and #23409 18:09:39 then there are the releases and i hope to start with getting rid of/triaging old torbutton tickets 18:09:46 that's it for me 18:10:09 * arthuredelstein can go 18:10:22 Last week I worked on ubsan, focusing on signed integer overflows. 18:10:28 You can see my summary here: https://trac.torproject.org/projects/tor/ticket/12418#comment:17 18:10:37 I also met with the Mozilla uplift team and reviewed four of their latest anti-fingerprinting patches. 18:10:45 (They're making excellent headway on the fingerprinting -- you can see progress at https://wiki.mozilla.org/Security/Fingerprinting) 18:11:33 GeKo and I also added text for our 2017 fundraising browser banner to the torbutton repo, which I plan to get ready for the next release. (#23483) 18:11:58 I'm waiting for images from the designer but those should be ready by today or tomorrow. 18:12:10 So this week I will be writing the banner patch and continuing on #12418. 18:12:22 Also I want to go back to #22343. For that ticket I need it's clear to me now I need to write regression tests to make sure all possible ways of "saving as" are covered. 18:12:45 That's it for me. 18:12:48 :) that's a big PITA 18:12:59 sorry for the needs_revision again 18:13:06 Yeah :( Apparently I'm not too good at testing my own patches... 18:13:23 i wonder what we can pick from #18101 for the upcoming releases 18:13:42 did you verify that the mac part is good as well? 18:14:02 otherwise i am inclined to pick at leats the linux defense 18:14:07 *least 18:14:22 and did you see the dns leak on windows too? 18:14:43 I haven't yet. But I agree that picking the linux defense is a good idea. Maybe I can squeeze in testing Mac and Windows this week. 18:15:05 that would rock 18:15:21 thanks. who is next? 18:15:31 * boklm can go next 18:15:46 This past week I did some test builds with GeKo's binutils patch for #23228. 18:15:49 I fixed #23513 and #23039, and made a patch for #23557. 18:16:04 I posted a patch on https://bugzilla.mozilla.org/show_bug.cgi?id=1305396 (which needs some revision) 18:16:13 This week I'm planning to post a new patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1305396 18:16:20 Then setup the Windows testsuite to be able to run it on the new releases 18:16:29 Continue the work on the Windows 64 build and help with building the new releases 18:16:37 That's it for me 18:17:14 boklm: where are we with the fp central deliverable? 18:17:33 I need to finish that too 18:17:46 ok. are there blockers you need help with? 18:19:14 boklm: ^ 18:19:21 I think there are no blockers. I currently have it running on a temporary VM. I need to open a ticket to have it on a tpo VM. 18:20:26 okay, good. time to get this deliverable finally done :) 18:20:40 who else is here for the status update? 18:21:41 You mean status of individuals? 18:22:53 i mean updates from folks who worked on tor browser 18:23:01 discussion time then i guess 18:23:08 i have just two reminders 18:24:25 1) isabela sent out an email to tbb-dev for brainstorming on future topics we want to work on 18:24:33 (sorry for the lag) 18:24:42 please have a look and think about that 18:24:58 2) the tentative schedule for the tor browser team meetings is ready 18:25:35 we'll have a roadmapping session from 11am-1pm, the uplift meeting from 3pm to 4mp 18:25:53 and the getting tor into firefox one from 5pm to 6mp 18:25:56 *pm 18:26:13 i'll send a mail to the mozilla folks so that they know about that as well 18:26:31 that's it from me. anything else we want to discuss= 18:26:35 That's the Montreal meeting you're talking about? 18:26:40 s/=/?/ 18:26:41 yes 18:27:15 Kathy and I should to be there just in time for the roadmapping session. 18:27:22 GeKo: What day do you plan to start building the next alpha/release? 18:27:41 (I'm thinking about torbutton banner timing) 18:27:59 release hopefully on wednesday and alpha on friday 18:28:18 but i guess we could rebundle for that in case it is too tight 18:28:36 That's pretty tight! I will try to get the patch in by tomorrow. 18:28:45 (I remember doing quite a bunch of rebundling last time ;) ) 18:29:08 Yeah... hopefully I won't screw it up this time. 18:29:20 otherwise we can think about doing another series of releases say in 3 weeks 18:29:34 which will have the things needed 18:29:38 The other thing is we are waiting for translations. 18:29:50 When do we want the banner to begin to be displayed? 18:29:57 yep 18:30:04 So if we rebundle later in the week the translations will presumably be more complete. 18:30:26 mcs: I'm checking the schedule, just a sec 18:31:00 I don’t really need to know; just curious. 18:31:02 :) 18:32:48 The campaign is launching on October 23. 18:32:56 At least as far as I understand from the calendar. 18:33:03 thx 18:33:10 Also, there is potentially a donor who will be match crowdfunding donations 18:33:56 But we're waiting to hear confirmation, which might not be for a week or two. So there might be an advantage in an additional release in three weeks. 18:34:06 arthuredelstein: so we could do the release in 3 weeks and oick up other things as well 18:34:25 GeKo: I hate to add an extra big burden to you and boklm 18:34:31 *pick 18:34:45 that's okay 18:35:08 If you think it's OK, then maybe we should just plan for it because it will probably go more smoothly. 18:35:35 I'll try and get the banner ready soon anyway so there is more time to catch any problems. 18:35:50 you mean just do the release in 3 weeks? 18:35:58 or the stable one at least 18:36:26 (with the banner stuff) 18:36:32 Right, I mean plan for doing a release in 3 weeks. But it depends on what you think is better. 18:37:05 i think leaving the banner out of the stable release but get it into the alpha 18:37:18 to be able to test better might be useful 18:37:37 and then we do releases in three weeks picking up the updates translations 18:37:48 That's a good idea. Our thinking was to suppress display of the banner until launch date, but I don't see any harm in showing it in the alpha early. 18:37:52 and the final thingg to be ready for the campaign 18:38:10 ah, showing it early. dunno 18:38:31 i thought just getting the code into and proceed as planned 18:38:55 testers can then use the alpha and enable the banner to see whether it looks right in the different locales 18:39:18 i think enabling it right away in the alphas and doing nothing in the stable series is confusing 18:39:24 Ah, OK, so we ask testers to enable the banner early with a pref or something 18:39:30 yes 18:40:16 and report back and that goes into the stuff we ship in the release in three weeks 18:40:23 i.e. in the week after montreal 18:40:37 Sounds good. I'll try to have a patch ready for tomorrow. 18:40:39 boklm: do you think this is doable? 18:41:36 I think yes 18:41:50 cool. then we are good it seems 18:42:04 thanks guys 18:42:08 arthuredelstein: let me know if there are plan changes 18:42:19 will do 18:42:22 and we need to get creative on short notice :) 18:42:26 thanks. 18:42:36 alright i guess that's it for today. anything else? 18:43:26 is the next TB alpha going to pick up tor-0.3.2 alphas? 18:43:39 yes 18:43:45 cool, thanks! 18:43:56 thanks all *baf* 18:43:59 #endmeeting