15:01:11 #startmeeting metrics team 15:01:11 Meeting started Thu Apr 25 15:01:11 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:16 https://storm.torproject.org/shared/5h1Goax5eNusxjXJ_Ty5Wl7hFR1uqCReUiN8xdlBG8T <- agenda pad 15:01:59 who's here for the metrics team meeting? 15:02:12 hi! 15:02:17 hi acute! 15:02:32 is gaba here? 15:03:18 yes 15:03:19 hi 15:03:22 hi! 15:03:53 shall we start? 15:03:56 ok 15:03:58 or add more topics to the agenda? 15:04:20 i do not have anything else to add 15:04:53 no more topics from me 15:04:59 me neither. we have a lot of discussions going on in parallel on tickets, but I don't think we need to discuss any of those now. 15:05:25 acute: any other topics you want to add? 15:05:30 ok 15:05:39 no 15:05:44 okay! 15:05:48 - #29399 (Retire host and services for tordnsel and check) 15:06:00 I added that one because weasel was asking 15:06:17 I said we have deprioritised it until it is funded, which is my understanding 15:06:57 we do not have funding for any of the stuff that is happening in metrics. we should do our own priorities right now outside of what is funded or not. 15:07:20 i understood it was deprioritized or it is going to be done in the next year, right? 15:07:32 i think weasel would like it done a lot sooner 15:07:48 aren't we going to apply for funding for this work very soon? 15:08:21 i have lost track of that 15:08:31 yes but I think we should work on needed stuff without funding. when we apply then we can change roadmaps according to that. 15:08:46 still, I think it's not highest priority for us at the moment. 15:08:54 the plan is to schedule a conversation between us and al to talk about that funding. 15:08:57 ok 15:08:58 if we don't work on the bandwidth file archive soon, we'll lose more data. 15:09:04 ok 15:09:15 if we don't work on the performance stuff soon, the results will be less relevant. 15:09:30 It is fine if that is the priority for that specific reason. We should communicate it with weasel that way. 15:09:47 the trouble with backups is new. 15:10:01 last thing we knew before that was that we still have 1 year until LTS runs out. 15:10:18 and even though we didn't want to use that full year, having at least a few months would be good. 15:10:48 ok 15:11:08 I see that irl has already answered on the ticket. 15:11:27 I only skimmed the conversation there, but that answer sounds reasonable to me. 15:11:47 ok. sounds good 15:11:50 I'll take a closer look later. 15:12:01 and then reply on the ticket. 15:12:34 anyway. 15:12:45 anything else on that topic? 15:12:48 yes, the reason we are not working on it is not because there is no funding 15:12:59 but yes, we can continue on the ticket 15:13:33 sounds good to me, thanks :) 15:13:52 thanks for helping with this, and sorry it's such an annoying topic... :( 15:14:30 okay. next topic doesn't need discussion? 15:14:40 mike's experiments are not going to work 15:14:41 it's meant as an announcement only? 15:14:44 net one that i wanted to bring for discussion but just a reminder :) 15:14:52 hah 15:15:07 relays count for 24 hour periods, but not necessarily starting at midnight 15:15:12 they all have different 24 hour periods 15:15:24 he needs to have 72 hour windows and measure the middle 24 hours 15:15:43 irl: can you make comments to mike, in #tor-internal or tor-scalability mailing list or meeting? we need to discuss this. mikeperry is working on this specifically. 15:15:49 are you able to come to the meeting on friday? 15:16:03 possibly as long as it's not clashing with driving lesson 15:16:09 it would be good if there is some discussion before that meeting 15:16:14 otherwise i'll post to tor-scaling 15:16:17 thanks!! 15:16:41 okay, cool! 15:16:48 now, roadmap? 15:16:54 yes 15:17:08 * irl loads up roadmap 15:17:22 unfortunately, the roadmap does not load for me 15:17:24 any change on any of the cards in the 'in progress'? 15:17:29 hey, there is a bug in wekan 15:17:36 click on 'all the baords' at the top 15:17:37 #29376 can be moved to done 15:17:40 and then click on the metrics one 15:17:46 (if this is still in progress on the board) 15:18:02 #29374, #29366 are under review 15:18:03 yes, thanks 15:18:21 I mean, they can be moved to 'under review' 15:18:55 ok 15:19:23 I'm working on #29507 in parallel to #30216 and other children of #21378. 15:19:42 but mainly #29507 and #30216. 15:19:57 irl took over #29315 from me. 15:20:07 yes, i am working on #29315 15:20:12 I think the PRD for data portal is "under review". there is no ticket but antonela is the reviewer. 15:20:51 ok, sounds good 15:21:06 I wonder what to do with Bridgedb stats. 15:21:14 I have a bunch of emails in my inbox on that topic. 15:21:30 sorry, one more from me : #26673 is in progress (PR ready to submit) 15:21:39 i think it may be necessary to do them twice 15:21:51 but I'm careful not to add yet another thing to my in progress items. 15:22:01 do what twice? 15:22:09 bridgedb stats? 15:22:18 we currently don't have the resources to do bridgedb stats in a useful way, we might just let network team do whatever and then later retrofit or rewrite it into our pipeline 15:22:37 anticensorship team 15:22:49 which is part of the network team 15:22:52 (: 15:22:52 and yes, I agree that we don't have the resources at the moment. 15:22:54 oh? 15:22:55 ok. :) 15:22:59 i thought it was, maybe i'm wrong 15:23:05 "incubating" 15:23:08 heh 15:23:23 karsten: bridgedb stat let's include phw in the conversation 15:23:44 anti-censorship team is its own team now that includes cohosh and phw 15:24:07 yes, happy to discuss this with phw. my point is that we might not be able to have this conversation in the next 2 or 3 weeks. 15:24:14 right 15:24:15 it's a whole new topic to add these stats. 15:24:25 it's a context switch which uses lots of mental energy too 15:24:26 and we need to focus on this to do it right. 15:24:30 yes. 15:24:36 * phw pops in 15:24:39 hi! 15:24:45 hi karsten! 15:25:02 * phw reads backlog 15:25:07 we're just talking about delaying the bridgedb stats work for a bit, because we're overloaded with other stuff at the moment. 15:25:34 same with snowflake stats, though I don't know how far that has progressed so far. 15:26:02 phw: is that blocking any work that needs to be done for s19 ? 15:26:27 karsten, ir: funny thing is that anything related to snowflake or bridgedb is funded by s19 :) 15:26:37 right! 15:26:40 i understand. that's fine from my side. we can still collect these statistics independently, without directly having them go into tor metrics. 15:26:57 are there deadlines? 15:27:16 sounds good! i think mostly we need to be sure it is not blocking any work on the anti-censorship team 15:28:14 it's not blocking anything. there's still merit in having the data, and publishing some insights from it, even if it's not fully integrated in tor metrics yet. 15:28:31 karsten: the sponsor ends at the end of may but there will be other sponsor after that. but it seems we do not need this soon. 15:28:33 (for bridgedb, that is) 15:28:56 ideally, we'd have this discussion before collecting and using data, though. hmmm. 15:29:12 this is what i'm saying, we could just do it twice 15:29:24 and bill the funder twice 15:29:36 ? 15:29:46 what do you mean? 15:29:47 yes, it would certainly be nice to have someone confirm that the data collection approach is safe. 15:30:04 phw: can you use the research safety board for this? 15:30:17 unclear if that's faster. 15:30:52 so, end of may is in ~5 weeks. 15:31:00 what needs to happen in that time? 15:31:03 i'm happy to contact the board if you think that's the best way forward. 15:31:20 this sponsor is very flexible. we do not have any specific objective other than work on this 15:31:32 but we want to show results at the end of may? 15:32:20 stating the obvious: this is not much time. 15:32:32 gaba: by this logic, the sponsor could also fund the tor metrics work to integrate the stats 15:32:35 and if it includes time to collect data, it's almost no time. 15:33:01 yes irl 15:33:02 or at least, tor metrics time to do the design 15:33:13 which the follow-on sponsor would then fund the implementation of 15:33:22 that would work, time-wise. 15:33:34 s/would/could/ 15:34:14 let me suggest something: let us continue/hopefully complete our current tasks in the next two weeks. 15:34:29 and then we focus more on the bridgedb (and snowflake?!) thing. 15:34:36 sounds good to me. 15:34:49 * gaba needs to run out now but it seems we are fine. 15:35:21 ok. 15:35:34 o/ 15:36:13 thanks karsten and irl! 15:36:23 do you want me to approach the safety board in the meanwhile? 15:37:04 it is not a terrible idea to have a second opinion (or fallback first opinion) 15:37:37 what about snowflake? 15:37:55 do we need to do something there until end of may, too? 15:38:28 let me see if cohosh is around. 15:39:21 irl: in the meantime, should we move #28322 out of the backlog and into the icebox? 15:39:40 and #24422? 15:39:55 hi o/ 15:39:58 #28322 yes, not #24422 15:39:59 hi cohosh! 15:40:16 being realistic with time 15:40:27 cohosh: we were just talking about whether we need to do something with snowflake stats by end of may. 15:40:37 for sponsor 19. 15:40:42 ah yeah 15:40:51 i was thinking about this again this morning 15:41:08 and i think the best plan is to not try to get all of the stats at once and start with some really simple things 15:41:19 like for example time series information about how many snowflake we have 15:41:30 so that we can compare that to client usage metrics collected from the bridge 15:41:45 okay, so we should schedule this for may then. 15:42:00 yeah i have replying to the snowflake stats ticket on my todos for this week 15:42:32 so, we're trying to juggle many things at the moment. 15:42:53 we might not be able to do anything for this in the next two weeks. 15:43:03 ok that makes sense, i just want to make sure i'm not the one blocking you on this 15:43:16 we're ok if it's not done immediately 15:43:17 no, that's not the case. 15:43:24 but do you need something by end of may? 15:43:27 cool 15:43:37 the number of snowflakes timeseries would be good to have, yeah 15:43:44 ok. 15:44:04 thanks! 15:44:17 our roadmap might be a tiny bit more accurate now. 15:44:21 np! 15:44:32 okay, anything else for today's meeting? 15:44:37 * cohosh also expresses appreciation on the input on safely collecting metrics 15:44:57 :) great! 15:45:26 irl, acute: anything else for today? 15:45:34 not from me 15:45:35 not from me 15:45:54 perfect, thanks! talk to you next week then! 15:45:59 #endmeeting