17:31:56 #startmeeting tor browser 4/8 17:31:56 Meeting started Mon Apr 8 17:31:56 2019 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:31:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:32:02 hello everyone 17:32:17 let's check out the pad 17:32:26 https://storm.torproject.org/shared/tHoN4Ii7rLSjPE0OP4gydX4cMGadsXmRQNc-6lwru0N 17:32:38 is the usual place to enter your items 17:32:57 and check the update of the others 17:33:14 please mark the pieces you want to talk about bold 17:34:07 hello! 17:34:28 acat: you around? 17:34:32 o/ 17:34:36 hi 17:34:41 hi 17:34:59 acat: could you add the items you worked on onto the pad? 17:35:00 o/ 17:35:12 we have a last week/this week category 17:35:26 so everyone knows what is yet to come and what got done 17:35:47 hi 17:36:25 hi 17:36:57 okay, let's get the status updates going 17:37:12 sysrqb: i have one item for you 17:37:15 and one for the group 17:37:25 i need review help with the tickets i worked on 17:37:36 mcs and brade picked already up a bunch, thanks! 17:37:57 boklm: could you pick up #30016 17:38:03 GeKo: ok 17:38:39 sysrqb: you are probably the best one for #28622, #29843, #29859 17:39:04 ack, i'll add those on my list 17:39:06 i think that's it 17:39:34 i might be able to finish #30069, too tomorrow or on wed 17:39:36 i'll look at the other needs-review tickets after i finish with these 17:39:44 cool 17:39:45 i think the other i can handle 17:39:54 or they can be postponed 17:40:01 okay 17:40:02 it's just the 4 right now 17:40:43 okay, it seems no ones else has anything marked bold 17:41:05 do we have other status update items or should we move on to the discussion part? 17:41:44 from Tails: anonym took {back,over} the "upgrade to Tor Browser 8.5" task. 17:42:15 intrigeri: great, 8.5a10 should have all the desktop things 17:42:23 modulo a fixup for #25658 17:42:57 one thing i heard on the comments were folks complaining about the removed noscript button 17:43:05 in particular in contexts like tails 17:43:42 because *if* they want to customize their scripts etc. they now need to put the noscript button back to the toolbar first 17:43:44 thanks, I'll point anonym to it. I'm not too worried about the noscript button personally. 17:43:46 every time 17:44:04 just sayin' 17:44:19 * antonela discovered that TB for Tails came with uBlock installed by default 17:44:42 i think we plan to implement the remaining part of prop 101 that shuold address that 17:44:55 but this very likely won't happen before 8.5 gets out 17:45:08 at least i hope it won't happen :) 17:45:30 thanks. that's all from the Tails side. 17:45:41 k 17:47:26 let's move on to the discussion then 17:47:47 i think we should start with the next meeting time 17:48:07 it seems neither pili nor i won't be available next week 17:48:14 and on monday 22th 17:48:20 yup, or the week after :) 17:48:33 so i guess this means no meeting next week 17:48:43 how about doing a sync on 23th 17:48:46 ? 17:48:55 the 23th works for me 17:48:58 maybe the same time and place? 17:48:59 works for me 17:49:02 +1 17:49:04 The 23rd sounds good to me 17:49:15 +1 17:49:16 do you want us to update the pad as usual on the intervening week? 17:49:56 i'll be traveling a little that week, but I should be available for a meeting on the 23rd 17:51:44 pospeselr: i think updating the pad before the meeting is fine 17:51:53 or whatever your update routine is 17:52:16 okay, then let's tentatively move the next meeting to that time 17:52:32 i'll announce that on tbb-dev@ 17:52:53 same time as today? 17:00 UTC? 17:53:13 well today is 1730 UTC 17:53:15 err, 17:30? :) 17:53:20 yeah 17:53:23 i think same time 17:53:34 okay 17:53:50 so, the 8.5a11 release 17:54:06 if we want to get 8.5 out in april 17:54:14 we need to get out 8.5a11 built this week 17:54:35 i am not worried about the remaining bits for #29768 which mcs and brade are addressing 17:54:59 but i don't know everything regarding #28239 and #27609 and friends 17:55:06 err 17:55:09 #28329 17:55:32 i think i'd need something to review by tomorrow and wed 17:55:41 how does that look like? 17:56:04 i am starting to get uncomfortable moving things further to may 17:56:19 mainly because that blocks other things we would want to get landed 17:56:24 and working on for 9.0 17:56:33 for #28329, we ran into a problem with the animation 17:56:40 and the more we are pushing 8.5 out the less time we have for those 17:56:59 sysrqb: yes, but what speaks against using what we have for now? 17:57:00 I have the library loading issue solved for Android. I'm doing build now so should have more info in a couple of hours. 17:57:13 so i think including a spinning onion will depend on whether we can resolve that issue with the designer's help 17:57:16 sisbell: ack 17:57:40 GeKnothing in particular is blocking using the current pulsing animation 17:57:45 GeKo: ^ 17:57:56 great, then let's go with that 17:57:57 other than trying to match the mock up 17:58:07 well, we can iterate on that later 17:58:22 android is just one platform of four right now 17:58:51 i don't feel the spinning justifies 8.6 getting delayed for the other platforms any longer 17:58:56 *8.5 17:59:09 that's fiar, i'll push my current branch today 17:59:48 okay. we might get it even easier that way as we coul dplan for the esr68 switch 18:00:11 like having this fixed once we switch to something newer 18:00:20 and then in shape for 9.0 18:00:30 sure 18:00:54 we can plan for that 18:01:09 okay, so i currently plan to get the build started on thursday 18:01:30 after reviewing the latest bits that got done on wed 18:01:47 sisbell: does that sound like a plan which could work for you? 18:02:02 sounds good 18:02:19 I'll touch base in a couple of hours, hopefully with good news 18:02:42 These builds are touchy beasts 18:02:59 yeah, thanks 18:03:20 anything else we should think about for 8.5a11 18:03:21 ? 18:04:22 okay, pili, you are up then 18:04:29 hi 18:04:47 I saw this ticket last week: #29837 18:04:57 and I thought it could be a nice one to discuss during this meeting 18:05:10 even though it's not a priority 18:05:18 just if anyone has any thoughts/ideas 18:06:25 metrics is the place where that info should live, imo 18:07:19 yes, agreed 18:07:23 hrm 18:07:44 but karsten has good points we should address 18:08:49 for example, is there any data that needs to be anonymised? 18:09:33 i expect yes 18:09:42 or at least bucketed 18:10:43 for example, they give us stats on which devices have installed the app and the count of each device 18:10:56 is there any information about hardware? 18:10:57 i belive we can get country-specific data, as well 18:11:18 butt we should be careful with that information 18:11:26 like, the most downloaded device 18:11:35 android version is helpful too 18:11:50 Some of the device info that Google collects could (nearly) uniquely identify a person. We should discard the long tail for sure. 18:12:11 antonela: yes, we can get that information 18:12:17 mcs: yes, for sure 18:12:44 great, that can be really useful for setting up some QA workflow in the future 18:13:26 yep 18:13:48 pili: so, yes :) 18:14:01 maybe we should drop the devices/android versions with less than 100 users 18:14:10 i guess we can tag that with our monthly tag and get to it after 8.5 is in shape 18:14:10 Yeah, you could correlate OEM device type, and carrier to get precise info on a specific user 18:14:23 pili: hopefully i'll be able to pick up this ticket, and a few others after the release is out 18:14:40 we should capture this discussion on the ticket 18:14:42 some devices are fairly unique 18:14:48 sysrqb: great :) 18:14:55 GeKo: semms like a good idea 18:14:59 *seems 18:15:11 i can put the discussion on the ticket and add the tag 18:15:25 thanks, that'd be good 18:15:30 i'll just copy out of the meeting if no ones says "no" 18:15:33 *no one 18:15:50 sounds good to me 18:16:10 i don't see a problem with that (considering it's already logged :) ) 18:16:17 okay, anthing else for today? 18:16:24 yeah, but maybe others do :) 18:16:32 one small thing 18:16:49 go ahead! 18:17:06 tomorrow during the Mozilla monthly meeting i'll demo TB8.5 sec settings, pospeselr could you help me if any tech question raise? 18:17:28 i can help you as well fwiw 18:17:39 yeah I think I can manage that :) 18:17:46 even better :) 18:17:50 perfect, thanks both! 18:18:15 alright, are we good for today? 18:18:18 groot 18:18:23 iamgroot 18:18:32 all good here :) 18:18:32 (: 18:18:39 mcs: brade: may i ask you to swap out #29197 for #30000? 18:19:02 i think the former can wait until may and i 'd like to see some progress on s27 work? 18:19:07 GeKo: ack. We wrote that before the S27 meeting :) 18:19:21 in particular as there might still need some help with the network team for that one 18:19:22 We have a lot to do to get up to speed on the S27 work. 18:19:39 it was not clear yet and we should find our early if possible 18:19:54 yeah :) 18:20:01 thanks! 18:20:12 alright, thanks everyone for today *baf* 18:20:15 #endmeeting