15:00:02 #startmeeting Tor Browser Weekly Meeting 2022-04-11 15:00:02 Meeting started Mon Apr 11 15:00:02 2022 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:24 usual stuffs please, update your boards, fill in the discussion points, complete todo list, etc 15:01:29 o/ 15:02:00 hello hello 15:02:11 Hi! 15:08:25 * sysrqb lurks 15:09:11 ok everyone 15:09:47 so last week i noticed we were basically hogging the entire #tor-dev channel with tor browser dev chat 15:10:14 which is great and all, but i do worry that when we do that we are kind of taking over the space, and preventing everyone else from have any sort of conversation 15:10:30 so i made a #tor-browser-dev channel (which I think y'all are already mostly in) 15:10:43 for when we need to go hard on tor-browser nonsense 15:11:02 ok second up 15:11:06 tor-browser-android 15:11:15 might be worth announcing that one if not done so already 15:11:16 wow what a nightmare 15:11:26 (in case it's meant to be a public channel anyway) 15:11:48 yeah i mean, it's not private but i guess we can also announce on the tor-dev list 15:11:49 richard, so, when I want to ask a question about Tor Browser dev, is the intent that I should use the new channel, or am I expected to use some heuristic to decide which channel to use (e.g. activity level in #tor-dev)? 15:12:41 heh, so mostly I think we should keep the majority of our coms in #tor-dev, and only move over once it's become clear no-one else in #tor-dev can have a conversation over us 15:13:03 richard: or tbb-dev, dunno 15:13:09 but if you need to ping us doing so in the #tor-browser-dev channel may also be useful since less likely to be drowne din other chat 15:13:24 but some kind of notification for potentially interested folks might be good 15:13:48 like i said, it's mostly there so other people can use #tor-dev when we need to have in-depth tor-browser conversations 15:13:57 richard, ok 15:14:18 ok second up, tor-browser-android 15:14:21 hot take: i would prefer to talk in a room where there wasn't constant crosstalk as a general rule. (perhaps i am an outlier tho) 15:14:34 aguestuer: yeah same :) 15:14:45 mentioning it on tbb-dev sounds like a good idea 15:15:12 (ie: i would prefer to default to using the smaller room always) 15:15:30 (and if people are interested in that topic they can come there... i know this can lead to room proliferation) 15:15:43 I'm sure we''ll converge to some usage that makes sense for our workflows 15:15:53 cool! please go ahead 15:16:18 Anyway, long term it's becoming clear having one person solely responsible for tor-browser android releases is a bad plan for the long-term viability of tor-browser-android being a thing 15:17:14 +1 15:17:17 So to that end we're going to be doing *something* to lighten the load there 15:17:18 +1 15:17:24 :) 15:17:45 tentatively the plan is to do some sort of periodic load balancing, by having the current tor-browser-android rebaser/auditer/etc be a rotating position 15:18:17 between at the very PieroV, aguestuser and myself 15:18:34 "the very PieroV" is an amazing handle 15:18:51 I promise I'm a native English speaker 15:18:53 and not a cat 15:18:56 as if "V" was the name and "piero" is an adjective 15:18:56 :) 15:19:10 ;) 15:19:13 (an adjective denoting awesomeness) 15:19:26 richard: if you want to we can rotate also rebasing of Tor Browser 15:19:39 (I mean Tor Browser desktop) 15:19:44 PieroV: yeah I think that will def be necessary on months where it's my turn :) 15:20:12 fortunately Tor-Browser desktop *just works* for the most part 15:20:12 ;) 15:20:16 until it doesn't 15:20:17 right now TBA consists of at least 3 rebases 15:21:08 and last times we sorta split them 15:21:22 So PieroV in the short term, tor-browser-android should be considered lower priority than any outstanding TB tickets w/ regards to s96 work 15:22:07 richard: okay, I think I'm going to be done with the latest donuts' requests soon :) 15:22:19 but for aguestuser's sanity I'd like you to take the lead on TBA 99 once that's complete 15:22:35 I already have a branch that could be almost entirely merged 15:22:57 I'd say that I could take it tomorrow my afternoon/on Wednesday 15:22:58 just a word of warning: there will probably be constant donuts requests up until the next alpha, but they'll be moderated by how frequently i can stop doing other things and test/create tickets :) 15:23:20 (thank you for everything so far!) 15:24:36 donuts: np, if it's just small things I can do them in not a long time, and I tend to parallelize (Android takes a long time... for everything!) 15:24:59 ha got it 15:25:36 aguestuser: take a break from android build fixing for awhile until we have a concrete plan of who's doing what and when; take some time off or go work on something you want to work on but can't because of build problems, whatever makes your heart sing 15:25:47 :) 15:25:51 +1 15:25:58 thanks. will do. :) 15:26:19 appreciate it. <3 15:26:27 ok 15:26:33 (occasionally there are android releases without major problems to fix. or a least, it has already happened in the past) 15:27:02 something to look forward to :) 15:27:03 ok, PieroV 15:27:09 tell me some good news about docs 15:27:28 I've published a page I had started to work on for a long time! 15:27:39 https://gitlab.torproject.org/tpo/applications/team/-/wikis/Development-Information/Codebases 15:28:01 And then I think we should start writing the discoveries me and aguestuser did for the problems we had 15:28:12 also the small things, like the fat .aar procedure, that seems obscure at least 15:28:23 yes! 15:28:35 and stuff about how to build from source when/if needed 15:29:22 also as a reaction of the docs discussions that all the Tor teams had 15:31:00 I love it 15:31:41 speaking of docs (or at least docs adjacent topis), I'm *really* loving gitlab issue templates for those repetitive tasks 15:32:10 I've found the workflow of just having a checklist to go thorugh w/ each tor-browser rebase very helpful, and I'm in the middle of the same for network audits 15:32:23 so I would encourage y'all to push your own templates where appropriate 15:32:34 nice! 15:33:20 ok, any other things to discuss this meeting? 15:33:29 quick state of the releases? 15:33:37 ah yes 15:33:54 (and update the pad if needed :)) 15:34:39 11.0.10 came out last week, and 11.5a9 is built and my task for this week is sign and upload(?) 15:34:49 11.0.10 has been built, but isn't on dist 15:35:39 oh, never mind 15:35:53 :) 15:35:58 it's me not thinking that for a computer .10 < .8 15:36:28 I'd love that all lists used natsort 15:36:29 boklm, sysrqb: first time going through this process so I'm sure I'll run into some problems at some point to expect IRC pings from me :p 15:36:53 PieroV: and I'd love if everything had leading 0s :D 15:37:09 richard: do you have all passwords and things needed to do it? 15:37:27 I have no idea, we'll find out :) 15:37:41 ok :) 15:37:50 my ssh key has allegedy been added where needed, and I have a big encrypted doc with instructions from sysrqb 15:38:14 but this is why I'm starting with an alpha release that isn't important 15:38:17 richard: let's chat when you're ready to go through it :) 15:38:26 well, important isn't the right word but you know what I mean 15:38:39 alright that's all I have 15:38:40 yes, that is less urgent than a stable 15:38:56 yes exactly :) 15:39:51 does anyone else have additional topics? 15:39:59 * PieroV doesn't 15:40:25 alright see you all on IRC 15:40:27 #endmeeting