19:00:19 #startmeeting tor browser 19:00:19 Meeting started Mon Mar 5 19:00:19 2018 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:23 hi all! 19:00:27 hi everyone! 19:00:31 hi! 19:00:42 that's the last meeting before we meet face to face in rome, welcome! 19:01:04 as usual the pad should have the upadtes for this and last week 19:01:06 !!!!!!! 19:01:19 please have a look and mark things bold you want to get discussed 19:01:26 hi 19:01:29 the url is https://storm.torproject.org/shared/tHoN4Ii7rLSjPE0OP4gydX4cMGadsXmRQNc-6lwru0N 19:01:34 howdy 19:01:44 hello! 19:02:21 o/ 19:03:07 * antonela is lurking 19:04:27 * tjr is here, but doesn't have much to say, aside from very excited about the clang stuff! 19:04:53 isabela: the pad is not loading for me (the roadmap one) 19:05:07 i get an invalid token error 19:05:15 * GeKo tries harder 19:05:15 * boklm had to remove the ) from the URL 19:05:28 (Actually I thought of something, bolding) 19:05:59 aha! 19:06:22 alright. let's get started 19:06:52 release preparations. 19:07:22 i think it's the first time we have to do a release during the dev meeting (at least one, maybe two due to pwn2own) 19:07:30 which is quite exciting 19:07:51 mozilla moved the release schedule after we finalized the meeting date, so here we are 19:08:22 i plan to have the bundles signed and on my people dir before i am leaving on saturday morning 19:08:44 if that's not working we'll see :) 19:09:12 there are a bunch of things up for review if any of you feels bored 19:09:25 for the stable #25112 is important 19:09:34 GeKo: https://storm.torproject.org/shared/OUn6YN7BEK2QiJXdk8tXxep9u24oBMiZ2mavmfH_0Ky 19:09:43 the remaining things is alpha stuff as i see it 19:09:51 yeah, thanks. 19:10:28 i just wanted to give that update here during the meeting so that everyone is aware of the plan at least 19:10:33 and in case there are questions 19:10:49 what day is Mozilla releasing? Friday? 19:11:01 tuesday 19:11:13 okay 19:11:18 during our unsrtructured day 19:11:32 I plan to look at the #25112 changes after this meeting 19:11:37 which would allow us to look for fast internet and do the things we need to do 19:12:02 i already asked hellais and i am confident we can sort things out in case we have to do some signing etc during the meeting 19:12:17 it's only a ton of extra stress and distraction i like to avoid 19:12:19 * isabela ok i go! 19:12:21 to another meeting! 19:12:37 \o 19:12:37 isabela: i'll ping everyon about the pad 19:12:46 it's on the discussion items 19:14:14 tjr: replied on the pad 19:14:34 i think we should try to get the mingw thing for esr 60 in shape a last time 19:14:59 okay; will dig into the x64 breaks on -central and try to clean them up! 19:15:02 and then fix all the remaining clang issues properly and get it into the shape we need 19:15:15 there is no DEP and ASLR yet (not sure how hard that is) 19:15:25 there are some ugly hacks for bugs i had to do 19:15:31 there is still a compiler crash 19:15:34 and on 19:15:51 and probably a ton of reproducibility issues we need to sort out 19:15:57 Hey something else for everyone to think about in Rome, which ill put on the pad too: which is more valuable to do first: a proxy bypass test harness for mobile or for desktop? 19:16:08 we could think about switching to it for 8.5 maybe? 19:16:20 as i would like to have stylo enabled sooner than later 19:17:04 i haven't looked, will stylo be optional in ESR60? 19:17:26 not sure yet 19:17:32 It will be 19:17:40 ah, okay 19:17:42 okay 19:17:52 It still works today, and they're not going to rip it out during the soft code freeze or beta :) 19:18:07 (It being --disable-stylo) 19:18:16 tjr: what timeframe for the test harness are you thinking about? 19:18:36 is it stuff that will be worked on starting from next week? 19:18:43 or in 3 months? 19:18:44 or? 19:18:53 Heh. "2018". Deployed in Q3 at the earliest, but I want to start thinking about it and talking about it soonish 19:19:03 hm 19:19:19 As it will require infratructure changes in our test infrastructure so I want to start talkign to those folks sooner rather than latest 19:19:29 tjr: i think i tm ight make sense to start with mobile then 19:19:30 given the uncertainty around the future of mobile with fennec/focus, etc 19:19:47 it might be easier with mobile, maybe 19:19:49 We think Mobile will be much easier. So there is that. 19:19:53 because i expect much more issues on that platform than on desktop 19:20:14 What do we need to do to be ready to enable stylo? 19:20:21 yes, it definitely will be more useful, immediately on mobile 19:20:47 arthuredelstein: fix https://bugzilla.mozilla.org/show_bug.cgi?id=1390583 properly 19:21:04 well, we can enable it on linux and os x 19:21:07 i guess 19:21:12 and we should 19:21:20 but the tricky one is windows 19:21:55 I see 19:22:02 igt0: sysrqb: while looking over your items: what's the state of the roadmap you have been working on? 19:22:20 i think it would be neat to have something to read before we meet in rome 19:22:26 if t hat's possible 19:22:44 I have a draft I wrote a few weeks ago 19:22:45 just to have some time to think about it with a text and some ideas in front 19:22:56 but not much progress since then 19:23:13 even a rough draft can be good for getting fast feedback 19:23:14 maybe we can work on it and send out a link on Wednessday? 19:23:18 ok. if you think it could be helpful please pass the text along 19:23:30 what arthur said 19:23:35 sysrqb: yes, that would rock 19:23:39 or even friday 19:24:13 okay, igt0 and I will work on that and send an email to the list with text and a link to the pad 19:24:23 it is stalled, however after the sysrqb investigation about feature extension, i think it will be easier to propose something more concrete. 19:25:16 +1 19:25:36 thanks, sounds good 19:26:00 do we have anything else before we move on to the discussion items? 19:26:20 I was curious about sysrqb's comment to me 19:27:03 oh, yes 19:27:05 I wasn't sure there was something to discuss 19:27:06 sysrqb: you are up 19:27:08 sysrqb: Any more details? 19:27:09 but happy to do it 19:27:21 Looked like you were going to write more :) 19:27:34 oh, i see! : 19:27:50 the pad timeed out and I guess the end of that sentence didn't sync 19:27:56 anyway 19:28:03 Do you know when that discussion will be? I'm definitely interested in discussing localization 19:28:07 "I'm interested in that conversation" 19:28:14 so no 19:28:33 I spoken with Erin, and she's under the impression you and colin are already planning on discussing it 19:28:44 re Localization Lab 19:28:54 That's true, although I don't know if we have it on a schedule yet. 19:29:32 I'll make sure you hear about it if we decide on a time. 19:30:19 OK, I think we're done with that one! :) 19:30:26 sorry 19:30:37 they kicked me out of another area :/ 19:30:49 but yes, i think having that conversation will be good 19:30:57 great! 19:31:17 i know some translators are upset they put in time for creating new localization and they never get used 19:31:41 yes, it's a serious problem I think and I'm hoping we can work out a strategy in Rome. 19:31:55 cool, sounds good, thanks 19:31:59 what is missing? 19:32:59 i thought the way to get more localized tor browsers out was pretty clear? 19:32:59 which languages? 19:33:23 multilang? 19:33:40 i know we're limited by which langpacks mozilla provide 19:33:50 ah, okay, the whole discussion then, good :) 19:34:00 Yeah, there are just a lot of details. 19:34:06 don't worry about that limit for now 19:34:15 One of the big questions is multi-lang vs many single-locale bundles 19:34:21 we are far from having that problem at the moment :) 19:34:42 GeKo: I'm not sure we ever came to a conclusion about fastly either 19:35:00 fastly? 19:35:37 ok, i see, let's not derail the meetin and talk about it in rome :) 19:35:42 *meeting 19:35:47 so discussion items: 19:35:47 When we were discussing adding locales earlier, there was a conversation about whether there would be a problem with permitted bandwidth via fastly 19:35:51 yup 19:36:14 yeah, true 19:36:17 ok 19:36:37 1) the meeting pad. please fill in details for things you want to have on our agenda 19:37:10 this will help the whole discussion (otherwise it's only stuff isa and i will bring up) 19:37:36 it's not only about roadmapping but all the other meeting we have as well 19:38:38 i there are things not fitting to any of the items on the pad 19:39:04 but you think it's still important let isa and me know so we can think about how to address those issues 19:39:24 letting them fall through the cracks is a bad solution :) 19:39:53 should we do a mobile show-and-tell on Sunday? or should we do it another day? 19:40:05 probably only 15-20 min, I think 19:40:09 unless there are many questions 19:40:24 sounds good 19:40:42 we have two hours for roadmapping 19:40:57 i think we could have that block as the intro for the mobile part 19:41:23 and then create a preliminary roadmap 19:41:30 that'll work for me 19:41:43 and refine that later on taking all the things we learned throught the week 19:41:48 into account 19:41:49 just to confirm: we should be filling in details on this pad, right? https://storm.torproject.org/grain/wyfgitPrKrr6sgXrvMQEyG/ 19:42:20 arthuredelstein: https://storm.torproject.org/shared/2RXUuAa_G4_GNy5yHFt8gjFqOv2wAJeq8-_0mQmSBiP 19:42:33 i don't have access to the former, so dunno 19:42:54 *through 19:43:01 Oh good, seems to redirect to the same thing 19:43:05 okay, and 2) next meeting 19:43:14 i know it's early to think about that :) 19:43:35 but anyway, we are in rome next monday, so no irc thing 19:43:48 and i think we can skip the one on the monday thereafter as well 19:44:17 so, the next irc meeting would then be on march 26 19:44:26 does that sound reasonable? 19:44:30 yes 19:44:45 the 26th sounds good to me. We also need to remember about time changes (daylight/summer time) 19:44:58 yes, I saw the networking team mentioned that, too 19:45:00 indeed 19:45:07 so 1800 UTC? 19:45:42 sure 19:46:05 sounds good to me 19:46:13 k 19:46:20 (this time works for me, I don't know if another time woould be better for anyone else) 19:46:22 i'll try to find out what the network folks are doing 19:46:35 so that we don't collide with our meetings 19:46:36 1800 UTC sounds good to me 19:46:59 GeKo: I think they're discussing it in rome 19:47:09 sounds good 19:47:24 ok, do we have anything else for today? 19:48:22 hearing nothing. okay, thanks for attending and safe travels everyone o/ *baf* 19:48:26 #endmeeting