14:35:58 #startmeeting metrics team 14:35:58 Meeting started Thu Nov 2 14:35:58 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:35:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:36:07 let's start. 14:36:11 * inter-team roadmap coordination meeting tomorrow 14:36:20 you probably saw my email. 14:36:33 tomorrow afternoon there will be a meeting in this room. 14:36:41 * iwakeh looked through the other roadmaps. 14:37:00 No requests for us, afaict. 14:37:07 i haven't had a chance to look at the other roadmaps yet, but plan to tonight 14:37:22 we should look at the network team roadmap in particular. 14:37:31 Some are simple spreadsheet and not very verbose. 14:37:34 it's not that they're asking us to do something, but they're making changes that might affect us. 14:37:44 the format is quite different, yes. 14:37:59 when in doubt, let's ask questions tomorrow. 14:38:10 or if you're not there, drop me your questions. 14:38:10 Well, lists of trac tickets in tables ;-) 14:38:59 okay, that's all on that topic from me. 14:39:16 moving on? 14:39:19 ok, i may have things in an email after i've read them 14:39:21 yep 14:39:24 sounds good! 14:39:47 yep 14:39:47 * October report 14:39:49 :) 14:40:05 I started collecting some input for last month's team report. 14:40:14 it's on the pad. 14:40:18 what did I miss? 14:40:34 * iwakeh added one thing. 14:40:36 obviously it still needs proper sentences here and there. 14:40:50 you mean mentioning that we did this brainstorming? 14:41:09 having the list and sending it to the community. 14:41:29 I mean, should we include this in the report? 14:41:47 It's started and published in a first rfc. 14:41:51 ok. 14:42:12 maybe, admins chime in after the report :-) 14:42:22 heh 14:42:32 for metrics-bot and atlas, i'll have to look back at trac, which i can do tonight, and then write text 14:42:38 if that's not too late 14:42:45 that would be perfect! 14:42:54 not too late at all. it's the 2nd today. 14:43:00 sending monday would be fine. 14:43:00 ok cool (: 14:43:25 I'll also try to find more. 14:43:30 and then work on the format. 14:43:37 if anything else comes to mind, just add it. 14:43:40 me2 14:43:44 thanks! 14:43:52 * notifications for operational issues 14:44:04 should we have another session for that? 14:44:13 i think another pad session would be great 14:44:15 the one we had was already pretty successful. 14:44:21 but it was "just" 1.25 hours. 14:44:23 sorry again for missing the first one, but it did look really productive 14:44:28 it was! 14:44:38 +1 14:44:56 how about tomorrow at the usual time? 14:45:05 not great for me, i have work things 14:45:08 already? 14:45:28 next wednesday? 14:45:33 folks from the ml might use the weekend to reply. 14:45:43 this may also give me time to play with some nagios dev in a test instance 14:45:44 ah, good point. 14:45:49 points. 14:45:55 next wednesday sounds fine to me. 14:45:56 maybe combine with #24036? 14:46:09 we could try that. 14:46:16 if there's time, that sounds very useful 14:46:35 so, wed 14:30 utc for notifications + package names 14:46:44 15min monitoring, 45 naming. ambitious 14:47:09 or 50/50. 14:47:21 time is ok. 14:47:29 50/50 sounds good as a plan. 14:47:30 time is ok for me, added to calendar 14:47:50 great! 14:48:14 * prioritize Tomcat -> Jetty switch? 14:48:23 so, 14:48:37 could be higher on my list. shall it? 14:48:38 the reason is that I'm still having trouble getting m-web and exonerator to run in new vms. 14:48:47 ok. 14:48:50 I'd put reviews high on my list, too. :) 14:48:54 i'm also having trouble ith running a dev instance for atlas work 14:49:08 (irl's w key is broken, not sure if iwakeh saw that.) 14:49:15 hehe 14:49:19 no 14:49:40 so, yes, prioritizing sounds great! 14:49:45 fine. 14:49:49 (: 14:50:04 hmm, now the agenda looks short. 14:50:07 #23421 14:50:23 should I look at that? 14:50:23 needs input, b/c many things depend on it. 14:50:38 especially, streamlining and simplifications and new modules. 14:50:48 that would be great. 14:50:52 on the list. 14:51:27 So, I might look at the other roadmaps again, but I 14:51:43 don't see there is much to bring to that meeting. 14:52:11 feel free to spend your time more productively! 14:52:14 i've seen things that are nickm-cares which i feel may be an alias for network-wants 14:52:34 you're invited to join, but you could also do other things instead. 14:52:46 ok. 14:52:49 but maybe these are things not on the roadmap 14:52:58 irl: example? 14:53:15 were that analysis tickets that he didn't want us to close just yet? 14:53:32 https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~nickm-cares&component=%5EMetrics&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority 14:53:59 yes, I think that was that. 14:54:24 I don't think we're expected to make much progress on those. but let's ask! 14:54:47 its good to check 14:54:51 agreed. 14:55:06 And, state that we already overassigned our resources ;-) 14:55:10 hehe 14:55:14 yes. 14:55:16 heh (: 14:55:20 maybe they'll send more devs!! 14:55:33 :-) 14:55:33 or at least coffee 14:55:34 by the way: 14:55:36 #24018 14:55:52 we should think about what to do with that. 14:56:10 basically, we're being asked to add new onionperf measurements. 14:56:12 IIRC. 14:56:15 IIUC. 14:56:38 feel free to read the whole discussion after the meeting. 14:56:42 ah, did rob write additional code for his tool? 14:56:58 there's the more general question of what's in scope for metrics or network team. 14:57:10 which we're silently ignoring by keeping some things in a gray area. 14:57:17 iwakeh: not yet. 14:57:31 ok 14:57:33 maybe we should at some point define who does what. 14:58:02 yes. 14:58:14 I can see this going in either direction. but if we're expected to do more things, we'll need more resources. 14:58:30 more beans. 14:58:38 it is sort of a question of short term analysis and long term metrics data. 14:58:46 right! 14:58:54 arabica best blend :-) 14:59:02 :D 14:59:32 alright. something we could do next week: 14:59:41 being able to send coffee virtually would be great! 14:59:57 go through the list of open trac tickets tagged as metrics-2017 and make plans for resolving some of them in 2017. 15:00:01 it would! 15:00:37 fine. In the team meeting? 15:00:37 anyway. I think we ran out of topics for today! 15:00:40 sure. 15:00:56 I'm fine. 15:01:01 great! 15:01:10 anything else from you, irl? 15:01:18 i think i'm out of things 15:01:29 cool! 15:01:43 see you tomorrow, maybe. otherwise email, trac, next week! 15:01:50 one non-meeting thing 15:01:50 thanks and bye, bye! 15:01:50 bye, bye! 15:01:54 yes? 15:02:05 metrics-bot sits in tor-test if you want to spam it to try out features 15:02:05 shall I stop the recorder? 15:02:15 in #tor-test? 15:02:18 yep 15:02:22 i don't have a hash key 15:02:27 sounds good, will do. 15:02:30 haha 15:02:45 okay. bye, bye! 15:02:48 bye! 15:02:50 #endmeeting