17:30:01 #startmeeting Tor Browser meeting 2019-09-30 17:30:01 Meeting started Mon Sep 30 17:30:01 2019 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:30:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:30:09 Hello everyone! 17:30:12 hello! 17:30:24 * sysrqb finishs add items on the pad 17:30:31 o/ 17:30:32 reminder: https://storm.torproject.org/shared/tHoN4Ii7rLSjPE0OP4gydX4cMGadsXmRQNc-6lwru0N 17:30:34 \o 17:30:35 hi 17:30:42 * tjr is caught up in something but will see a highlight 17:31:27 hi 17:31:42 hi 17:31:53 hi 17:32:23 hello! 17:34:01 okay, let's start in about 2 minutes 17:34:19 hiii 17:35:44 okay 17:36:05 welcome everyone for another week of tor browser development! 17:36:19 antonela: i think you're first 17:36:34 hi :) 17:37:31 hi folks, i've worked on some options for the new identity button we want to have at the toolbar 17:37:49 feel free to leave your feedback at the ticket #27511 17:38:07 we should decide who will work on that item 17:38:15 we don't have too much time so if it happens this week, double appreciated 17:38:15 it's not much time left 17:38:48 it should not be that hard, given it's essentially adding just a toolbar button 17:38:53 but still 17:39:14 and, re : #31778 - i saw acat listed it for this week so, alex ping me if you need anything 17:39:57 antonela: "- #a - Anything needed on my side for this?" 17:40:03 should that be #31778? 17:40:22 si, fixed 17:40:24 good, i can also work on #27511 17:40:27 good :) thanks 17:40:42 acat: thanks! ping me if anything 17:41:19 okay, pili, i think you're next 17:41:23 do we have any winner if we look at anto's design options right now? 17:41:24 about FOSDEM 17:41:43 ah, we have some time, we can talk about that now 17:41:46 oh, we moved on, nvm then 17:41:50 heh 17:41:53 https://trac.torproject.org/projects/tor/ticket/27511#comment:17 17:41:56 whatever 17:42:08 i think it might be worth trying to settle on a candidate right now 17:42:11 while we are here 17:42:19 (if possible) 17:42:28 that'd be useful, yes 17:42:37 I don’t like the first two (trash can and going back in time) 17:42:42 hi, sorry, i got a phonecall 17:42:45 here now 17:42:48 yeah, that's a good idea 17:43:07 np pili, we'll talk about antonela's question and then get to yours 17:43:13 I like the ID card but it’s hard to recognize with the vertical line in the middle 17:43:33 of the options i like the cleaning brush icon 17:43:36 yeah, the ID card isn't immediately recognizable as such to me 17:43:41 though it might should be tweaked becasue it also looks like a bell 17:43:55 the vertical lime makes it look like a squished apple to me 17:43:59 line* 17:44:09 yeah id card only really reads for me when you're zoomed in 17:44:19 I like 3 best although the concept in 4 is good (hard to decipher the icon though, as others have said) 17:44:20 which doesn't really work when it's little icon sized 17:44:23 the cleaning brush / broom icon looks intuitive to me 17:45:10 could it work if i iterate the brush/clean version? 17:45:19 i like delete (1st one) 17:45:34 make it less look like a bell, and also refine the little size version 17:45:37 the 2nd one looks too similar to a Refresh/Reload icon to me, though I may be an outlier on that opinion 17:45:50 acat, i also like the trash as a concept 17:46:01 antonela: I’d rather you iterate on the ID. Can you make it look more like a driver’s license (US-thinking??) 17:46:48 brade, yes i could! i used that id because is the one that comes with https://design.firefox.com/icons/viewer/# 17:47:09 ctrl+s+formfill 17:47:24 the 3 and 1 look like the easiests to understand for me 17:47:53 im quite happy that the 3 option got some fans 17:47:53 antonela: did you decide against using a fire image? 17:47:56 like ddg browser 17:48:00 (i think) 17:48:11 sysrqb: i didn't, maybe the trash do that work too 17:48:21 i like the fire, tho 17:49:10 antonela: I don’t recognize that as “form fill” :-) 17:49:25 me either :? so i took it as an ID icon lol 17:50:50 this is a good feedback folks! thank you! if you have deeper ideas you can paste them in the ticket for the posterity. On my side will iterate based on what we just talked and back to the ticket asap 17:51:14 thanks antonela 17:51:23 once someone takes the ownership of that ticket, please let me know! 17:51:28 thanks sysrqb 17:51:49 any last comments on this? 17:52:02 or odes anyone want to work on this? 17:52:05 *does 17:52:15 (while we're talking about it) 17:52:52 i can work on it (already said :) ) 17:53:06 :) 17:53:09 oh, thanks acat :) 17:53:20 good stuff acat, thanks 17:53:37 but will we have a decision on the icon this week? 17:53:43 i hope so 17:54:10 ok! 17:54:34 okay, pili 17:54:37 hi 17:55:08 just an announcement that I'm trying to put together a main track talk for fosdem and looking for potential speakers 17:55:29 also can do other non-main track talk 17:56:00 as it seems like there will be a decentralized internet and privacy devroom 17:56:11 neat 17:56:56 that's it 17:56:59 anyone have questions or comments about this? 17:57:21 (sorry; Internet out.) 17:57:37 :( 17:58:12 sisbell: how is #31564 going? can anyone help you with that? 17:58:19 pili, I've considered going to FOSDEM but can't commit to attending at this time (mostly due to travel cost + lost dev time that it would entail) 17:58:38 sisbell: i see your update, but i'm not sure what else we can do 17:58:46 sysrqb: At this point, I don't need any help. I just have to manually track every resource 17:58:50 Jeremy_Rand_Talos: yup, I understand, that's also why we're trying to send people from Europe from the Tor side also :) 17:59:17 I tried this a while ago and had missing resources so I'll need to track down where those are built 17:59:45 Its tedious but should make it repoducible 17:59:45 pili, there are some European Namecoin devs, but they're less involved in the Tor-related dev aspects of Namecoin 18:00:02 sisbell: we can likely get a slightly newer version of apktool in buster, if that will help 18:00:11 (within the same major release) 18:00:49 That could also work. I'd test with the version prior to putting in buster so we can verify 18:01:23 When are we moving to buster? 18:01:26 okay, we should ping _hc and ask about the newest version he can package 18:01:35 This could impact other platforms 18:01:47 we move each platform separately 18:02:06 so we could move android builds to buster now, if it's ready 18:02:32 boklm, ok so I'll need to make some changes to the configs since I removed stretch 18:02:55 I'll just add it for buster. I'll open a ticket if there isn't one already 18:03:18 sisbell: why not taking the appraoch you meantioned first to download some random apktool from the internet? 18:03:53 Depends on when we need the issue 18:04:04 That's the shortest path 18:04:16 comment:26 that is 18:04:21 well, last week :) 18:04:51 we've tried a lot so far and have just one alpha left which is due in about two weeks or so 18:05:04 i think it might be worth implementing the shortest path now 18:05:05 If everyone is ok with that, I can get that out today. 18:05:12 and then build on top of that 18:05:19 like getting _hc involved 18:05:28 and then move to buster 18:05:47 Yeah that works, we just need to version that we are pulling from remote repo put into buster 18:06:06 ? 18:06:21 So we can take baby steps, first download ourselves, then have that version included in buster 18:06:22 comment:26 did not seem to involve moving to buster 18:06:28 ah, yes 18:06:31 exactly 18:06:40 because other work is still blocked on that 18:06:47 i don't know if we can get the same versoin in buster 18:06:49 like the gradle dependencies fix up 18:07:05 i assume as long as the version in buster is new enough, that shoudl work 18:07:10 which in turn blocks getting other tickets out of our (review) queue 18:09:03 okay, we'll look for that branch (early) this week, for reviewing 18:09:36 anything else for weekly updates? 18:09:43 sisbell: please address boklm's feedback and push a new branch 18:09:50 rebased against master 18:10:06 yes, I see his comment, so I'll make that change 18:11:42 okay, next up are discussion points 18:12:08 the only one this week is discussing some questions about migrating desktop to rapid release 18:12:56 these questions are coming from the OTF "pre-proposal" we submitted 18:13:01 (i forget what it was called) 18:13:22 concept note? 18:13:23 we're thinking about having a meeting later this week to go over the questions and decide on some answers 18:13:39 ah, that could be it 18:13:55 scope of work? :) 18:14:01 how does Thursday look for people? 18:14:04 :) 18:14:29 does after 1700 UTC work for most people? 18:14:46 or 1500-1600? 18:14:58 pospeselr: sisbell what's the earliest you'd be comfortable with meeting? 18:15:36 I can do 1500 UTC 18:15:39 I'm ok anytime 18:15:47 whatever works best for others 18:16:14 or even 1400 18:16:36 I'm CST at the moment 18:17:24 15UTC is best for me 18:17:31 okay, how's 1500 for everyone? 18:17:32 I have other meetings before and after 18:17:43 1500 works for me 18:17:43 wfm 18:17:44 works for me 18:17:45 works for me and mcs 18:17:52 Thursday right? 18:17:57 yes 18:18:20 acat: ^ 18:18:29 works for me too 18:19:01 okay, it sounds like we have a meeting 18:19:17 oh, mcs brade ^ 18:19:27 oh, you did say! 18:19:28 sorry 18:19:47 okay, anything else we should discuss this week? 18:19:53 <_hc> hello 18:20:05 o/ 18:20:06 _hc: hey 18:20:06 some Namecoin stuff on my end if you're interested 18:20:10 <_hc> reading the backlog 18:20:39 Jeremy_Rand_Talos: sure, if you have a quick summary 18:21:24 sysrqb, yeah, so the tl;dr is that I've been doing a bunch of refactoring/optimization work, as well as getting stream isolation to work properly. 18:21:38 <_hc> a backport of apktool 2.4.0 to buster should be easy 18:22:15 Hoping to have a tor-browser-build patch that'll be in a reviewable state within a month, maybe sooner if things go well 18:22:49 full list of things I've been doing in the last week is in the Etherpad for those who are curious 18:23:46 neat 18:24:37 thanks for the update 18:24:44 no problem 18:24:57 _hc: thanks. i don't know what version we'll need. 18:25:23 _hc: hopefully sisbell can figure that out 18:25:28 <_hc> 2.4.0 is the latest release, you need something from git? 18:25:29 it looks like 2.4.0 is the version we need according to the patch from https://trac.torproject.org/projects/tor/ticket/31564#comment:26 18:25:39 _hc: ah! 18:25:52 yes that's the one 18:26:03 okay, great 18:26:40 okay, we can discuss the details for this after the meeting 18:26:44 _hc: thanks 18:26:53 <_hc> you could probably just include the testing package directly in buster 18:27:10 <_hc> if you're not already using buster-backpots 18:27:32 <_hc> ok, let me know 18:27:43 it's in -backports? 18:28:02 <_hc> I can upload it there 18:28:07 ah, okay, yeah 18:28:15 sisbell: which package did you use in https://trac.torproject.org/projects/tor/ticket/31564#comment:44 ? 18:28:17 we can figure this out 18:28:58 okay, i think we're done with the meeting 18:29:03 thanks everyone! 18:29:16 bolkm: That was using the apktool pakcaged with buster 18:29:22 thanks 18:29:29 o/ 18:29:31 Its said 2.4.0 but the dependencies didn't match 18:29:31 #endmeeting