14:58:44 #startmeeting metrics team meeting 14:58:44 Meeting started Thu Jun 18 14:58:44 2020 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:58:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:58:46 hi dennis_jackson! 14:58:56 https://pad.riseup.net/p/tor-metricsteam-2020.1-keep <- pad 14:59:02 hi everyone! 14:59:34 hi acute! 15:00:07 please add topics to the agenda. 15:01:11 hi! 15:01:16 hi gaba! 15:01:45 at some point we'll have to rename this meeting from metrics team meeting to onionperf project meeting. 15:02:01 but I guess it's just a name. 15:02:26 anyone thinking about agenda topics, or should we start? 15:02:31 nothing to add here 15:03:16 okay! 15:03:23 let's start with: 15:03:24 op-??3 instances 15:03:30 they're now up and running. 15:03:41 https://metrics.torproject.org/torperf.html already has the new instances. 15:04:03 I clicked through the various graphs and didn't find anything that stands out in comparison to the op-??2 instances. 15:04:18 Cool! Nice to know they are consistent 15:04:34 excellent news 15:04:37 if anybody finds something that's different, please let me know. 15:04:58 otherwise I'll shut down the op-??2 instances once there's 7 days overlap or so. 15:05:17 I think there's a slight change in how circuit timeouts are recorded 15:05:18 (I could wait longer, if there's a reason.) 15:05:32 Since there are no true 5kb / 1Mb requests anymore 15:06:03 ah. 15:06:29 you refer to the metrics website graph that doesn't have any dots for 50 KiB and 1 MiB from the new instances? 15:06:43 should I change the default option to 5 MiB for that graph? 15:06:56 I think that would make sense 15:06:59 which would also affect the other graphs, though. 15:07:16 still, we could change that. 15:07:21 it's just a default. 15:07:55 Alternatively, could try to redefine timeout by % complete at time of timeout? 15:08:21 And hope to see the same distribution for timeouts after 50 KB. Unlikely though and probably brittle 15:08:50 ah. hmmm. 15:08:56 maybe. 15:09:35 I'll look into that. 15:09:39 good suggestions! 15:09:55 :) 15:10:13 cool! 15:10:20 anything else on the new instances topic? 15:10:54 if not, let's move on. 15:10:59 GitLab migration 15:11:23 is everyone familiar with the new gitlab presence of onionperf? 15:11:32 with issues and boards and so on? 15:11:56 https://gitlab.torproject.org/tpo/metrics/onionperf 15:12:18 yes, it's quite a change :) 15:12:23 it is! 15:12:42 I'm glad that onionperf is a small project by now, with many tickets already out of the way. 15:13:14 yes 15:13:20 I am super happy, I think it is much friendlier for new people now 15:13:26 there are some ticket that still need to go there but I will do it later 15:13:29 yes 15:14:04 gaba: speaking of, we talked about having code in gitlab. 15:14:29 is it possible to mirror the code in gitlab and still keep the master in gitolite? 15:14:42 yes 15:14:45 that is possible 15:14:45 just thinking that it would be even friendlier to new people to have the code here. 15:15:06 karsten: agreed, I was going to suggest the same thing 15:15:15 karsten: can you create a ticket in https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues about the code that you want or are going to mirror? 15:15:38 any reasons not to do this? 15:15:44 otherwise I'll open a ticket. 15:16:22 I guess we could try it, and if it turns out to be a bad idea, take it out in four weeks. 15:17:11 okay, will open a ticket. 15:17:27 notifications: 15:17:34 are there any question about those? 15:17:38 questions* 15:17:45 do they work for everyone? 15:18:05 I also moved my onionperf dev repository to our gitlab from github 15:18:20 oh? how? where? 15:19:08 this is just my copy where I push new code for review 15:19:32 okay. is there a way to find it? 15:19:36 or is it hidden? 15:19:42 in the past, we used github 15:19:49 https://gitlab.torproject.org/acute/onionperf 15:20:55 just to highlight you can create projects in gitlab and have code there if needed 15:20:56 nice! 15:21:04 I like keeping things in one place 15:21:08 yes, looks good. 15:21:53 okay, great! anything else to talk about regarding gitlab? 15:22:14 one quick question - I noticed you used the /spend command to add points 15:22:18 yes. 15:22:45 we have /spend and /estimate 15:22:50 please let's use estimate too :) 15:23:17 this is cool, I was wondering if there are more useful commands like this 15:23:29 or if we have some documentation for them 15:23:40 https://gitlab.torproject.org/help/user/project/quick_actions 15:23:50 a few. :) 15:24:00 wow, thank you! 15:24:24 and no, I have no idea about 98% of them. 15:24:42 we'll all learn how to use this tool, some day. 15:25:03 okay, moving on? 15:25:47 One small thing 15:25:50 yes? 15:25:59 I don't seem to be able to enable notifications for some of the metrics projects 15:26:05 E.g. https://gitlab.torproject.org/tpo/metrics/analysis 15:26:25 "Notifications have been disabled by the project or group owner" 15:26:31 dennis_jackson: what is your user in gitlab? 15:26:40 But I can enable notifications on the Onionperf project 15:26:49 for some reasons notifications were disabled by default. 15:26:49 @djackson 15:27:01 I enabled them for onionperf and maybe a few more. 15:27:04 oh yes. notifications got back yesterday i think 15:27:30 ah okay 15:27:40 gaba: where did I do that? 15:27:46 but yes. I will add you as a member of group metrics 15:27:48 as in: where would I look now? 15:27:57 karsten: notifications? or members? 15:27:57 thanks gaba! 15:27:58 is it a member only thing? 15:28:05 notifications. 15:28:07 not sure 15:28:15 anarcat enabled notifications 15:28:21 they were off while we do the migration 15:29:40 dennis_jackson: try again? 15:29:48 dennis_jackson: notification in analysis. 15:29:58 It works now! Thanks! 15:30:00 this seems to now work for me also 15:30:27 it was disabled, overriding the group-level permission. 15:30:38 it should be enabled for all metrics things. notifications are good. 15:30:48 if you see something like this with other projects, let me know. 15:31:06 okay. 15:31:10 moving on: 15:31:15 Adding documentation ticket (#40001) to current roadmap 15:31:30 I'm thinking about moving this to the current (june) roadmap. 15:31:38 is that okay? 15:31:50 hi all, sorry for being late. had another meeting 15:31:53 or should I just work on it while it's in backlog? 15:31:56 hi phw! 15:32:01 hi phw! 15:32:18 phw: https://pad.riseup.net/p/tor-metricsteam-2020.1-keep <- pad 15:32:42 gaba: I guess that's a more general question to you. 15:33:05 seems ok to me 15:33:06 yes 15:33:16 okay. 15:34:01 I just think that I'm currently in the mood of documenting something, and I should really use that momentum. ;) 15:34:17 moving on: 15:34:18 Reviews 15:34:52 I moved #33399 to needs_review. 15:35:43 and I think I'm doing reviews the old-trac-way, not the new-gitlab-way. 15:35:52 should I do it differently? 15:36:30 for now we are trying to figure out how to mark reviews. The proposal is to have the needs_rview label and have it that way (you did it right) 15:36:40 the person taking this review will add a comment saying that they are taking that review 15:36:45 ah, okay. 15:37:26 no need to make a decision now who's going to review this. 15:37:42 but now it's a bit clearer how to find tickets in need of review, I think. 15:38:14 moving on: 15:38:19 Any blockers, anyone? 15:38:38 can we help with anything? 15:39:19 no blockers at the moment 15:39:25 same 15:39:44 okay, great! 15:40:16 I think that's everything for today then. 15:40:37 thanks, everyone! talk to you next week same time. :) bye! o/ 15:40:46 bye! o/ 15:40:47 o/ 15:40:49 o/ take care 15:40:59 #endmeeting