15:01:15 #startmeeting metrics team 15:01:15 Meeting started Thu Jan 23 15:01:15 2020 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:25 The pad is here: https://pad.riseup.net/p/tor-metricsteam-2020.1-keep 15:01:48 anything else for the agenda before we start? 15:02:35 okay, starting. 15:02:42 not from me 15:02:45 potential gsoc project (georg is interested in mentoring with somebody else): Tor weather (#26124) <-- pili is going to follow up on this to define scope of this gsoc project --gaba --> 15:03:09 Brin? 15:03:21 does zwiebelbot have character issues? 15:03:29 or is it my irssi? 15:03:32 worked for me 15:03:35 "a student that only triples my workload is a good student" 15:03:39 it did 15:03:50 it did work* 15:03:55 interesting... 15:04:08 so, regarding this gsoc project, 15:04:15 despite irl's concerns... ;) 15:04:22 irl: i'm guessing you are saying you do not want to mentor? :) 15:04:42 i mean, i'm happy to answer questions and review code 15:04:48 if this project would use onionoo as data backend, we could support the onionoo side of this. 15:05:07 yeah it would be good to not have this be a separate thing, it should fit with our existing tools 15:05:12 like help with the API, extend it (though not too much) in order to make weather work better. 15:05:19 yeah 15:05:29 karsten: i am not sure whether i am interested yet :) but, i guess it _could_ be a good project 15:05:34 it would require some new parts with a subscription database and emailer and all. 15:05:41 hi GeKo! 15:05:49 hihi! 15:06:01 (I'm in another meeting, will read backlog later :) ) 15:06:12 I'm more careful about mentoring the development of those new parts. 15:06:27 also because I'm not good at writing applications like that. 15:07:01 GeKo: if you would mentor those parts and we would mentor the data side with onionoo, that would work for me. 15:07:13 if you decide it will be a good project. 15:07:20 and if you find a good student for it. 15:08:05 Sounds good and important to specificy the project you all think is needed. I know pili is on it so I think we should wait for her to move forward with the project and we all give feedback and help her shape it. 15:08:08 okay, good to know 15:08:23 sounds good to me! 15:08:57 okay, moving on? 15:09:10 ok 15:09:16 ok 15:09:22 schedule next roadmap session 15:09:31 how about the week after next week? 15:09:38 ok 15:09:43 because we might learn more about what's needed next week. 15:09:48 we == irl 15:09:48 so far there is more work to do, mostly about the onionperf project. 15:10:12 i think onionperf work might be informed by my trip quite a bit 15:10:19 yes. 15:10:26 right 15:10:37 irl: but you are done on the 31st, right? 15:10:43 should we pick a date? 15:11:08 I'm afk from 31st to 3rd. 15:11:23 the project will be informed by the meetings next week but we already have a project that we shaped and presented to moss 15:11:32 if i'm taking days off because i was travelling/meeting, then i only work two days in week 6 15:11:43 unfortunately, I also have very little time until the 5th of February 15:11:45 i don't mind so much which days they are 15:11:53 and i'll probably end up only taking 1 day back 15:12:18 I say let's continue working on it independent and then we can sync again when you are all back 15:12:40 well, we could pick a date for our next roadmap session. 15:12:43 we will meet anyway on 6th feb 1500 for metrics meeting 15:12:56 In the pad I wrote some of the tasks I need you all to do. https://pad.riseup.net/p/0K2Q5uuN0CbjbOGxJQsL-keep 15:12:56 we could roadmap 7th feb 1500? 15:13:39 7th at 15 utc works for me. 15:13:50 gaba: and yes, we can do those tasks until then. 15:13:53 7th is a Friday. I will be traveling that day but let me check if I can meet in the morning 15:14:12 yes this works for me 15:15:09 we can also roadmap the week after if that's easier for you gaba 15:15:12 we don't want to rush it 15:15:35 * gaba is checking the calendar and looking for the flight... 15:16:06 yes, let's do the monday after 15:16:20 15 utc? 15:16:29 that's the 10th then. 15:16:34 yes 15:16:35 works for me 15:16:53 seems ok 15:17:02 great! 15:17:46 okay, moving on? 15:17:58 ok 15:18:21 Needs review tickets: https://trac.torproject.org/projects/tor/query?status=needs_review&component=%5EMetrics&col=id&col=summary&col=component&col=owner&col=type&col=priority&col=milestone&col=reviewer&order=priority 15:18:45 irl: should I set you as reviewer if I hope that you review something? 15:19:01 or would you rather assign yourself? 15:20:17 karsten: either is ok for me 15:20:25 okay. 15:20:32 my query catches either those without a reviewer or those where i'm set as reviewer 15:20:53 i do the ones where i'm a reviewer first so you could indicate priority by setting me as reviewer if you like 15:21:16 e.g. where you have data fresh and don't want to reprocess again 15:21:20 yeah. 15:21:25 not the case with these three. 15:22:04 do you think you can do these three before you leave? 15:22:09 i think so 15:22:27 and what about the bottom three? are these yours, too? 15:22:50 i've been braindumping the exitscanner into https://people.torproject.org/~irl/exitscan.html so i can pick that up again when i'm back, and then i'll shut off the aws stuff for that until i'm back too 15:22:55 and then i'll just do reviews 15:23:16 some of the onionperf ones have been reviewed and need changes 15:23:19 so i updated those in trac just now 15:23:54 wait, do we need to consider two lists? 15:24:04 trac + gitlab? 15:24:29 nothing is actively being worked on in gitlab right now 15:24:35 the onionperf stuff is in metrics/cloud component 15:24:41 ah. okay. 15:25:22 cool. anything else on tickets in need of review? 15:25:46 not from me 15:26:06 moving on to another ticket query then: 15:26:08 Defect tickets: https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_revision&status=new&status=reopened&type=defect&component=%5EMetrics&group=priority&col=id&col=summary&col=component&col=status&col=priority&col=changetime&desc=1&order=component 15:26:28 as I said last week I went through the list of defects we accumulated. 15:27:07 I tried to assign priority high to some of them. 15:27:26 this is tricky, because I don't want to manage our defects. I want to resolve them. ;) 15:27:50 right 15:28:14 so, one of the criteria I used was "can we close that soon, if only we look at it now?" 15:28:44 if anything else of the medium-prioritized tickets stands out as high priority, please change that. 15:29:10 but I assume you're not going to do much with these defects in the next two weeks anyway. 15:29:17 i think i have a long time to spend in an airport next week, i'll take a look through that query then 15:29:37 that sounds great! 15:29:51 if it's any relief, the list is a lot shorter than it was four weeks ago. 15:30:04 yay 15:30:28 okay, great! let's look again at this list at our next meeting. 15:30:45 moving on to roadmap? 15:30:55 ok 15:31:24 I already moved one card to done. #32747 15:31:50 and I just moved the graphs for mike to the review column. 15:31:59 which leaves fun with geoip databases... 15:33:39 ok that's tickets updated 15:33:55 #29624 and #29653 should be done in february, right? 15:33:59 i've moved onionoo hosts back to backlog for now, i've not made progress on that and we should do that once things have calmed down a bit 15:34:03 I will take them out of the icebox into the backlog 15:34:10 yes 15:34:23 oh wait, not new version of exit list format 15:34:39 and i guess also #29653 is done, it's not reusable 15:35:00 can we close it? 15:35:03 yes 15:35:40 are you going to do that, irl? 15:35:42 done 15:35:45 :) 15:35:46 ty 15:36:03 oh, speaking of tickets: #33010 15:36:13 I was just wondering if that's in the wrong component. 15:36:31 that's not what onionperf does 15:36:45 #33010 was proposed as a gsoc project also I think 15:36:47 it's in the Exit Scanner component right now. 15:37:01 it might be something for Ideas. 15:37:08 yeah, you could do it with exitmap 15:37:14 i think exitmap already has this plugin even 15:37:46 anyway. this just came to mind when talking about Exit Scanner tickets. 15:38:37 * phw surfaces and points people to https://github.com/NullHypothesis/exitmap/blob/master/src/modules/cloudflared.py 15:38:50 yeah i was sure i'd seen this 15:39:17 can you comment on the ticket, so that this doesn't get lost? 15:39:31 and should we move it to Ideas? 15:39:47 yes ideas is the right place i think 15:40:01 i can see a case for metrics running instances and publishing data on this sort of thing 15:40:40 right. 15:40:48 i do not see us having more mentors for this one as a gsoc project 15:41:10 it will be a busy year, one gsoc project to mentor will be enough :) 15:41:40 unless people in other teams can/want to do it 15:41:49 well, the process is that we write ideas, receive applications, and then decide which students we can accept and mentor, right? 15:41:57 right 15:42:04 having more ideas is useful. 15:42:06 do you think this one is a better project to mentor than then other one? 15:42:13 yes, that is right 15:42:20 more ideas is good :) 15:42:41 I didn't really read about that idea. I wouldn't be a good person to mentor this. 15:43:02 it also doesn't have to be a metrics person. 15:43:44 +1 to more ideas 15:43:45 more ideas does not have to mean more mentors 15:43:51 and they do give us more chances to be selected as long as the ideas are "exciting" ;) 15:44:01 right! 15:44:14 ok, sounds good 15:44:26 so, going back to the roadmap topic. 15:44:36 everything good with the in progress column? 15:44:59 yep 15:45:24 yes 15:45:28 alright, that was our last topic for today. 15:45:45 irl: if you need my help with anything next week, just let me know. 15:46:04 ok will do 15:46:23 no meeting next week, but the week after, right? 15:46:34 sounds good 15:46:40 irl: also if you want to send any question/comment/notes about the all hands to our signal group, that would be good 15:46:44 yes 15:46:58 yeah 15:47:15 cool! 15:47:42 thanks, everyone! have a good evening/day! o/ 15:47:47 thanks! o/ 15:47:58 #endmeeting