19:00:24 #startmeeting tor-browser 19:00:24 Meeting started Tue Feb 16 19:00:24 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:30 hi everybody 19:00:55 hi 19:00:56 first, sorry for the late rescheduling. it seems i need to highlight us holidays in my calender or something 19:01:34 my fault for not mentioning it earlier 19:01:54 Some US holidays are more important than others, but most schools and banks are closed on days such as Presidents’ Day. 19:01:59 It's our dumbest holiday, but who doesn't like those? :) 19:02:12 then we have a bit of an agenda today. first, status updates as usual, then we need to think about our next meeting as i won't be here next monday (and probably neither the rest of the next week) 19:02:33 and, third, we should think about about some kind of irc roadmapping session 19:02:46 given that the majority of tor browser folks won't be in valencia 19:03:03 alright, let me give you an update about stuff i did: 19:03:24 i fixed all the issues for getting esr45 built for windows 19:03:46 although, i can't get rid off libfaketime it seems, not sure why yet as it should work 19:04:01 then there was the chemspill that costed quite some time 19:04:03 impressive progress on esr45! 19:04:10 thanks, boklm, for helping 19:04:23 i had time to write on the design document 19:04:40 and i spent a bit time reviewing code. some of it already got merged 19:05:11 this week i plan to look at osx and linux builds with esr45 and do more reviwing and more design documentation stuff 19:05:21 that's it for me 19:06:50 * mcs can go next 19:06:57 Last week, Kathy and I filed #18292 and posted a stop-gap patch (already reviewed by GeKo and merged — thanks!). 19:07:03 We spent some time on bug triage, e.g., for #18199. 19:07:09 But the bulk of our time was spent on #13252. 19:07:15 This week, we will continue to work on #13252. 19:07:28 We are starting to work on the packaging changes (builders/tor-browser-bundle) but we have not done any work on migration yet (old directory layout to new). 19:07:37 We also have some questions about PTs that we will need to eventually answer for #13252. 19:07:42 E.g., how can we ensure that PTs will store all of their writeable data outside of the .app bundle on Mac OS? 19:07:47 That's all for us. 19:08:31 man, this is more complicated than i anticipated :/ 19:10:13 Something similar to that seems to happen on Linux, where the Download folder is internal to the tor-browser directory. Do we have a ticket for that? 19:11:16 I have an action item to file additional tickets for Windows and Linux to move all user data out of the application directory. 19:11:38 (I don’t remember if there is already a ticket about Downloads) 19:12:18 thanks 19:12:22 * arthuredelstein can go 19:12:49 Last week 19:12:52 I wrote a patch for #18297. 19:12:56 I revised my patch for #16990. 19:13:11 I looked into Emoji options for #18172, but I don't have a good answer yet. 19:13:21 I did some rebasing of our patches to ESR45. 19:13:39 And I worked on bugzil.la/1121643 19:13:46 (mainly unit tests) 19:13:49 That's it for me 19:14:49 what's up for next week? how is the rebasing going? 19:15:38 Ah, sorry next week. 19:16:06 More rebasing, finishing #18172, and hopefully finishing bugzil.la/1121643 19:16:56 I'm maybe 40% through the patches? A lot left to do. 19:17:07 ok 19:17:26 BTW, mcs and brade, would you like to do the updater patch rebasing again like last time? 19:17:42 Sure, we can do that. 19:17:57 thanks! :) 19:18:27 We want to make more progress on #13252 first if we can but I am not sure when you need the rebased patches. 19:19:18 i think trying to get #13252 solved for the next alpha and doing the rebasing afterwards is fine 19:20:57 sounds good. 19:21:10 * boklm can go next 19:21:24 This past week I reproduced builds of the releases. 19:21:28 I worked on #16009 and pushed an updated branch. Added a small patch to #18127. 19:21:41 I started looking at why some of our unit tests that should fail do not fail on Mozilla Try 19:21:55 This week I'm planning to work on #16009 and Windows / OSX support, and try to understand what happens to those non-failing unit tests 19:22:08 That's it for me. 19:23:39 is anybody else here for a status update? 19:27:34 alright. when does the next regular tor browser irc meeting happen? 19:27:55 i probably won't be here next monday and i probably won't have much internet access next week either 19:28:15 if other folks want to meet and discuss things that's fine, though 19:28:50 i guess monday in two weeks won't work either due to the dev meeting 19:29:44 I am flexible about meeting or not. It is good to touch base as a group but maybe no other day will work next week. 19:30:15 What about after the Valencia meeting (week after)? Or are you at IFF? 19:30:48 no, i am leaving march 2 19:31:14 i think i'd like to have a meeting that week as we have a release in the week thereafter 19:31:31 Sounds good to me. Maybe on the 3rd? 19:31:58 fine with me. boklm are you stying longer? would that work for you? 19:32:03 *staying 19:32:39 I will be at IFF, but I should be able to join the meeting on the 3rd 19:33:08 It's possible I may have a conflict on that date, but not confirmed yet. 19:34:22 well, i am fine with the 2nd as well if that works better for all 19:34:41 either works for us 19:34:56 it should work for me too 19:34:57 March 2nd works for me. 19:35:27 usual time? 19:36:31 sounds good to me 19:36:49 yes 19:37:16 yes 19:37:56 btw, daylight savings time (summer time) begins on March 13th in the U.S. 19:38:01 ok. it seems that got sorted out. I'll write an email later to tbb-dev 19:38:04 something to keep in mind in a few weeks 19:38:13 oha, yes, another thing to keep i mind, thanks. 19:39:19 let's turn to our pre-valencia roadmapping sessions 19:39:30 do we think https://trac.torproject.org/projects/tor/wiki/org/meetings/2015SummerDevMeeting/Roadmap/TBB is still accurate 19:39:32 ? 19:40:06 (modulo the e10s and sandboxing stuff) 19:40:48 OSX codesigning should be moved to something like “end of March” 19:40:55 looking at the stuff we need to deliver i think that looks not bad 19:41:02 yes, that's true 19:41:15 (hopefully mostly done this month) 19:42:10 i wonder if we need a separate seesion for that? or an email thread? 19:42:40 A session to add items to the roadmap and edit it or ? 19:42:51 maybe we are in good shape? 19:43:21 well, i think the roadmap is still good 19:43:36 we might want to flesh out who is doing what a bit but apart from that 19:43:48 there is no need to add new things to it AFAICT 19:44:27 mike plans to help with the feature review and is doing the network audit 19:44:33 which is a big help 19:45:33 so looking at the approaching ESR 45 stuff i think we are fine with sharing the workload 19:45:41 as specified on the roadmap 19:45:44 Maybe there is another item which is something like “Create patches to address new ESR 45 features.” 19:46:08 i can add that and put tbb-team as owner, yes 19:46:09 (or we can look at “update patches” as a very broad thing) 19:47:02 sounds good to me 19:47:38 done 19:47:51 After we finish rebasing to ESR45 I'd also like to work on "update our FF45-esr patches in Mozilla Bugzilla" 19:48:22 if that seems reasonable 19:48:37 yeah 19:48:42 Or maybe call it "work with mozilla to merge updated patches for ESR 52" 19:48:50 That’s a good thing to add. 19:49:37 added 19:49:47 thanks 19:50:00 i've put it into the October month as the contract ends there but that's just for planning 19:50:31 makes sense 19:50:37 who wants to finish the torbutton conversion? 19:51:49 Do we know how much more there is to do for torbutton? I cannot remember the contract details right now. 19:51:51 I'd be happy to contribute to that if it wold be useful. What is left to be done? 19:52:30 Kathy and I can help too. 19:54:19 i'd need to look at the torbutton code to see what is left 19:54:46 OK. Looking at the contract, it promises “Convert key Torbutton privacy features into Firefox patches" 19:54:51 all the privacy features should be converted to c++ code 19:54:52 yes 19:55:24 The idea being I think that someday a patched Firefox without Torbutton would still give you all the privacy features. 19:55:55 yes. so maybe the resizing logic we have on start-up would be one thing. uh...oh... 19:56:06 but i have to think about it a bit more 19:56:19 Quite a bit of Firefox is implemented in JS anyway 19:56:29 So I'm not sure it always makes sense to port to C++ 19:56:34 true 19:56:52 I'll add both of you and try to come up with a list for that item 19:57:18 sounds good 19:57:38 yup 19:57:47 Maybe the priority is to port patches that mozilla is perhaps likely to uplift? 19:58:15 yed, that as well 19:58:19 *yes 19:58:52 I think we could also make an argument that porting to Firefox is key, not necessarily porting to C++ (we should use good judgment, in other words) 19:59:09 that basically leaves the partitionalloc part which i need to think about a bit as well 19:59:22 mcs: yes, good point 19:59:53 Also, cleaning up torbutton code is a good thing to do if we have time and opportunity. 19:59:58 yes 20:00:23 ok. do we have more concerns/suggestions for the roadmapping being done in valencia? 20:01:02 Something to keep in mind is whether we need anything from other teams, e.g., the tor/networking team. 20:02:20 Something I think we haven't talked about much recently is issues related #5791. Is that something we want on the roadmap or are we just waiting for Mozilla to get their act together? 20:02:28 *related to 20:02:48 (In other words, sandboxing.) 20:03:13 mcs: i think we are fine at least wrt SponsorU stuff 20:03:59 not sure if we'd need adjustments for domain socket support but I'd say "no" here as well at the moment 20:04:18 GeKo: I think so too but there may be other dependencies. Anyway, something to think about. 20:04:51 arthuredelstein: i think given that we have actually a smaller team available now i'd say there is no e10s for us for esr 45 20:05:21 i like the idea for providing sanbox profiles in a contrib dir or something 20:05:39 but i guess that would start for the hardened series first anyway 20:05:52 *sandbox 20:06:45 GeKo: yeah. I guess probably we should look at it again for ESR52 when we have e10s. 20:06:51 so "getting their act together" seems it to be at the moment 20:06:52 yes 20:08:12 alright, do we have anything else for today? 20:09:20 In case anyone will be in Berlin on 22 Feb, the Mozilla policy team will talk about cookies I think. 20:09:52 ah, thanks 20:10:01 I think it's a public event, on the weekend (maybe 20-21 instead of 22.) Announcement on Mozilla german mailing list. 20:11:11 okay, thanks everybody. it was a longer meeting than usual and the next one will be on march 2 19 UTC *baf* 20:11:15 #endmeeting