18:31:49 #startmeeting Tor Browser Team Meeting 10 February 2020 18:31:49 Meeting started Mon Feb 10 18:31:49 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:31:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:32:01 hi 18:32:12 hi! 18:32:14 hi 18:32:30 Hello! 18:32:41 hi 18:32:41 hi 18:33:11 hi 18:33:40 hi 18:36:49 * sysrqb is amazed by tjr's color on the pad 18:36:59 me too! 18:37:04 ikr 18:37:19 it's not even a selectable option 18:37:48 haha wow 18:38:12 white-on-pink. pretty special. 18:39:48 okay, let's get started 18:39:55 hello everyone 18:40:49 i want to begin by checking-in with all of you on the initial tasks for starting the migration 18:41:05 does anyone have comments or concerns about what i asked you to do? 18:41:24 or comments/concerns about the overall process? 18:42:20 okay, i'll assume silence means no, but if that ever changes please le me know (either publicl or privately) 18:42:51 tjr: thanks for working on 1599226 18:42:56 that's exciting 18:43:03 wrt to patches rebasing, does that mean both desktop and mobile ones? 18:43:18 or will the mobile ones not be needed for Fenix? 18:43:32 acat: some of the mobile patches will be needed 18:43:43 the patches affecting gecko 18:43:53 we don't need any of the UI patches 18:44:26 ok 18:44:31 you'll run into conflicts during the rebasing on patches that affected the UI and/or patches that were fennec-specific 18:44:43 does that mean we do not need anything under mobile/android ? 18:44:46 because mozilla deleted a lot of the fennec-specific code from m-c already 18:44:55 mcs: unfortunately no 18:45:02 that would be too easy :) 18:45:15 all of the java and kotlin geckoview implementation is still under mobile/android 18:45:53 but fennec was (mostly) implemented mobile/android/java and that is gone 18:46:06 got it; thanks 18:46:22 err, sorry, mobile/android/base 18:46:31 but geckoview is under mobile/android/geckoview :) 18:47:11 acat: so, you'll have some trouble in that area, but please feel free to ping me whenever you have trouble resolving any conflicts 18:47:32 good, thanks 18:48:53 * tjr has to run, but will be back later today 18:49:05 sisbell: we need to finish integrating tor for android into tor-browser-build 18:49:26 tjr: o/ 18:49:40 Yes, I have that code done, I'll set up a branch for review today 18:50:01 With static compiles for compression libraries and openssl, everything is looking very good 18:50:07 great! 18:50:14 that is very exciting 18:50:34 Yes, its cool 18:51:13 When we get it stabilized, we can add a tor package step and push to maven central 18:51:24 okay, let's chat about other items for this week after the meeting 18:51:32 right 18:52:30 okay. next topic. our gitlab instance is nearly ready for production use 18:53:24 but before that happens each team was asked to find a volunteer service admin for it 18:53:41 similar to the request for gitweb support a few months ago 18:54:15 would any of you ike to help support gitlab admining? 18:54:28 I can do that if there is no other volunteer 18:54:28 I could do that 18:54:30 as far as i know, it shouldn't be very time consuming 18:54:44 oh, two! :) 18:54:58 i tihnk gaba will have more details about what this will involve 18:55:27 okay, pospeselr can i put you in touch with gaba and you can decide if this is a thing you want to do? 18:55:35 sounds like a plan 18:55:41 great, thanks! 18:55:42 this thing replacing our gitwebs? 18:55:50 and thanks boklm for volunteering, too 18:55:58 pospeselr: i think not entirely 18:56:25 as in, i assume our "official" repos will remain on git/gitweb.tpo 18:56:34 at least for the foreseeable future 18:56:49 but you can create all of the personal repos you'd like on gitlab, afaik 18:57:04 (within some reasonable limits) 18:57:16 nice nice 18:57:38 when is trac -> gitlab going to happen (migration)? 18:57:42 but we can think about moving code review onto the gitlab instance, and i assume trac... 18:57:49 yes, that ^ 18:57:59 i have no idea about that time line 18:58:13 i can guess sometime this year, but i don't really know 18:58:47 maybe our new gitlab admin will ask gaba and let us know ;) 18:58:56 sounds like a plan :) 18:59:54 it looks like pili wants to remind everyone about updating points and tickets 18:59:59 yup 19:00:10 did you also want to remind people about timesheets? 19:00:14 I lost connection temporarily also, but I think i have all backlog 19:00:28 ah yes, please make sure you have all filled out a timesheet every week 19:00:45 and please submit all of the january ones now 19:02:30 thanks 19:03:17 pospeselr: we're tinking about delaying work on the per-site security settings until after the ESR->Release migration 19:03:34 do you think that's a reasonable thing to do 19:03:47 given the need to balance other priorities? 19:03:56 *thinking 19:04:04 given the need to balance, and that we're dependant on no-script changes i think that makes sense 19:04:24 great. that was my read on it, too 19:05:18 i had a conversation with asn earlier about some S27 work i may ask you to pick up for handling TLS certificates for onion serivces 19:05:27 but we can talk about that outside of the meeting 19:05:33 ok ok 19:05:38 and we'll be discussing it at the s27 meeting tomororw 19:06:27 TLS certs for onion services? Is there a Trac ticket where I could look at that? 19:06:39 boklm: do you think the timeframe for setting up the rebasing and testsuite are okay? 19:06:50 #30025 this is the parent Jeremy_Rand_Talos 19:06:57 you may find interesting childs there 19:07:01 boklm: end of this month and mid-march? (i think I asked) 19:07:12 thanks antonela 19:07:42 pospeselr: does the S27 meeting time work for you? 19:08:07 it's on at 15UTC... 19:08:23 sysrqb: yes 19:08:43 boklm: great. thanks 19:08:44 pili: yeah that works for me 19:08:52 great, thank you 19:08:57 sorry missed last week, was on a plane :) 19:09:16 (missed my flight on Monday and had to spend an extra day in Iceland >:[ ) 19:09:23 oh no 19:09:33 oh si :) 19:09:35 boklm: i assume the toolchain will be a little tricky, as well 19:09:46 yeah it was pretty awful wouldn't recommend it ;) 19:09:46 lol 19:09:50 boklm: but I'll help you with that as much as i can 19:09:55 haha 19:10:02 pospeselr: too many hours in the spa? 19:10:11 sysrqb: yes, I'm not sure how much work the toolchain update will be 19:10:13 * mcs wants to get stuck in Iceland someday 19:10:19 (for a little while) 19:10:22 :) 19:10:31 :) 19:10:46 boklm: yeah, we'll see :/ 19:11:25 okay, the last topic 19:11:47 today pili, mcs, brade, and i triaged tickets tagged for this month 19:12:03 and we moved some of them to June, and some to March or April 19:12:29 based on how important they seemed compared with sponsored work and the migration 19:12:45 if you think we moved a ticket which should have a higer priority 19:12:53 please let one of us know 19:13:06 (in particular, please let me know :) ) 19:14:07 our current priorities are (some) s9 work like the nightly updater, s27, upcoming s30 work, and the migration 19:14:35 if there is a small ticket that won't take you much time, then you can pick that up when you have some free time 19:15:09 but other than that i'd really like us to concentrate on these critical pieces of work for the next few months 19:16:12 and then we can get back to fixing all the other issues like letterboxing, per-site settings, etc. 19:16:56 let me know if you think this'll be an issue (either now or in the future) 19:17:11 i think that's all i had for this meeting 19:17:23 any last thoughts/comments/suggestions? 19:18:31 * sysrqb assume no one is writing... 19:18:46 thanks everyone! 19:18:49 #endmeeting