14:29:23 #startmeeting metrics team 14:29:23 Meeting started Fri Oct 20 14:29:23 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:29 hello! 14:29:45 https://storm.torproject.org/shared/Ou-1QRctynWbF4yedi-MfDsjImFMFSIEP20fbVGCPRa <- agenda pad 14:29:54 for today's metrics team meeting. 14:30:07 * karsten spotted iwakeh, but is irl around, too? 14:30:32 On the pad? 14:30:46 well, on the pad and here. 14:30:52 * irl is everywhere 14:30:55 hehe 14:31:00 perfect! 14:31:14 I'll start with the first topic then: 14:31:17 hi irl! 14:31:20 * roadmap feedback from Montreal [karsten] 14:31:42 so, as expected, I received a lot of ideas what else we could be doing. 14:31:55 I did not receive many ideas we can remove from the current plan. 14:32:18 some of the new ideas seem really important, so we'll have to decide which of the existing ones to drop ourselves. 14:32:36 I'll go through the list that I started on the pad. 14:32:36 is there a list of ideas in a wiki page or similar? 14:32:44 ah ok. 14:32:50 there are notes on the wiki. 14:32:57 but I did not clean them up very much yet. 14:33:04 so, #1 is: 14:33:05 - Twitter bot/external communication 14:33:10 was the twitter bot really popular enough to be first on that list? 14:33:20 that idea was really well received. 14:33:29 oh cool 14:33:41 it's not necessarily the most important one, but there's certainly request for having this bot. 14:33:42 what contents were expected for the bot? 14:34:06 I think people started looking at @TorAtlas and liked that a lot. 14:34:19 which doesn't mean that it's too late to discuss and decide ourselves what contents we want to provide. 14:34:24 so, in the direction of our earlier mail thread. 14:34:34 yes. I replied to that a few days ago. 14:34:38 when you were afk. 14:34:49 it's something we should include in the roadmap and pick up over the next weeks. 14:34:57 true. 14:35:00 and we should include steph and tommy. 14:35:08 so the bot basically has "templates" and then fills in data from onionoo 14:35:18 there's no reason we cant use the CSVs or OONI data or whatever 14:35:30 sounds good. 14:35:42 to be honest, I haven't even looked at the code yet, 14:35:47 those graphics are just Graphics2D things 14:35:56 or put any thoughts into implementation questions. 14:36:04 #23799 14:36:25 i don't know who to poke for that 14:36:29 metrics-bot? 14:36:41 yes, metrics-bot might make more sense. 14:36:50 poke for creating the repo? 14:36:54 yep 14:37:01 and i'm open to renaming it to metrics-bot 14:37:21 fine question. I'm not sure who's creating repos these days. but I can find out. 14:37:25 i also see it being an irc bot that can do what zwiebelbot does for bugs but for relays 14:37:28 cc karsten 14:37:36 on the ticket. 14:37:48 irl: sounds great! 14:37:51 iwakeh: makes sense! 14:37:59 Cc: karsten added 14:38:06 alright. 14:38:13 moving on? 14:38:19 yep 14:38:20 fine. 14:38:26 - OONI graphs 14:38:37 this is also something that people want to see. 14:38:54 also to show closer cooperation between metrics and ooni, which makes sense. 14:39:03 on metrics.tp.o? 14:39:07 what we discussed is that ooni will provide CSV files to us. 14:39:08 yes. 14:39:19 with tor-related stats. 14:39:21 ok, this sounds cool 14:39:29 yes, indeed. 14:39:46 for example, they have a vanilla tor test that tries to bootstrap from wherever there are ooni clients. 14:40:15 the plan is to visualize how these connections are successful in different parts of the world, and maybe how fast that goes. 14:40:30 and there's another data set about reachability of default bridges shipped with tor browser. 14:40:48 i remember they previously had a deliverable to explain the ooni pipeline, so we should get the detailed explanations of what is in the CSVs 14:40:50 so, useful stuff. and we don't have to write the aggregation code. *phew* 14:41:04 hehe. 14:41:22 we'll certainly learn how they're making their CSVs. 14:41:30 @irl yes that'll be important. 14:41:36 I think we'll be part of the process to design them. 14:41:48 so, something for the roadmap and for the upcoming weeks or months. 14:41:55 ok cool 14:42:05 next? 14:42:10 yes 14:42:14 yep 14:42:15 - IPv6 graphs 14:42:23 that's something that teor wants. 14:42:32 he's working on integrating ipv6 better in tor. 14:42:52 and he'd like to see graphs on how ipv6 adaption is right now, and how that changes after making some changes. 14:42:53 the thread on metrics-team? 14:43:08 maybe? I don't know exactly. (so many threads.) 14:43:21 * irl had planned to add ipv6 graphs to metrics-bot 14:43:31 * iwakeh sighs, about the lists. 14:43:32 in any case, we won't have to add new data to the tor daemon for this. 14:43:41 which would take ages. 14:43:52 true. 14:43:52 what we do need to do is write aggregation code. 14:44:08 but the cool thing is that we can still throw in the entire archive when we're done. 14:44:17 so we don't need to do it all this afternoon! 14:44:25 it will still be useful in 4 weeks. or 8. 14:44:37 is there a deadline? 14:44:55 this work is also something that people care about and that show how metrics are important for the other parts of tor. 14:45:09 not that I know of. maybe we should ask. 14:45:13 good point. 14:45:18 so, higher prio than the other topics we just talked about. 14:45:28 roughly the same, I think. 14:45:31 sorry, I'm creating repos 14:45:37 but I haven't done it much lately 14:45:38 thanks, Sebastian! 14:45:47 ah. 14:45:56 metrics-bot 14:45:59 way more reliable pinging me on irc than trac unforutnately 14:46:09 yes, Sebastian can you rename the thing to metrics-bot not atlasbot? 14:46:38 Is tomorrow ok? 14:46:48 sure. 14:46:48 Sebastian: yes, i'm updating the ticket 14:46:49 irl: maybe quickly update the ticket? 14:46:52 great! 14:46:55 renaming is annoying because you need to be careful and do manual stuff 14:46:59 thanks 14:47:04 and sorry for the wait 14:47:11 thanks! 14:47:16 (: 14:47:27 alright. that's all about ipv6. moving on? 14:47:36 yep 14:47:37 karsten: can we quickly 14:47:45 yes? 14:47:49 there was a bug about or addresses and reachability and things 14:48:01 and tor clients don't check reachability of ipv6 or ports 14:48:12 is it dirauths that test reachability themselves before including them? 14:48:14 and not all do? 14:48:20 ah. 14:48:36 you mean #21637? 14:48:48 yes 14:49:06 if so, turns out that tor26 and gabelmoo don't include relays as running if they are not reachable via ipv4 _and_ ipv6. 14:49:18 there's more on the ticket, and I sent something to the dirauth list. 14:49:34 what do you want to know? 14:49:45 and note that I'm not too deep into this. 14:50:06 I mainly cared about finding out why my task-21637 onionoo branch produced the documents it produced. 14:50:19 i mostly just want to know what to do for atlas 14:50:20 teor might know more. 14:50:36 ah. nothing at this point. 14:50:36 if there's an ipv6 in or_addresses, is it reachable or untested? 14:50:53 reachable. 14:50:57 ok 14:51:02 then this is fine 14:51:13 with #21637 we're adding an unreachable_or_addresses field. 14:51:19 i couldn't answer this question yesterday on #tor, now i can 14:51:19 with the ones that are not reachable. 14:51:23 ah, cool! 14:51:28 we can move on 14:51:34 - better tool support for relay operators 14:51:40 so, relay operators are sad. 14:51:49 oops 14:51:52 and we discussed a few ideas how to make them less sad. 14:51:58 ok? 14:52:12 the part that is relevant to us is that we can provide them with better tools. 14:52:24 what kind? 14:52:28 longer term thing could be reviving tor weather. 14:52:35 someone has already 14:52:50 medium term thing would be an atlas with more gamification components. 14:53:07 really? I heard about torweather.org, but I couldn't find a running instance. 14:53:09 https://github.com/thingless/torweather/blob/master/README.md 14:53:13 it's running 14:53:14 I didn't look in detail, though. 14:53:15 i got mail from it 14:53:19 ah, neat. 14:53:26 should we add it to metrics.tp.o? 14:53:29 as a link? 14:53:36 i mean, there's not really a link other than the sources 14:53:37 ask the maintainer? 14:53:41 a lot was stripped out of it 14:53:47 to make it easier to run 14:54:01 do we know who the maintainer is? (other than seeing their github account?) 14:54:11 nope 14:54:24 what I mean: is there a website where I can sign up to get notifications? 14:54:31 most relay operators won't care about the sources. 14:54:44 ah, no 14:55:08 so, I need to run it myself to get notified about my own relays? 14:55:19 no, it'll scrape contactinfo 14:56:16 so, it's run somewhere and notifies relay ops? 14:56:18 hmmmm. so, if I were running a few relays, what would I do? 14:56:35 it just scrapes email addresses from contactinfo 14:56:41 when a relay is down, it'll tell you 14:56:43 by email 14:56:53 there is an unsubscribe option and it doesn't send more than one mail 14:56:54 regardless of any subscription? 14:56:56 yes 14:57:01 uhm. 14:57:03 understood. 14:57:06 you can only unsubscribe, not subscribe 14:57:14 not really great idea. 14:57:22 so, this is just an example. 14:57:31 i do wonder if such notifications are in scope for metrics-bot 14:57:37 we found that a working notification service might help relay operators. 14:57:53 well, maybe for high-profile relays. 14:57:57 yes, the bot might be a good place. 14:57:58 it could notify by email/tweet/irc/xmpp 14:58:18 Metrics messaging engine ;-) 14:58:26 ah, but directed to the relay operator only? 14:58:30 yep 14:58:33 rather than shouting it out to the world. 14:58:39 that would make sense then. 14:58:40 :) 14:58:53 but again, that's just an idea. 14:59:05 what we should do is brainstorm how we can make the life of relay operators easier. 14:59:25 okay, next one? 14:59:33 yep 14:59:41 - PrivCount proposals 14:59:49 we had a good meeting with the privcount folks. 15:00:00 they finished one proposal and discussed it a few weeks ago. 15:00:09 there will be more such proposals, some of which affecting us more than this one. 15:00:35 for example, there will be one for including noise. and we'll have to know what's going on there, because we'll later have to handle that noise. 15:00:50 or there will be another one for versioning statistics reported by privcount. 15:00:58 like, how do we add or remove statistics. 15:01:05 and two more or so. 15:01:23 these will be written in the next months, and we should be part of that. 15:01:45 good thing we already have an L task for this. 15:01:56 see also the notes on the wiki about this session. 15:02:11 were there other requests? 15:02:11 about tools for r-ops? 15:02:13 just downtime, t-shirt, ...? 15:02:19 maybe, ask in the relay ml and collect ideas? 15:02:41 wiki link? 15:02:49 I'd say let's brainstorm a little, suggest something to relay operators, and ask for other ideas. 15:03:02 * karsten finds the link.. 15:03:06 fine. 15:03:18 https://trac.torproject.org/projects/tor/wiki/org/meetings/2017Montreal/Notes/PrivCount 15:03:58 keep in mind that these notes are relatively quickly written while talking about things, so nothing is written in stone yet. 15:04:19 but I was under the impression that there's a common ground for making this work. 15:04:48 fine, so we'll notice 15:05:04 ah, and we have a plan for making the next proposal discussion work better despite timezones. 15:05:09 via tor-dev or will there be other means of looking at proposals early? 15:05:26 we might just use a pad and leave it open for a week where everyone can participate whenever they're awake. 15:05:41 good :) 15:05:44 I'm sure we'll notice somehow when new proposals are being written. 15:06:03 ;) 15:06:20 I have two dates here: feb 2018 and mid-2018. not sure which was which. but I figured neither of them is oct or nov 2017, so we're good. 15:06:27 for now. 15:06:40 alright. 15:06:44 - inter-team dependencies 15:06:57 we'll need to move forward with the roadmap draft until next thursday. 15:07:16 the idea is that all teams have roadmaps until then to identify inter-team dependencies. 15:07:25 another pad/googledoc meeting thursday? 15:07:50 and, reviewing and adding the new topics earlier. 15:07:52 regarding the tool, it might be that our google doc is sufficient. 15:08:18 regarding the timing, I was planning to put in more ideas over the next days. 15:08:25 including feedback above. 15:08:34 good. 15:08:43 I just had to write some code this week after talking about writing code for so long. 15:09:09 alright. I think that's all for roadmap feedback. 15:09:25 moving on to the next topic? 15:09:38 I moved irl's topic as it is montreal related. 15:09:54 * From the meeting: "Working bad: Tor Atlas backend is always down after a few searchers." ?? 15:09:57 you mean this one? 15:10:00 oh, unless there is another feedback topic. 15:10:07 yes 15:10:08 not that I know. 15:10:22 do we know anything about that issue? 15:10:33 who reported it when where? 15:10:41 somebody in montreal. 15:10:54 anonymous person? 15:11:00 we had a session where we wrote "works better", "works the same", or "works less well" on stickies. 15:11:09 and this one was on a "works less well" sticky. 15:11:10 ah. 15:11:22 (we had a few "works better" stickies, too. :) ) 15:11:28 i've not seen this 15:11:50 I also had atlas hanging/not making progress earlier today. 15:12:00 when I was looking into the ipv6 thing. 15:12:02 i've seen that we don't really get much backend being down since the new onionoo servers came along 15:12:25 could it be the second real backend? 15:12:29 or the load balancing? 15:12:40 we have lots of new caches. 15:12:43 i just can't reproduce it 15:12:57 maybe, that was an older notion? 15:12:57 i get more failures from the twitter api than i do from onionoo 15:12:58 but one that is a cache and separate backend. 15:13:08 okay. 15:13:20 I think most things on these stickies were quite recent. 15:13:29 but, anyway, 15:13:32 maybe it's when i'm asleep? 15:13:36 maybe watch out for any issues. 15:13:37 hehe 15:13:40 :-) 15:13:53 we can move on. 15:14:09 sure. 15:14:14 * next steps for Sponsor13 deliverables [iwakeh] (if time permits) 15:14:28 right, I thought about topics. 15:14:34 ok. 15:14:38 and how to approach the doc structure. 15:14:43 another idea is 15:14:54 to collect topics/questions raised in 15:15:06 mailing lists (as happened recently) 15:15:15 on a wiki page in order 15:15:31 to keep track and really address these in the end. 15:15:36 collecting ideas on a wiki page sounds great to me! 15:15:44 right now I'm collecting them, erm, in my inbox. 15:15:47 ok, I'll start one. 15:15:51 please do! 15:16:10 maybe also put your ideas about the document structure there. 15:16:14 and topics. 15:16:16 yes. 15:16:40 I'd say it's perfectly fine to collect ideas for the next few weeks or even until the end of 2017. 15:16:50 ok. 15:16:51 while we work off things that seem more urgent. 15:17:01 next topic? 15:17:06 and start actually writing docs in early 2018. 15:17:08 yep. 15:17:12 * next steps webserver logs (CollecTor&metrics-lib) [iwakeh] (if time permits) 15:17:19 all reviewed! :) 15:17:29 I noticed. 15:17:31 :-) 15:17:45 though not exactly on the plane. anyway. ;) 15:17:49 the replies will be high prio. 15:18:02 for both. 15:18:06 okay! I'll prioritize responding and re-reviewing. 15:18:07 just a thing from #tor, someone found the onion service for the sanitised logs and thought they'd stumbled onto a secret hacking operation 15:18:24 oh 15:18:43 maybe an index.html on the virtualhost to explain what is there and a link to the out folder would help 15:18:43 the onion service for https://webstats.torproject.org/ ? 15:18:45 yep 15:18:58 we'll soon shut that down. 15:19:01 this will go away. 15:19:06 ah ok 15:19:07 where soon means in the next couple of weeks. 15:19:12 it'll be on collector. 15:19:16 cool (: 15:19:40 okay. anything else on webstats? 15:19:47 nope. 15:19:52 last topic: 15:19:56 * other priorities regarding tickets [all] (if time permits, this might also depend on the first topic) 15:20:01 heh 15:20:06 fine question. 15:20:11 roadmap 15:20:16 for all of us. 15:20:33 you mean prioritize the roadmap over tickets? 15:20:50 not really, but not drop it. 15:21:07 * iwakeh wants to know if there are pending reviews open. 15:21:19 lots. 15:21:31 but, that doesn't mean they are higher prio than the roadmap. 15:21:42 the roadmap has a deadline. 15:21:43 ok. 15:22:06 so, from all the tickets in needs_review, I'm not sure if there's a clear order regarding priority. 15:22:18 that's fine, 15:22:22 if you want to review something, maybe pick something that looks easy. 15:22:27 I'll define it myself :-) 15:22:34 sounds good to me. :) 15:22:49 just wanted to make sure nothing is overlooked. 15:22:56 nothing is on fire. 15:23:03 good! 15:23:14 alright. I think we're done then. 15:23:18 yay 15:23:21 yep. 15:23:28 good meeting! 15:23:35 (: 15:23:35 yes 15:23:41 I'll ping you via email as soon as I have something new for the roadmap. 15:23:46 fine. 15:24:01 have a nice weekend, and let's talk more next week! 15:24:09 you too. bye, bye! 15:24:11 i'll rename atlasbot, and will email when sources are uploaded 15:24:17 though i won't be upset if you don't look immediately 15:24:20 great! 15:24:21 sounds good, irl! 15:24:27 bye, bye! :) 15:24:33 * irl -> coffee 15:24:35 #endmeeting