15:00:13 #startmeeting metrics team 15:00:13 Meeting started Thu Mar 2 15:00:13 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:21 hello :) 15:00:42 hey :) 15:01:07 13 seconds late ;-) 15:01:20 Meeting started Thu Mar 2 15:00:13 2017 UTC 15:01:44 yeah, sorry for that :D 15:02:10 okay, shall we start? anything missing in the agenda? 15:02:20 sure. 15:02:45 okay. 15:02:47 - Atlas usability project remaining fixes and blog post (irl|RaBe) 15:02:49 hi 15:03:04 - 16 tickets closed this week 15:03:06 amazing to see all those closed trac tickets! 15:03:15 :D 15:03:17 i've had to keep updating the agenda for this number 15:03:24 because patches just kept coming 15:03:28 and they were all good 15:03:32 great! 15:03:36 awesome! :) 15:03:41 we're getting through these quite quickly now 15:04:11 there's less than 30-ish left i think 15:04:26 22 to be exact 15:04:33 maybe the blog post will summon more contributors. 15:04:44 indeed 15:05:01 we have at least one, maybe more than one cypherpunks that has been very helpful 15:05:15 good to hear. 15:05:26 on the topic of new contributors, i've prepared a wiki page 15:05:34 - New wiki page with information for prospective contributors https://trac.torproject.org/projects/tor/wiki/doc/Atlas 15:05:55 there is a hacking section here that should help new contributors get started, improvements to this are welcome 15:06:10 cool! 15:06:28 cool! mind if I look at the blog post and the wiki page after the meeting? 15:06:38 (TODO: Which mailing list should be used for Atlas?) 15:06:39 that seems ok 15:06:53 (which would be effectively tomorrow, because of another meeting after this one.) 15:07:05 karsten: no problem 15:07:09 fine question about the mailing list. 15:07:20 On the bottom of the page. 15:07:32 i was thinking tor-relays@ for users and metrics-team@ for dev 15:07:45 unless you think it's worth a dedicated list 15:07:46 that could work. 15:07:51 (which i don't) 15:08:10 I'd say let's use existing lists and see how that goes. 15:08:28 metrics-team is good as things are related to Onionoo often. 15:08:31 maybe mention that both lists are public. 15:08:46 ok, i'll do that 15:09:38 sounds great! 15:09:41 (: 15:09:57 unless RaBe has anything futher on Atlas, I think that concludes Atlas for now 15:10:01 oh, except one thing 15:10:32 this is part of a Sponsor X deliverable, which mentions the scope for bugs, which should probably be used to prioritise bugs 15:10:46 can someone at some point point me at the missing context i need to work out what they are? 15:11:05 high-priority are the focus for X. 15:11:12 oh, I think we're doing just fine with respect to sponsor X. 15:11:23 high priority by 2016-12-31. 15:11:29 right. 15:11:41 ok cool. i just stumbled across it in the wiki and wondered if there was anything that was important 15:11:48 that sounds fine 15:11:50 well, we mostly put that in, so that we don't suddenly have to solve all tickets (which you almost did ;)). 15:12:02 heh (: 15:12:03 we should have known :-) 15:12:07 true! 15:12:18 overachieving is good :-) 15:12:37 Hi all. Does Tor Browser cache view-source: pages? 15:12:51 yes, we did a lot more than we had to. but that's okay. 15:13:01 users actually use this stuff. 15:13:15 davywybiral: in a meeting right now. want to ask in #tor-project or come back in 45 minutes? 15:13:29 alright, shall we move on? 15:13:40 sure :) 15:13:53 - CollecTor, Onionoo, and metrics-lib websites (karsten|iwakeh) 15:14:03 there are at least 3 topics here: 15:14:07 - move sub sites to Metrics 15:14:07 - split Metrics into data-processing service and website 15:14:08 - rebranding (or let's wait postpone this until it's on Trac) 15:14:21 oh, and another one: 15:14:34 - metrics-lib contents 15:14:44 web-site? 15:14:45 all somewhat related. 15:14:52 - metrics-lib website contents 15:15:20 so, iwakeh and I just had a discussion of the metrics-lib website. 15:15:21 well, the last is going forward. 15:15:28 and we have a plan. 15:15:42 our action items are: 15:15:42 iwakeh: https://trac.torproject.org/projects/tor/ticket/21614 15:15:43 karsten: write a draft page of what we discussed above 15:16:00 which I'll share on the ticket next week. 15:16:20 3 needs some discussion via mail still? 15:16:42 probably. 15:17:10 Is 2 in scope for q1&q2 2017? 15:17:28 not necessarily. 15:17:44 it would be good to discuss whether it's a good idea though. 15:17:54 but the actual work can happen after sponsor X. 15:18:17 was there a ticket? 15:18:24 for 2? 15:18:34 yes? 15:19:01 ah, right. 15:19:04 #19754 15:19:53 I wonder how to move forward here. hmm. 15:20:00 I think I can respond to the comment there. 15:20:29 Currently, web and backend are intertwined. 15:20:50 irl: would you want to comment on #21551 and whether that would work for you? 15:20:56 iwakeh: true. 15:21:12 * irl takes a look 15:21:21 irl: basically, you brought up concerns last week, and I hope we addressed those. 15:22:03 okay, seems like we can continue on trac here, and hopefully discuss this more with a trac ticket for 3 next week. 15:22:18 ok. 15:22:29 karsten: all the concerns are there, so that's ok 15:22:41 irl: okay! 15:22:54 moving on? 15:23:00 yep. 15:23:14 hiro: around? 15:23:21 uhhhhm 15:23:23 skipped one. 15:23:27 - Tech reports on statistics collected by the Tor daemon (iwakeh) 15:23:34 (sorry!) 15:23:44 Aiming at next week new draft 15:23:58 yeah, sorry for keeping you busy with all the other stuff.. 15:24:11 well, 15:24:17 'aiming' 15:24:24 yes i am here 15:24:25 but, I might have 15:24:31 sorry :) 15:24:38 a list of questions for you by tomorrow. 15:24:44 sounds good! 15:25:58 and just in case there's a question that you need an answer to more quickly, don't wait for the list to be finished. ;) 15:26:12 good to know :-) 15:26:21 okay, moving on? 15:26:35 yes. 15:26:40 - Deployed OnionPerf instances (hiro) 15:26:44 yep 15:26:45 hiro: there. 15:27:01 so I was making an issue when parsing the time differences 15:27:28 I thought I was getting the difference in microseconds instead I was just getting the microseconds part of the difference 15:27:35 I noticed the new graphs look more similar to torperf than the old ones. 15:27:42 so I fixed that and the data in the board made more sense yes 15:27:50 great! 15:28:11 I am going to add to the documentation the tpo machine 15:28:18 I will send that to the ticket too 15:28:25 so we will have 3 instances in the end 15:28:33 cool! 15:28:56 onionperf-one which is the US-DC instance.. then onionperf-eu which is in amsterdam and the onionperf.tpo 15:29:02 s/the/then 15:29:27 where is onionperf.tp.o? 15:29:27 that's my update 15:29:35 hetzner? 15:29:36 just curious. 15:30:12 so, hmm, we're printing these names out on the metrics website. 15:30:22 I wonder if there's a way to make them more intuitive to users. 15:30:40 maybe onionperf-$cc for all of them? 15:30:55 $cc ? 15:30:59 country code. 15:31:05 ah ok 15:31:11 yes we can do that 15:31:54 or op-$cc ? 15:32:06 not sure if onionperf-$cc is too long. 15:32:11 the question is do you want to do that at the host level, onionperf logs or collector? 15:32:43 host level would be easier, I guess. 15:32:49 op-$cc might be better. 15:32:50 ok :) 15:33:02 otherwise different collector instances could collect these logs differently. 15:33:15 ok 15:33:15 they could always 15:33:17 I think they shouldn't mess with the source name. 15:33:25 they could, but not accidentally. 15:33:36 true. 15:33:49 hope that's not too much trouble, hiro? 15:33:53 but, the source is configuration. 15:34:09 so, operators will mess with it ;-) 15:34:13 it isn't :) 15:34:21 yes, but onionperf operators. 15:34:31 not collector operators. 15:34:45 ah, I was referring to collector ops. 15:35:58 hmm, not in the branch I'm working on, which I never showed anyone. ;) 15:35:59 +## OnionPerfHosts = http://first.torproject.org/,http://second.torproject.org/ 15:36:17 collector just uses whatever source onionperf puts in. 15:36:23 in that branch. anyway. :) 15:36:38 ok, 15:37:06 I thought it would be analogue to torperf there. 15:37:25 ah, you think it's a feature. hmm. 15:37:31 maybe. 15:37:39 lots of things to discuss when that branch is ready. 15:37:40 well, we might want to change names 15:37:54 and researchers might need it 15:38:03 for their own perf-files. 15:38:29 yes :-) 15:38:46 yes, let's take that to the ticket once there's something that works. which is not the case yet 15:38:55 okay, cool! 15:39:08 I need to write text anyway :-) 15:39:13 I hear that sponsor R folks are waiting for this, too. 15:39:43 shall we move on to the last topic? 15:40:14 sure. 15:40:19 - Monthly team report (karsten) 15:40:26 I put the current draft on the pad. 15:40:34 anything that needs tweaking before that goes out? 15:41:21 fine from my point of view. 15:41:25 cool! 15:41:30 atlas bits look fine 15:41:34 great! 15:41:40 yep, all good 15:41:47 (linebreaks and XXX replacements, of course :-) 15:41:52 heh, yes. 15:42:25 okay, how about I leave it there for another 15 minutes until 16:00 UTC and then send it out? 15:42:41 except there's need to edit something, in which case I don't send it yet? 15:43:35 main block were agreed upon. 15:43:41 blocks 15:44:09 good! 15:44:12 (: 15:44:24 okay then. done on time? :) 15:44:27 :-) 15:44:37 3 weeks until amsterdam, by the way. 15:44:45 yay! 15:44:46 * Samdney comes too late and lurks :) 15:44:56 yes. 15:45:10 Samdney: any pressing questions before we end the meeting? 15:45:23 not for the meeting 15:45:27 okay. :) 15:45:43 great, thanks for this meeting, everyone! talk to you next week. 15:45:47 #endmeeting