15:01:35 #startmeeting metrics team 15:01:35 Meeting started Thu Nov 21 15:01:35 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:02:02 What do we continue taking notes in? nc pad, riseup pad, other? 15:02:11 that's the first item on the agenda. 15:02:19 I'm ok with either. The pad in the nc.torproject is easier to track 15:02:29 the nc pad is ok 15:02:30 but we can move to pad.riseup.net 15:02:37 ok 15:02:40 having a single place would be good. 15:02:53 I'm fine with this pad, even though it has no author colors. 15:03:08 or can we somehow enable that? 15:03:27 * gaba briefly looking 15:04:43 i don't think it's possible 15:04:50 yes, i do not see it 15:04:53 okay. 15:05:24 I just added my name near the stuff I added to the agenda 15:05:47 yep. 15:05:52 next item? 15:06:03 yes 15:06:09 #25924 ? (gaba) 15:06:20 I found out that this has become a problem. 15:06:30 I'm currently working on this. 15:07:06 my goal is to tweak it and try hard not to rewrite major portions of it. in that case I'd say something on the ticket first. I'm still optimistic that it can be tweaked. 15:07:07 ok. I'm going to add it to the roadmap (checking that it was not there) 15:07:21 it's not there. we tried to get funding for it, but that didn't happen. 15:07:35 in fact, that's the reason for the ticket to exist, IIRC. 15:08:20 moving on? 15:08:30 yes 15:08:34 ok 15:08:37 ExitScanner status? (gaba) 15:09:22 we have an exit scanner, i got some details from tsa, i am working on a testing deployment on aws which i will then run for a bit and then ask for review 15:09:35 we don't have a dns server or integration with check.tpo yet 15:09:40 but one problem at a time 15:09:56 I'm ready to review code or results as they appear. 15:10:01 cool 15:10:06 sounds good! thanks irl 15:10:22 glad to see progress there! 15:10:28 should have a review ready on tuesday 15:10:33 well, a thing to review 15:10:40 sounds good! 15:11:22 next item? 15:11:25 ok 15:11:34 Do we have OONI data resolved? https://trac.torproject.org/projects/tor/ticket/32126 (gaba) 15:11:48 see my huge comment on that ticket. 15:11:56 from 5 weeks ago. 15:12:12 arturo responded 15:12:20 6 minutes ago 15:12:23 hah 15:12:27 (: 15:12:32 okay, I did not see that yet. 15:12:37 great! 15:12:48 so things are moving forward :) 15:12:51 will take a look after the meeting. 15:13:00 i did think it sounded odd about the replication because i was sure it was meant to sync, not load a new database every time 15:13:17 i vaguely remember doing this with ultimate debian database but i don't remember exactly how 15:14:31 do we even have a machine for keeping a db clone? 15:15:18 that's a question for tsa 15:15:33 right. 15:15:41 so far i'm working on the assumption that tsa will give me whatever i ask for as long as it's reasonable 15:15:46 maybe this is a bad assumption 15:16:03 i would assume so 15:16:14 irl: do you want to bring it to anarcat to check if it is possible? 15:16:26 or i can talk with him to follow up on that ticket 15:16:54 well, we would need to know what we want 15:17:04 ok, let's continue in the ticket then 15:17:05 in terms of cpu, disk space, network requirements, memory 15:17:06 yes, it's two problems to solve. 15:17:07 and after the meeting 15:17:09 yeah 15:17:20 ok. 15:17:38 * anarcat raises head 15:18:07 uh, sorry that i mentioned you 15:18:10 no probs 15:18:28 just saying i'm around to answer a specific question, but i lack context and don't have time to catchup with backlog :) 15:18:42 this is not a problem for this month 15:18:51 but expect a problem in the future 15:18:54 that you will have to fix 15:18:55 heh 15:18:59 ha 15:19:06 yes, we'll first figure out what we want and then reach out to you, okay? 15:19:17 challenges are good, right? 15:19:42 okay. moving on to the next challenge? 15:19:45 ok 15:19:57 Let's work on a new roadmap for the Scalability/OnionPerf project in January. (gaba) 15:20:10 are we going to start this work in january? 15:20:24 is this related to anti-censorship team? 15:20:36 also, what is "this work" here? 15:20:43 Scalability/OnionPerf 15:20:54 the thing we wrote a proposal for. AFAIU. 15:20:54 I would like us to start working in the project as soon as we can 15:20:54 irl: the usual ;) 15:21:05 aah ok i see 15:21:20 We are applying for funding and it will take some time but I think we should still start working on this as it is something we need. 15:21:24 what you both think? 15:21:29 sure! 15:21:39 on the assumption that the exit scanner is wrapped up, yes 15:21:40 I'm happy to start working on that, if it's something we can do. 15:22:17 if the exit scanner needs another week or two i think it is important to finish it properly so we really can not worry about it again for a while 15:22:17 the two might overlap for a bit. unless the exit scanner project keeps both of us busy. 15:22:25 totally agree with that. 15:22:36 agree on that yes 15:22:46 just saying, if you're still busy for a week or two in 2020, and I'm not, I could start with the onionperf work. 15:22:47 exit scanner needs to be finished 15:23:03 yeah sounds good 15:23:04 maybe we can have a voice meeting in mid December to discuss and build a roadmap for this project 15:23:14 sounds good to me. 15:23:19 when is mid-december? 15:23:57 first half of december? 15:24:06 if mid-december is too close to other events? 15:24:13 i am at a conference on the 6th, and my last working day will be the 18th 15:24:56 also the 2nd is a public holiday 15:25:15 we'll find a date. :) 15:25:39 ok 15:25:45 ok 15:26:06 could it be monday 16th? 15:26:16 yep. 15:26:25 or we could leave it for January 15:26:30 and start with this roadmap exercise 15:26:34 or that. 15:26:50 16th december is ok, but i wonder how much i can think about a new project then 15:27:06 january? 15:27:13 if we do it in january i can re-read the proposal and things over the break and be ready for an excellent roadmapping session 15:27:47 january 3rd 15:00 utc? 15:28:10 or 6th? 15:28:25 i am looking at the wrong year 15:28:30 I'm coming back on Jan 9th 15:28:47 so, 9th? 15:28:54 or 10th :) 15:29:01 10th 15:00 utc? 15:29:02 ok. 15:29:05 ok 15:29:07 woo 15:29:10 cool 15:29:25 great! 15:29:30 I'm going to add it to the 'metrics calendar' in nc.torproject :P . You may get an email about it 15:30:02 ok 15:30:09 okay. 15:30:18 next item? 15:30:23 ok 15:30:37 Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap 15:31:17 #32265 went into review and back out again into in progress, #32264 is still in progress 15:31:49 acute is still travelling but has been working on the cloudformation/ansible for onionperf 15:32:20 #32473 is still in progress, because I expect more results to evaluate next tuesday or wednesday. 15:32:30 ok cool 15:32:33 #25294 is what we discussed briefly earlier. 15:32:49 same with #32126. 15:33:05 hmm, not that one. 15:33:08 i don't think 25294 is right 15:33:28 #25924 15:33:52 that one. fixed in the roadmap. 15:34:18 fixing an exception in firefox.exe would take me more than a week... 15:34:31 heh 15:34:42 first challenge would be to find a test system. anyway. 15:34:55 I think the roadmap is fine. 15:35:12 yes, all up to date 15:35:28 regarding releases: nothing new this week. 15:35:47 we do have unreleased patches in master, but I don't think they're urgent. 15:36:25 btw, I did push a few fixes to the various masters. nothing important enough to create a ticket for and ask for a review, though. 15:36:34 except for the collector config thing. 15:36:45 which isn't urgent, either. 15:37:05 ok 15:37:25 anything else for today? 15:37:34 not from me 15:37:43 i can review #32554 just now 15:37:52 sure! 15:38:13 before we close, what about next week? 15:38:43 I hear it's a holiday in the U.S. 15:38:48 i am not in the US 15:38:49 oh yes 15:38:56 I will not be working on Thrusday 15:39:01 but I will be in Europe next week :P 15:39:10 should we move the meeting to wednesday? 15:39:17 we could do that 15:39:17 heh, nice! 15:39:28 that could work although I will be on a panel on Wednesday and I need to look at what time 15:39:52 or friday? 15:40:00 Friday is much better for me if you all can make it 15:40:11 friday is also a US holiday 15:40:12 if that works, holiday-wise, fine with me. 15:40:21 yes but I can meet Friday 15:40:39 then friday 15 utc? 15:40:42 ok friday is ok 15:40:42 ok 15:40:53 great! 15:41:16 that's all for today. thanks, and bye! o/ 15:41:25 bye! 15:41:32 o/ 15:42:06 karsten: you need to stop logging, right? 15:42:58 aiiii 15:42:59 #endmeeting