14:00:47 #startmeeting Measurement team meeting 14:00:47 Meeting started Wed Jul 15 14:00:47 2015 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:56 who's here for the meeting? 14:01:01 * qbi is. 14:01:06 i am 14:01:13 me 14:01:41 hi qbi, tomlurge, leeroy! 14:01:48 hi karsten 14:02:25 I'll start suggesting an agenda, and maybe more people will have joined us by when I'm done. 14:02:26 here 14:02:31 hi aagbsn 14:02:32 hello 14:02:53 so, this is the second meeting, and last time we mostly did introductions. that's why we should do: 14:03:01 1. introductions of people who haven't been here last week. 14:03:20 (under the assumption that introductions from last week are in the log for anyone to re-read.) 14:03:28 I'd also want to talk about: 14:03:39 2. problems that came up last week and problems that came up since then. 14:03:47 things we can solve now or think about solving soon. 14:03:54 and then, 14:04:05 3. products: what's the scope of our products, what's their status, what's their future. 14:04:17 that will be an experiment that involves an etherpad. 14:04:24 I hope to spend most time on that today. 14:04:32 and finally, 14:04:41 4. discussion, misc, whatever you call it. 14:05:17 that's all. we should be done by 15:00 utc. an hour per week should be enough. 14:05:26 thoughts? 14:05:37 (i'm here too, sorry for being late.) 14:05:44 hi phw 14:06:21 looks like a good schedule to me. 14:06:22 okay then, let's start with 14:06:26 great! 14:06:29 14:03:31 < karsten> 1. introductions of people who haven't been here last week. 14:06:48 tomlurge: I think that's only you for now. want to give a quick introduction of yourself? 14:06:53 maybe I … 14:06:56 yeah 14:07:08 I’m working on a tool called visionion 14:07:26 which will be a visualization frontend to metrics data 14:07:33 +1 14:07:34 you can look it up on github 14:07:55 i’m terribly slow… 14:08:06 but you're still working on it! 14:08:11 (not only with typing ;-) 14:08:14 when did we first talk about it? which congress was that? 14:08:15 yes, i am! 14:08:31 ahem, 30 months ago 14:08:40 heh 14:09:04 that’s all from me, i guess 14:09:10 okay, cool. thanks! 14:09:21 (didn't we have virgil around here half an hour ago?) 14:10:28 well okay, let's move on, and when virgil comes back, we'll squeeze in another introduction somewhere. 14:10:36 14:04:08 < karsten> 2. problems that came up last week and problems that came up since then. 14:10:46 two things I wrote down from last week: 14:10:51 - did hellais find help with maintaining bridge reachability probes? 14:10:51 - did phw find help with handling reports about bad relays? 14:10:58 phw: any updates? 14:11:38 or rather, anything we can help with while we're talking here? 14:11:45 oh I see this meeting just began---Oh hai---I exist. 14:11:50 karsten: I exchanged an mail with hellais regards reachability probes. 14:11:58 hi virgil :) 14:12:13 virgil: let's finish this agenda item and then get back to introductions briefly. 14:12:20 I might be able to help him, but haven't found the time to fully read his last mail which contained all details. 14:12:29 qbi: oh, neat! 14:12:48 karsten: no updates. i've been busy working on zoossh and sybilhunter. 14:12:53 thanks for helping with that, qbi! 14:13:03 phw: ok. 14:13:35 phw: please bring it up again at one of the next meetings if you think this group can help. 14:13:48 (don't want to nag you unnecessarily when you're enjoying writing code.) 14:14:20 sounds like there's nothing more to do about these two problems. 14:14:35 did any other problems come up that we should discuss today? 14:15:03 not for me. 14:15:41 great. 14:15:41 nope 14:15:54 okay, should we move on to the fun then? 14:15:59 14:04:34 < karsten> 3. products: what's the scope of our products, what's their status, what's their future. 14:16:19 my plan was to start an etherpad somewhere 14:16:24 (any preferences?) 14:16:41 storm? 14:16:44 and come up with a) a list of products and b) a list of questions. 14:16:52 does storm require registrations? 14:17:09 and if so, does it send emails quickly? 14:17:27 and can anyone register, including people without .tpo address? 14:17:36 IIRC you can set the pad to be an open one. 14:17:40 aha! 14:17:46 can you do that for us? 14:18:46 I'm just trying 14:18:52 so, this pad is about writing "fact sheets" for our products. 14:19:14 where a product means something like virgil's roster, tomlurge's visionion, etc. 14:19:29 I don't know this visionion, but I love the name. 14:19:38 oh, thanks :) 14:19:39 for each product we would ask ourselves questions about scope, dependencies, design, operation, future planning, etc. 14:19:48 and soon there will be a fact sheet to find out more! ;) 14:20:12 the idea is to get a rough overview of what exists in this part of the tor ecosystem. 14:20:36 karsten: https://storm.torproject.org/shared/6_LHT814bdvcA6dti5YOQJftWR7pCqVk7ROVtxOb44m 14:20:42 maybe we'll find out that some pieces overlap heavily, or that we don't have anything in a certain area, etc. 14:20:50 This is editable by anyone who knows the URL. 14:21:06 cool, let's all log in. 14:21:15 thanks for setting it up, qbi! 14:21:22 np 14:22:28 okay, let's keep the chat here for our dear meetbot to notice. 14:22:50 regarding questions, 14:23:00 I wrote such a fact sheet with dgoulet a while ago. 14:23:13 I categorized those questions a bit and will paste them into the pad. 14:23:45 everyone, feel free to add products or questions. 14:24:07 how about we do that for 10 minutes or so? 14:24:15 (does this plan even make sense to anyone else?) 14:25:01 OK for /me 14:25:26 great! :) 14:31:59 starting network team meetting in #tor-dev now! 14:33:31 pad action is going quite well, should we give it another 5 minutes? 14:37:58 I am answering inline. Is that how the pad is meant? 14:38:24 not quite, but you're the best person to start writing that fact sheet, so that work won't get lost. 14:38:49 (the surprise will be that we'll all have homework after this meeting, and that will involve writing, err, something...) 14:39:06 ha! 14:40:01 so, we might need more input on the possible questions. 14:40:44 the quetions I pasted there were quite specific to dgoulet's hs health thing. 14:41:06 when you think about other products, what questions might we have? 14:41:20 now is a good time to ask them. well, to write them on the pad. 14:43:34 okay, people start making the pad prettier. shall we come back here? :D 14:44:11 virgil: should we move your question to our agenda item 4 and discuss it in a few minutes? 14:44:17 14:05:10 < karsten> 4. discussion, misc, whatever you call it. 14:44:19 (not now) 14:44:33 it is sufficiently pretty for me. If you leave it with me longer I'll start \LaTeXing it. Yes item 4. 14:44:58 great! (and +1 on LaTeX!) 14:45:24 removing that section from the pad. copied the question to a local editor for later. 14:45:37 so, 14:45:48 virgil: Go ahead. /me likes \LaTeXing :-) 14:45:54 I'm counting 20 products. 14:45:59 and we may still be missing a few. 14:46:04 hello i just heard about a measurement meeting going, and id like to watch :-) 14:46:12 welcome ohmygodel. 14:46:22 meetbot is listening, too, so you can read backlog later. 14:46:22 karsten: Error: "is" is not a valid command. 14:46:28 blah 14:46:31 ohmygodel: https://storm.torproject.org/shared/6_LHT814bdvcA6dti5YOQJftWR7pCqVk7ROVtxOb44m 14:46:32 super thx 14:47:09 how about each of us picks a product or three and starts writing a fact sheet for that until our next meeting? 14:47:36 these don't have to be perfect, and we'll probably learn during this process and come up with better questions. 14:47:40 but I guess we'll have to start somewhere. 14:48:05 karsten: hi sorry for the lateness to the meeting 14:48:11 hello hellais 14:48:16 I had some unexpected things to tend to 14:48:22 see my comment to ohmygodel for some context. 14:48:45 sure, no worries. good to see you here now. :) 14:49:07 so, how about we put names next to the products? 14:49:17 sounds good 14:49:19 where it's only allowed to write your own name. :) 14:49:30 I will update that document with some information later 14:49:35 you can put my name freely :) 14:49:36 neat! 14:50:31 we don't have to put a name next to all products for now, I'd say. 14:51:18 how about we write fact sheets on the same pad or on pads linked from this one? 14:51:19 does storm show edit ownership by line only? 14:51:34 it seems that someone can edit your text and not change attribution 14:52:11 it also doesn't show any colors. 14:52:17 could be a preference hidden somewhere? 14:53:40 * qbi looks 14:53:56 how does that plan sound? pick 1, 2, or 3 products now, write your name next to it like (fact sheet: $you), write such a document in the next 7 days either on this pad or on a pad linked from this one. 14:54:32 * karsten notices how short an hour can be.. 14:55:27 okay, sounds like everyone loves this plan and we can move on to the last agenda item 4. 14:55:30 ;) 14:55:32 14:05:10 < karsten> 4. discussion, misc, whatever you call it. 14:55:37 we have: 14:55:39 Onionoo: Virgil wants family-ids. I propose this as a stop-gap measure. Accept/reject? Discuss. https://trac.torproject.org/projects/tor/ticket/16599#ticket 14:56:01 I'm going to add: time for next meeting? does this weekday and time work for everyone? 14:56:03 anything else? 14:56:55 I think this time is ok 14:56:58 karsten, aagbsn: I don't see a config option to change the handling of colors etc. 14:57:26 qbi: ok. 14:57:41 Same time next week is OK for me. 14:57:48 it overlaps with the network group meeting, but that is convenient so I can observe both 14:57:50 same time is good by me. 14:58:12 I noticed some overlap, too. 14:58:17 if this works for people, great. 14:58:23 from reading the last minutes i got the impression that a lot of people are working on/with visualizations. made me a bit nervous if visionion is still relevant and/or has the right focus 14:58:30 time is good for me 14:58:40 karsten: Do we have a specific format for the factsheet? 14:59:21 qbi: see how dgoulet and I wrote the one for his tool. Q: A: newline, Q: A: newline. 14:59:29 there are certainly better formats, but re-formatting is easy. 14:59:36 pick the format you like most, I'd say. 14:59:51 tomlurge: I'm not at all concerned that we have too many visualizations. 15:00:23 tomlurge: there's a growing interest in visualizations. so I'd say don't worry about that. :) 15:00:24 * phew * 15:00:25 OK 15:00:40 i would love help from someone who is good at visualizations :) 15:00:50 virgil: we just crossed the 1-hour mark. let's talk about that ticket after the meeting? 15:00:59 sure 15:01:00 or to contribute to visionion 15:01:38 aagbsn: sure! let’s talk about that after this meeting 15:01:45 ok 15:01:52 okay, anything we should discuss before the meeting ends? 15:02:14 next meeting on july 22, 14:00 utc. will send another reminder next monday or tuesday. 15:03:10 great, ending this meeting. 15:03:12 #endmeeting