15:03:45 #startmeeting metrics team 15:03:45 Meeting started Thu May 16 15:03:45 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:03:54 anything else for the agenda? 15:04:14 not from me 15:04:26 not from me 15:04:46 great! 15:04:49 - bandwidth files update (karsten) 15:05:01 so, collector is archiving bandwidth files now! 15:05:13 woo 15:05:34 there's one known bug remaining that affects syncing between collector instances. there's a patch on the ticket. 15:05:46 the other remaining part is to do something with tom's archive. 15:05:52 i'm hoping to deploy that on the test box on monday 15:06:27 for tom's archive, will the tarballs script do the right thing if we just run them all through collector? 15:06:35 not automatically, no. 15:06:59 basically, we'd do those tarballs manually. 15:07:08 which should be fine. 15:07:11 we need to add type annotations 15:07:12 we're only doing it once. 15:07:29 right, so my idea was to make sure the Local mode works with bandwidth files, 15:07:37 this might actually be a thing to use bushel for, because it has a "collector document" concept which is an encapsulation of a descriptor 15:07:40 download them all from tom's server, and make tarballs out of them. 15:07:41 this would be a good test case 15:08:15 ah, it's a good test case for local mode too 15:08:44 right. how about I try that out, and if it turns out to be more work than I think (for whatever reason) we try bushel? 15:08:48 and then you're going to make the tarballs by matching with a glob? 15:09:07 hm? 15:09:38 the date is in the filename, so just YYYY-MM-* would work for putting things into monthly tarballs 15:09:45 with two for loops if you wanted it more automated 15:10:14 my current plans for tarballs is to hack create-tarballs.sh a bit. 15:10:23 by making tarballs for more than just 2 months. 15:10:43 collector would first make sure that files are in the right subdirectory. 15:11:08 ah, yes, i forgot they are in different directories 15:11:15 that sounds like an ok plan 15:12:02 great! 15:12:15 after these two things, we should be done with bandwidth files, right? 15:12:20 or did we want to do more? 15:12:38 i think we would be done with them for now, until some funded work comes along relating to them 15:12:45 yes, sounds good. 15:12:55 moving on: 15:12:59 - OnionPerf update (karsten) 15:13:16 I saw ticket updates before/during my previous meeting. 15:13:33 I didn't have the chance to look, but this is something I'm planning to do next. 15:13:46 would be great to add these graphs soon. 15:14:07 question: tor version update? 15:14:19 also, available disk space? 15:14:38 these haven't been looked at yet 15:14:53 ok. do you have an idea when they might fit in? 15:15:09 tuesday? 15:15:20 sounds good! 15:15:50 that's all on that topic from me for the moment. 15:16:05 - Roadmap: how are we doing with the tasks in progress? 15:16:24 gaba? 15:16:41 hey 15:16:54 it seems we are on track on many of the tasks in progress 15:17:13 I have a few suggestions for moving cards. 15:17:26 #26838 is done, I think. 15:17:28 mmm, just a sec that I clicked the wrong thing in storm... 15:17:31 yes 15:17:46 #28322 is in progress 15:18:01 #26597 is on review 15:18:30 right. 15:18:35 #29366 is done 15:18:44 #21378 is the one you were talking about. Is still in progress, right? 15:19:19 #21378 is what we talked about, yes. 15:19:26 and it's still in progress, but close to completion. 15:19:28 #23758 should go to the icebox probably? 15:19:33 whoa no wrong ticket 15:19:42 #23752 should go to the icebox probably? 15:19:55 yes. 15:20:10 or backlog? is not coming back any time soon? 15:20:37 as time permits. 15:20:40 ok 15:21:17 the others on in progress? 15:21:24 I was wondering if #29653 and #69650 should go into the icebox for now, too. 15:21:30 errr 15:21:41 #29650 15:22:00 #29653 should go to icebox, not #29650 15:22:11 ok. 15:22:46 #29624 is the bit that i'm still working on anyway 15:22:52 and I was wondering if "Perform one off page load metrics for user perf metrics" could go into backlog and soon into in progress. 15:23:11 would be something to discuss at moz all hands. 15:23:25 if it happens in the next few weeks. 15:23:30 it sounds good 15:24:26 what do you think, irl? 15:24:41 is that something you would work on, or is it for me? 15:25:31 well, I could do something there, but it would be good if you reserved at least some time for this. 15:25:40 my workstation is in a mess at the moment so trying to get a working selenium+tor browser setup might take more time than it's worth 15:26:15 something broke in an apt upgrade recently and i've not worked out what it was yet 15:26:33 when would it need to be before? 15:26:56 it would be good to have any work done that may help the conversation for the all hands 15:27:05 I think starting measurements by end of the month, running them for a week, and then looking at the results would be good. 15:27:42 let's move it to backlog and either of us starts working on it? 15:27:56 right, a week's worth of measurements is not something i could magic up this month 15:28:34 okay, happy to grab the card. 15:28:49 unless, i could run it on aws 15:28:54 well, sure. 15:29:05 if that works, too, I don't see an issue with that. 15:29:10 small machine should be sufficient. 15:29:15 in which case i should be able to set up something on 28th june 15:29:21 in which case i should be able to set up something on 28th may 15:29:34 or april? 15:29:39 may is great! 15:30:02 i just want to make sure i have a whole clear day, which is why i don't want to say i can do it sooner 15:30:16 okay, cool! 15:31:12 trying out "focussed tuesdays" to follow from "review mondays" 15:31:32 heh 15:31:34 and "meeting thursdays" 15:31:40 yeah... 15:31:48 okay, so backlog? 15:31:55 yeah 15:32:12 I need to leave in 5 min. 15:32:15 sorry 15:32:32 these were all my updates for the roadmap. 15:32:40 Is all the other things in 'in progress' and 'in review' correct? 15:32:47 i believe so 15:32:52 same here. 15:32:53 PRD for metrics portal in review? 15:32:54 ok 15:32:59 still waiting for antonela 15:33:06 ok 15:33:21 not in a huge hurry though 15:33:34 one more thing I have is bring the Tor meetup. Does the team needs one space for the morning of one of the days? 15:33:44 what do the other teams do? 15:33:58 we should probably follow that. 15:34:02 still deciding. OONI asked for 1 whole day and it seems that will also be the case for the network team. 15:34:13 i think we have not run out of roadmap yet 15:34:23 irl, what are you waiting from me exactly? 15:34:31 https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/DailyAgenda 15:34:32 we could shuffle priorities but we're looking a way down the road maybe it doesn't make sense 15:34:37 ohhh, sorry 15:34:38 true, but we'll have to make more roadmap for the time until the next meeting. 15:34:38 antonela: review of the prd for data portal 15:34:46 I need to go. I will look at the backlog later. o/ 15:34:51 o/ 15:35:17 i think we could even have a 1 hour roadmapping session 15:35:22 if we plan ahead 15:35:23 hehe 15:35:45 in fact, that is what we have on the agenda 15:36:03 1 day sounds like a lot. 15:36:16 yeah, we could roadmap the next 25 years in that 15:36:22 irl: oh, okey 15:36:51 my understanding is that if we need less time, that's not an issue. 15:37:01 on the other hand we cannot do as much if everyone else is busy with their team. 15:37:19 i think it may be useful to spy on other roadmapping sessions in the morning 15:37:20 maybe we should put this on the agenda for next week? 15:37:33 one of us can do ooni and the other network 15:37:37 yeah ok 15:37:44 yes, that sounds like a good plan, too! 15:37:53 just in case they make plans that involve us. 15:38:12 exactly 15:38:28 cool! 15:38:57 I guess gaba will read backlog and would tell us if she needs to know anything else regarding the tor meetup. 15:39:07 anything else for today? 15:39:10 yeah, can follow up with email if needed 15:39:12 nothing else from me 15:39:14 yep. 15:39:39 cool! thanks, and bye! o/ 15:39:46 bye! 15:39:52 #endmeeting