15:00:33 #startmeeting metrics team 15:00:33 Meeting started Thu Oct 31 15:00:33 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:49 https://storm.torproject.org/shared/5h1Goax5eNusxjXJ_Ty5Wl7hFR1uqCReUiN8xdlBG8T <- agenda pad as usual 15:01:23 please add topics if anything's still missing. 15:02:48 all done 15:03:06 I don't have more topics, either. 15:03:07 nothing from me 15:03:55 gaba: ? 15:04:32 okay, let's start and append anything else that comes up to the end. 15:04:36 Onionoo deployments (irl) 15:04:41 did you get my mail about this? 15:04:45 yes! 15:04:46 yes 15:04:53 nothing else from me :) 15:04:58 and I totally forgot the time suggestion there. 15:05:03 sorry for that! 15:05:10 that's ok, i did reviews instead 15:05:32 can we do that tomorrow morning? 15:05:51 i won't be working tomorrow, but you can do the AWS version of it and let me know if the instructions break down? 15:06:46 or maybe I'll do that on monday then. I would be around for a meeting but was otherwise planning to take it easy after all that index.json hacking. 15:06:57 monday is fine too 15:07:06 okay, then I'll plan to do this on monday. 15:07:20 i'll be around on irc most of monday if you find yourself stuck 15:07:27 sounds good! 15:07:43 that's all for this topic (: 15:07:48 cool! 15:08:02 Exit scanner (gaba) 15:08:05 ok 15:08:11 how are we doing with it? 15:08:59 there is an architecture, an implementation plan, some very rough code exists and i found a flaw in the control port protocol #32190 15:09:45 next steps? 15:10:10 #32262 15:10:28 this is the foundation of the "scanner" portion of it 15:11:56 would you mind writing a short summary like this on the pad? 15:12:11 just so that we don't forget until next week. ;) 15:12:24 i'm going to be adding exitscanner keyword to the tickets in trac to keep track of the ones that needs to be done for this to be complete. 15:12:31 ok 15:12:44 they are all child tickets of #29654 15:13:38 should we have #32190 in the roadmap after that one? 15:14:09 i am hoping that that will be done by arlo(?) 15:14:22 yeah arlo 15:14:35 no wait 15:14:55 that's core tor, #32186 is the bug that i filed that i think arlo will hopefully do 15:15:02 #32190 we will just work around 15:15:06 it's not that big a deal 15:15:09 just annoying 15:15:25 ok 15:16:10 are you block by #32186 in any of this? 15:16:16 not yet 15:16:19 ok 15:16:37 i will be later but that's when we start deploying new hosts and installing the new stuff 15:17:11 and that may be in december, right? 15:17:28 are we on track for having this then? is there anything we can do to help? 15:17:30 i think it is unlikely we will deploy in december, but hopefully we would have something to deploy 15:18:18 there is not really any way to make this go faster 15:18:22 ok 15:19:40 done with exit scanner for me :) 15:19:48 cool (: 15:20:02 great! 15:20:12 moving on: 15:20:15 Updating the wiki page for the metrics team https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam 15:20:33 i think this topic and the next topic are the same 15:20:42 ah, maybe. 15:20:45 Release announcements, cf. #32142 (karsten) 15:20:52 yes, similar 15:21:15 the wiki will be moved to gitlab and that could be an oportunity to update it 15:21:20 heh 15:21:27 when is that going to happen? 15:21:35 hopefully december 15:21:40 who is going to do that? 15:21:56 there are a few volunteers for this like me and ahf and pili 15:22:11 ahf is working on the migration 15:22:26 we can easily throw out a bunch of stuff that is outdated. 15:22:33 but do we want to keep old roadmaps somewhere? 15:22:55 subpages? 15:23:06 yes, i think it would be good to keep it as history 15:23:53 okay. I can go through the wiki page and remove or move stuff. 15:23:59 i can take it into other page for old_roadmaps 15:24:06 ah, thanks karsten 15:24:21 if we're going to move to the gitlab wiki it will break metricstimeline 15:24:40 uhh, I wonder when I last updated that on metrics.tpo... 15:24:49 but yes, that's a good point. 15:24:54 is there some gitlab way for people to contribute to it better? 15:25:27 irl: what do you mean? 15:25:41 we have this page with a table https://trac.torproject.org/projects/tor/wiki/doc/MetricsTimeline 15:25:55 is there some way for people to contribute to this table in a way that is more robust than editing a wiki page? 15:26:24 ahh, I see. I would have to investigate a little 15:26:50 maybe via issues in a project and then we render them in the wiki 15:26:53 i would have to check 15:27:17 or just a file that ppl send PRs to 15:27:20 it might be that dcf is the only person that edits it 15:27:26 in any case we should update events on metrics.tpo one last time before the move to gitlab. 15:27:44 ok 15:28:12 yes, dcf, phw and me are the only ones to recently edit it 15:28:55 so, release announcements. 15:29:49 we don't have the capacity to be doing full release engineering with press releases 15:29:52 I wonder when we last made them. 15:30:03 we mostly do releases for ourselves 15:30:29 maybe we could mention new releases in the weekly meeting summary? 15:30:44 there's always a ticket for a new release. 15:30:49 sounds good 15:30:53 we could link to those tickets for new releases. 15:30:55 yes, mention them somewhere would be fine 15:31:07 weekly meetings summary is ok 15:31:14 the wiki can just link to the relevant folder on dist, not to a version 15:31:19 that way it's never out of date (: 15:31:33 yep 15:32:22 https://trac.torproject.org/projects/tor/query?component=%5EMetrics&summary=%5ERelease&max=10&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=changetime&desc=1&order=changetime 15:32:42 we could include the "Release*" tickets on the wiki page, too. 15:33:17 ahh, I see. yes 15:33:44 is that sufficient? dist.tpo link + this ticket list on the wiki page? 15:34:04 we could also add something to the weekly mail, but that's yet one more thing to keep in mind. 15:34:56 Let's try to include it in the weekly mail if possible. 15:35:00 we should have checklists for releases so we don't have to keep things in mind 15:35:16 we can add release checklists at https://help.torproject.org/metrics/ops/onionoo-ops/ and make other pages there for other services 15:35:47 (this is a git repo anyone can commit to) 15:35:58 (if you have a git-rw account that is) 15:36:08 https://gitweb.torproject.org/project/help/wiki.git 15:36:56 gaba, you're writing the weekly mails. would you be checking release tickets before writing them, or how would and when you want to learn about new releases? 15:37:07 how and when would* 15:37:09 karsten: yes, I can check release tickets 15:37:22 okay, cool! 15:37:25 I will try to check them before the meeting and add them to the summary 15:38:10 irl: I'll write down steps for releasing metrics-lib + collector for the index.json update. 15:38:27 and then we can see whether they're good to go on that ops page. 15:38:30 ok cool 15:38:39 ok 15:40:04 I need to go now. The last item is the update of the roadmap 15:40:15 we should move the exitscanner tickets up in the backlog 15:40:20 okay, I'm done writing the summary. 15:41:12 one quick question about the roadmap: wouldn't it make more sense to have icebox on the left, then backlog, then in progress, then on review, and then done? 15:41:22 just so that cards flow from left to right? 15:41:43 that would seem logical but i've never seen it done that way 15:41:58 ah, do we follow a convention here? 15:42:15 yes, we have it that way in other teams 15:42:22 i'm just going on what i've seen other projects do 15:42:23 i don't really mind 15:42:39 better, thanks. :) 15:42:51 i like it better with icebox on the left :) 15:43:23 and now i really need to step out... I will read the backlog later and send the logs to the mailing list 15:43:32 bye! 15:44:19 for roadmap updates, i've moved #31659 to "on review" for you to look at on monday karsten 15:44:23 otherwise no changes for me 15:44:24 I'll add #31071 to in progress, too. 15:44:32 sounds good! 15:45:08 after spending more time on #31204 than anticipated, I hope that my three items in progress or on review will be done next week. 15:45:32 not adding more at this time. 15:45:40 cool 15:45:51 I've moved an onionperf automation task for irl to review, but it has no ticket number 15:45:51 alright! 15:46:02 yes, i'll make some ticket numbers for those tasks 15:46:08 great! 15:46:13 they've been in the roadmap since last week but i didn't make tickets yet 15:46:28 thanks! 15:47:08 that's all from me 15:47:24 are we all done? 15:47:25 okay, I think we're out of topics! 15:47:27 yes. 15:47:38 excellent 15:47:43 talk to you next week, same time! 15:47:54 bye! o/ 15:47:54 cool, bye! 15:47:57 bye! 15:48:00 #endmeeting