15:00:31 #startmeeting metrics team 15:00:31 Meeting started Thu Feb 16 15:00:31 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:40 - Atlas usability project and blog post (RaBe) 15:00:55 RaBe: I went ahead and put that on the agenda. 15:01:02 hope that was okay. 15:01:12 want to give a quick update how this is going? 15:01:30 irl: same question to you, I guess. 15:01:51 oh, unfortunately nothing new in the past two weeks - irl was in spain, and I was working on CollecTor and other stuff :) 15:01:55 7 tickets ready for review, 1 ready for merge 15:02:07 neat! 15:02:15 i'll be catching up on those reviews this weekend 15:02:35 will start on drafting a blog post, ready for the end of the month 15:02:36 the plan is still to have a blog post by end of the month? 15:02:39 yep 15:02:39 awesome! 15:03:03 feb 27 is when we're going to launch onionoo protocol version 4.0. 15:03:20 we could aim for the 27th or 28th for the blog post. 15:03:26 this sounds good 15:03:34 great! 15:04:00 okay, if there's nothing to discuss today, shall we move on? 15:04:14 (nothing related to atlas, that is...) 15:04:42 sounds good, RaBe: we can continue as before now that i'm back 15:04:43 please bear with me today, antibiotics are running this body... 15:04:51 irl: sure! 15:05:18 okay, great! 15:05:35 moving on to the next topic: 15:05:37 - CollecTor website (RaBe) 15:05:43 I just commented on the ticket. 15:05:53 * iwakeh just commented on karsten's comment. 15:05:57 but maybe we should look at the prototypes together. 15:06:05 '21381 15:06:09 #21381 15:06:10 i just read ticket #21381... I'm not sure if i understand the suggestion with the "big table with buttons" 15:06:42 you mean this one? https://collector.torproject.org/#available-descriptors 15:07:05 if you click on one of the "format" buttons, you'll navigate to the data formats section further down below. 15:07:24 oh, i never figured that one out :) 15:07:36 hehe. can we make it more obvious somehow? 15:08:02 whoever goes there for the contents will notice, I think. 15:08:27 i think that was just me... i agree with iwakeh 15:08:28 But, that's hard to notice when just looking at the layout. 15:08:55 okay. 15:09:02 we could add an ">" to clearify they're buttons? 15:09:21 sure, feel free to try something like that. 15:09:55 so if i understand all comments correctly, we won't have ANY navigation left at that page? 15:10:07 (beside that table...) 15:10:09 could be. :) 15:10:17 the table is the navigation. 15:10:33 and browser search. 15:10:46 maybe we could turn the table more into a table of contents. 15:10:52 not sure how to do that. 15:10:58 well, 15:11:14 the descriptor types could become links. 15:11:21 yes, or that. 15:11:28 to the format. 15:11:41 i like that idea 15:12:02 another thing we could do is do something with cell background colors, indicating that a line is a relay descriptor, a bridge descriptor, etc. 15:12:22 not sure how that would work. most entries are for relay descriptors. 15:12:33 wouldn't that be too many colors? 15:12:35 or maybe something with thicker lines between groups. 15:12:46 yes, I guess I mean two alternating colors. 15:12:49 what about labels, like we use on the news? 15:13:02 or "badges" 15:13:22 or group headers, "relay descriptors" 15:13:32 I think rather group headers than badges. 15:13:34 "bridge descriptors" etc.? 15:13:39 badges might be confused with buttons. 15:13:44 well, assuming we keep those. 15:14:08 RaBe: want to take this input and try some things? 15:14:08 the format buttons will disapear. 15:14:20 yes, that one will disappear. I meant the recent and archive buttons. 15:14:41 maybe, have the column header "access" for the buttons? 15:14:51 i agree. i'll split the table into subsections somehow and comment on the ticket :) 15:15:32 okay. quite a few options there. 15:15:56 shall we move on? 15:16:01 yep. 15:16:15 - Tech reports (iwakeh) 15:16:28 yay, I saw a draft today. :) 15:16:45 yes, the second. I'm assembling some ideas and questions, which I'll mail later today. 15:16:53 with 15:17:05 ideas about how to proceed more speedily. 15:17:13 sounds good! 15:17:20 again, it's quite the topic. 15:17:35 big 15:18:00 any other references I should take note of? 15:18:23 fine question. I mention them as they come to mind. 15:18:31 ;-) 15:18:34 under the assumption that more input must be better. 15:18:44 and that you filter input appropriately. 15:18:46 ;) 15:19:07 yes, that filtering will 15:19:14 work some way :-) 15:19:19 heh 15:19:33 alright, looking forward to that mail later today. 15:19:49 moving on? 15:19:51 I'll try to keep it short 15:19:56 yes. 15:20:01 - OnionPerf (hiro) 15:20:05 sure 15:20:30 so last week I was finishing running some quick test to see if our onionperf deployment was prducing the same results as torperf 15:20:41 it looks like it is. 15:20:48 neat! 15:20:58 I basically did the parsing myself and used a python notebook to do a couple of plots 15:21:07 can you share those? 15:21:15 sure 15:21:28 I am going to send an email after this meeting 15:21:32 okay, great! 15:21:39 or, attach to that ticket? 15:21:49 how many instances are you running? 15:21:54 otherwise it get's lost in inbox too easily. 15:22:05 ok I will attach to the ticket better 15:22:13 sounds good. 15:22:20 thanks, that's easier to comment. 15:22:23 I am running only one instance at the moment. So moving forward there are two action items 15:22:49 1. Running also on tpo infrastructure. We have the VM I will set it up after this too 15:23:22 2. What do we do with this data? Shall I work to have it included in metrics-web? Shall I maintain a notebook that people can quickly play with? 15:23:49 re 2: I guess we should extend collector to fetch those files and archive them. 15:24:14 right now it only knows how to download the older .data and .extradata files and merge them into .tpf files. 15:24:28 but downloading .tpf files from remote servers shouldn't be that hard. 15:24:37 iwakeh: what do you think? 15:24:42 karsten yes. I guess that should be our goal. 15:24:44 that'll be easy. 15:24:51 happy to avoid httpurlconnection. ;) 15:24:55 hehe 15:25:12 hiro: the files are publicly available via http(s)? 15:25:16 yep 15:25:34 as one big file that gets bigger and bigger, or as one file per day? 15:25:43 one file per day 15:25:53 we need a description of how these files will accumulate and where, 15:25:55 cool! can you paste a url to the ticket, too? 15:26:01 sure 15:26:09 i.e., what path (if at all) under which url. 15:26:12 each measurement has a different file 15:26:18 sure I will add it to the ticket 15:26:55 okay, sounds doable then. 15:27:16 re 1: are you planning to run a second instance in a different location of the cloud? 15:27:29 we can do that too 15:27:37 that would mean we'd have 3. 15:28:00 by the way, we'll need to come up with names for these instances. 15:28:00 sure so I'll add that to my list 15:28:11 could be the physical location. 15:28:22 at the moment I have onionperf-one and was planning to just increase the numbering 15:28:26 or really anything. the current ones are torperf, siv, and moria. hmm. 15:28:46 well, numbers work, too. :) 15:28:48 anyway. 15:28:50 also I should share access to this instances ;) 15:29:16 either that, or be around when they break. which works for me, too. 15:29:18 :) 15:29:32 but yes, having a second operator would make sense in the longer term. 15:29:34 ok :) I can do both 15:29:45 similar to all the other services. 15:29:50 http(s) access is sufficient :-) 15:30:05 alright, moving on? 15:30:41 - metrics-lib 1.6.0 release (karsten) 15:30:49 I'd like to put out a release. 15:30:55 fine. 15:31:01 https://gitweb.torproject.org/metrics-lib.git/tree/CHANGELOG.md already has quite a few changes. 15:31:15 and there's #20323. 15:31:28 well, which could as well go into 1.7.0. 15:31:30 * iwakeh has review planned. 15:31:37 okay! 15:31:42 how about release tomorrow? 15:31:48 what about #20430? 15:31:52 so, 15:32:03 I started looking into that and found that it's related to #16225. 15:32:21 and then I started thinking about a better DescriptorSource interface. 15:32:39 which I added to #16225. 15:32:42 Well, ticket description and content differ quite a bit? 15:33:04 well, logging is just one way of handling an error. 15:33:21 the question is whether it's the right way to handle the error at all. 15:33:26 I'm referring to the interface changes. 15:33:48 you mean the builder pattern? 15:33:51 but not too quick, first 1.6.0 15:34:03 right. so, my plan was to discuss all that for 1.7.0 15:34:17 ? 15:34:24 oh, no 1.6.0? 15:34:27 logging and unifying error handling. 15:34:41 so, my plan was to put out 1.6.0 with what we have. 15:34:56 and move the logging improvements to 1.7.0 together with better error handling. 15:35:00 including those interface changes. 15:35:08 ok, depending on the review of 20323, if that'll be 1.6.0 or 1.7.0. 15:35:25 either would work, I guess. 15:35:29 ok 15:35:50 but I think that with a better interface, we'll have an easier time writing tutorials and that blog post. 15:36:02 the current interfaces are a bit clumsy. 15:36:07 there are some other tickets 15:36:16 with similar intentions. 15:36:19 true. 15:36:25 I'll look for them after meeting. 15:36:30 yes, please do. 15:36:52 okay, sounds like we have a plan for 1.6.0. 15:36:53 and take a look at 16225 15:37:01 yes, please. 15:37:04 and the planning of 1.7.0 15:37:07 :-) 15:37:13 so many plans! 15:37:25 well, we get them done, too :-) 15:37:25 okay, moving on? :) 15:37:31 yes! 15:37:34 fine. 15:37:39 - Berlin meeting (When?) 15:37:49 speaking of plans that did not work out.. 15:38:05 - Agenda planning for AMS (or schedule an online meeting?) 15:38:05 oh, that's life 15:38:14 yep. 15:38:26 ams could be a good time 15:38:35 I think that's a good suggestion, to make some plans for AMS. 15:38:42 ams := amsterdam 15:38:56 we'll have a team day, I think. 15:39:08 where we can schedule a session or two. 15:39:14 it's in my inbox somewhere. 15:39:24 ok, good place :-) 15:39:29 hehe 15:40:11 okay, how about I dig out what I have in my inbox related to AMS planning and our earlier TXL plans? 15:40:13 should we have a meeting (irc) next week about that? 15:40:21 BER 15:40:27 is that a thing yet? 15:40:39 what's TXL? 15:40:40 no, BER is any airport in Berlin 15:40:41 a separate meeting? 15:40:45 ah! 15:40:49 TXL = tegel airport. 15:40:51 ahh 15:40:54 txl:= tegel (berlin) 15:41:14 or should we add an agenda item for next week's meeting? 15:41:19 sxl:= schönefeld 15:41:33 is there anything urgent that it's better we start discussing before amsterdam? 15:41:33 yes. 15:41:59 nothing, which we are not yet discussing, afaik? 15:42:13 I can't think of anything in particular, no. 15:42:23 we're already preparing for AMS in a way. 15:42:43 did you already book flights? 15:42:48 ah ok :) 15:42:58 not yet, thinking about driving maybe. 15:43:02 and put your arrival and departure dates on the wiki? 15:43:04 my question was related to the question: shall we have a separated irc meeting 15:43:12 yes! I have to do that 15:43:40 regarding the separate irc meeting, I think we should try putting it on the agenda for next week and prepare a bit via email. 15:43:51 sounds fine. 15:44:04 yep sounds fine to me too 15:44:09 okay! 15:44:28 does that mean we're done early today? 15:44:35 yay! 15:44:51 well, on time as we intended this for 45min once upon a time :-) 15:44:58 hah, true. 15:45:20 alright. thanks for an efficient meeting, everyone! 15:45:33 thanks! bye, bye. 15:45:38 bye! 15:45:39 talk to you next week as usual. bye, bye! 15:45:41 thanks! talk later by email/ticket update 15:45:45 yep! 15:45:48 #endmeeting