13:59:36 #startmeeting Measurement Team 13:59:36 Meeting started Thu Oct 8 13:59:36 2015 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:46 hello, who is here for the measurement team meeting? 14:01:27 hi! me 14:01:34 hi tomlurge! 14:02:35 hi everyone 14:02:44 hi clv! 14:02:57 hi clv! 14:03:37 https://pad.riseup.net/p/pk94s9DbR0v3 <- agenda 14:04:42 please add more items if you want 14:06:30 okay, looks like we have some items. let's start. 14:06:35 thnks 14:06:46 1. Berlin team retrospective session 14:06:53 https://trac.torproject.org/projects/tor/wiki/org/meetings/2015SummerDevMeeting/MeasurementTeam 14:07:10 we had a session in berlin to talk about how the team thing worked out so far. 14:07:17 we came up with five suggestions. 14:07:32 maybe take a quick look, and I'll be quiet for 2 mins. 14:09:22 karsten: are you waiting for input? i sometimes don’t get how this IRC thing works :-/ 14:09:39 sure, feedback is great. 14:09:44 or we can go through the items one by one. 14:09:55 I was mostly waiting for you to read through them. 14:10:17 maybe let's go through the list one by one and see what you have to add. 14:10:25 1. team landing page. 14:10:33 what do you think? want to help? 14:10:55 Ok 14:11:01 okay. i read them :) 14:11:22 btw, we had this team landing page long ago: https://trac.torproject.org/projects/tor/wiki/doc/VegasTeam3 14:11:49 but we might as well start from scratch. 14:12:01 oups, now i get it … ahem, which wiki page? 14:12:06 oh! 14:12:11 https://trac.torproject.org/projects/tor/wiki/org/meetings/2015SummerDevMeeting/MeasurementTeam 14:13:35 okay, how about I start a new wiki page somewhere, and people add content to that? 14:14:22 karsten: yes, i think for you it’ll be much easier to begin it 14:14:31 ok. 14:14:39 added as action item to the agenda pad. 14:14:40 sure, i imagine the content would be something like the pdf report you did before berlin? 14:15:12 it would link to that report and add more stuff. 14:15:20 okay, will start something. 14:15:39 release early. release often :) 14:15:41 moving on to 2. analyze data, discuss findings, post to list, report in TWN. 14:15:47 okay 14:16:06 this is related to agenda item 3. new Hadoop/Spark/Drill server 14:16:12 I suggest we talk about that later. 14:16:42 it’s also related to what i try to achieve with visionion 14:16:52 it is! 14:17:22 i wasn’t very successful with collecting usecases in berlin, though 14:17:42 it didn’t seem like people have urgent questions that they need a visualization for to answer 14:17:47 it's difficult to think those things through theoretically. 14:18:11 you might have more luck presenting potentially interesting results and hear what other things people are interested in. 14:18:41 I'm certain that there are such things hidden in the data. 14:18:48 yeah, but … actual needs, burning questions?! sebastion had one, very concrete. but he was the only one 14:19:10 he probably has more if he thinks harder. ;) 14:19:50 after that success i pressed him to come up with more, but to no avail 14:20:15 let's try to answer that first question and ask again for more. 14:20:40 but let's move on to 3. 1-on-1 conversations. 14:20:57 and talk more about interesting visualizations later. 14:21:14 of course 14:21:38 so, I guess I'll ask people if they want to have a 1-on-1 conversation in the next weeks. it's totally optional, and I hope to have a better idea what to talk about than the weather soon. 14:22:03 but maybe it's useful. it could also be via IRC, or use higher-bandwidth media. 14:22:32 I'll reach out to folks (you, other regular attendees of these meetings, etc.). 14:22:51 does that make sense? 14:23:09 IMHO it shouldn’t be so optional. 14:23:29 rather the norm 14:23:59 well, pretty much everything is optional for volunteers. 14:24:15 but i’m not THAT experienced in team leadership. 14:24:32 I agree that we should totally try it and see how it works. 14:24:35 i mean it shouldn’t feel like: “we can talk if you really need help” 14:24:51 agreed. 14:25:55 in fact, good point. will make sure it won't sound like that. :) 14:26:04 i think it's a great idea btw 14:26:11 you were quite insistive that it would be good to take part in these meetings and for me that was helpful (you insisting AND taking part) 14:26:26 ah, good to know! 14:26:29 clv: great! 14:27:00 cool, added as action item. 14:27:12 on to 4. mailing list. 14:27:28 what do you think about creating a team mailing list? 14:27:46 totally pro 14:28:18 +1 14:28:44 I should talk to the other teams about this, but most people agreed that this would be a good idea. 14:29:07 so, adding another action item. 14:29:46 as a new member i must say i feel tor-dev and mostly tor-talk have a huge flow of information sometimes 14:30:03 same with irc channels, sometimes i don't get to read all the backlogs 14:30:12 :( 14:30:23 so divide and conquer sounds great 14:30:26 ^^i never even try… 14:30:27 yep. I'm not sure if adding new channels will solve that problem, 14:30:34 but I'm happy to try it. 14:30:39 it would be a public list, too. 14:31:04 but it would probably have less than a dozen people. 14:31:17 i’m working on a draft about that server. would love to send it around on a measurement list but wouldn’t dare on tor-dev 14:31:25 well, i'm not proposing to create new irc channels, just mentioning my POV 14:31:28 right, tomlurge. 14:31:41 clv: ah, by channels I also meant mailing lists. 14:32:04 tomlurge: I'm curious why wouldn't send this kind of stuff to tor-dev@ ? 14:32:07 okay, let's try it out (if other teams agree). 14:33:04 dgoulet: because the target audience is the tor-dev list and i dont want to spoil the surprise err use up the attention befor it’s ready. and i know that i can be chatty… 14:33:20 I see 14:33:27 thx 14:33:37 I can see how posting to the large tor-dev@ list with many smart people on it can be frightening at the beginning. 14:33:45 dgoulet: and tehre’s just tooo many people that i admire too much… 14:33:51 how was that for you in the beginning, dgoulet? 14:35:13 oh ah, it was stressful at first but it's not at all an aggressive mailing list like tor-talk@ could be 14:35:14 imo 14:35:27 oh, right. 14:35:33 tor-talk@ is a different challenge. 14:36:03 i agree, it never felt hostile or arrogant 14:36:11 and if anyone is mistaken on tor-dev@ for instance and someone call the person out, that's totally fine and that means *other* people were mistaken about the same thing so win-win 14:36:28 being wrong is totally OK, being irrelevant is something else :) 14:36:45 ;-) 14:37:01 well, the downside of moving to a small team list is that there are fewer smart people on it. 14:37:08 dgoulet: On reflection email lists add a '[tor-consensus-healt]' or other prefix to emails, so '[DocTor]' is redundant. In a couple days when I redirect it to bad-relays@ it'll have that prefix, so gonna drop the '[DocTor]' bit I added yesterday. 14:37:17 it could be used as staging area for posts that then go to tor-dev@. 14:37:47 but let's conclude the mailing list topic here. let's try it out. 14:38:06 moving to 5. communication between teams. 14:38:06 (sorry about intteruption) :) 14:38:13 thanks for interrupting, dgoulet! 14:39:05 I take 5 as feedback for something I should be doing better. 14:39:13 and I agree with it. 14:39:56 we had some trouble with meetings of team leads for various reasons: meeting time, audio quality, etc. 14:40:18 I hope we can resolve those issues soon. we talked about that in berlin, too. 14:40:33 and then I should report about what we talked about in our meetings here. 14:40:52 so, hope this will be better in the next couple of week.s 14:41:11 anything to add to 5? 14:41:17 to me that whole tor thing is still frighteningly big so having someone (karsten) giving me a “best of” from time to time would certainly be appreciated 14:41:32 heh, will try. 14:42:03 so, there are two more ideas for what we could improve: 14:42:08 I'll add them as 6 and 7 here. 14:42:19 6. switch to having irc meetings every two weeks instead of every week. 14:42:27 7. turn 1-1-1 task exchange into a tor-wide thing. 14:42:49 the idea behind 6 is that we'll move some of our discussions to mail, 14:43:00 and having an irc discussion every week is a lot. 14:43:19 it might prevent people from attending, and then we'll only have half of the team every week. 14:43:34 so the idea is to hold them every two weeks with (hopefully) more people. 14:43:39 how does that sound? 14:43:48 6 sounds reasonable (less people, mail) 14:43:50 (in combination with the mailing list maybe) 14:44:35 okay. 14:44:53 we can try this one as well and evaluate in 3 months. 14:45:18 so, 7, 14:45:37 the idea was to hold an irc meeting (weekly or every two weeks) for all tor folks, 14:45:55 exchange tasks like we did in the measurement team, 14:46:04 and put whatever is not taken on TWN. 14:46:16 that would allow new contributors to get into tor more easily. 14:46:23 TWN? 14:46:31 Tor Weekly News, the newsletter. 14:46:40 ‘kay 14:47:02 (just subscribed to it the other day) 14:47:07 once upon a time we specifically wrote easy tasks for TWN to be more attractive to new contributors. 14:47:22 but we stopped that because of the effort involved in that. 14:47:31 the new idea here is that these tasks will already be written. 14:48:22 so, another thing to try out, I think. 14:48:24 +1 to "new tasks already written" 14:48:50 what do you mean by “will already be written”? already published somewhere? or just well prepared? 14:48:50 toml: btw, here are some examples: https://etherpad.mozilla.org/O6TCKaTQ2j 14:49:26 tomlurge: well, people describe these tasks during that 1-1-1 session and hope that somebody else picks them up. 14:49:45 but if nobody bites during that session we can easily put them on TWN. 14:50:56 still, the idea would be that people notify the task owner that they're picking a task. 14:51:15 I guess we could use the wiki for that. 14:51:20 well, not sure yet. 14:51:34 something to figure out in the first tor-wide 1-1-1 meeting. :) 14:52:03 aaand, we almost spend the entire meeting on agenda item 1. 14:52:08 spent* 14:52:13 ok. i can imagine myself picking up a CSS task and hiding from c++ 14:52:29 sure, that would be totally up to you. 14:52:54 are we allowed to elongate the meeting? 14:53:20 I think we shouldn't. or at least not by more than 5. 14:53:28 let's move on, okay? 14:53:36 ky 14:53:41 2. Berlin 12-month roadmap 14:53:50 https://trac.torproject.org/projects/tor/wiki/org/meetings/2015SummerDevMeeting/Roadmap/Measurements 14:53:58 no need to talk about that now. 14:54:06 it's what we came up with in Berlin. 14:54:29 it took about an hour to make that roadmap, and it's not really complete. 14:54:34 or realistic. 14:54:41 but it's a start. 14:54:54 I'd say send me additions/corrections to that roadmap if you have any. 14:55:01 or hey, it's a wiki! 14:55:33 please add/edit to reflect your measurement-related tasks. 14:55:54 maybe ping me after adding something. 14:56:24 I'm thinking about adding those items to the roadmap PDF in a week or so and call that done. 14:56:48 will add visionion, globe+atlas integration into visionion, analytics server and metrics website 14:57:01 sounds great, please do! 14:57:44 clv: feel free to do the same for erebus. 14:58:00 moving on... 14:58:03 3. new Hadoop/Spark/Drill server 14:58:17 tomlurge: want to describe that? 14:58:37 like, give a 2-minute introduction? :) 14:59:05 yeah: we are settig up a server with all raw metrics data on it (disk space permitting,at least the last 2 years or so) 14:59:42 we install some big data analytics tools on it like Spark and Drill, all in a Hadoop environment 15:00:03 teh aim is to make it easy for people to dive into the data and check stuff out 15:00:11 woa! +9000 15:00:20 without having to set up their own analytics framework on their poor laptop 15:00:34 finished 15:00:35 and we're adding users per request. 15:00:46 sounds like dgoulet would be one of them. 15:00:52 :D 15:00:54 I also think that phw would be interested. 15:01:04 and Sebastian maybe. 15:01:26 tomlurge: this is the email you're planning to send to tor-dev@, right? 15:01:28 cool. we will have to keep an eye on disk space usage and teh like though 15:01:51 yep, that’s the mail. it’s practically ready 15:01:52 well, 2x240G + 2x2T is plenty. ;) 15:02:13 cool! 15:02:14 karsten: we’ll see… :) 15:02:43 okay, last item is 4. parsing lib comparison 15:02:57 that's something atagar and I came up with in berlin. 15:03:12 we're planning to compare metrics-lib and Stem wrt. capabilities and performance. 15:03:21 we sent mail to tor-dev@ about that. 15:03:41 a side effect of this plan is that we're going to team up on metrics-lib and then Stem for this. 15:03:50 rather than him working on Stem and me working on metrics-lib. 15:04:09 that's a pattern we should try out for other tools, too. 15:04:36 well, depending on whether we're still happy with how this goes afterwards. ;) 15:04:46 that's 5 minutes over time now. 15:04:52 should we conclude the meeting here? 15:05:31 pasting action items for the log: 15:05:36 - karsten: Create team landing wiki page, invite others to add content. 15:05:36 - karsten: Invite team members to 1-on-1 conversations (blocking on input from Tom). 15:05:38 - karsten: Talk to other teams about creating team lists, then ask for one for the measurement team. 15:05:41 - tomlurge: Add visionion, globe+atlas integration into visionion, analytics server and metrics website to the roadmap wiki. 15:05:44 and adding one more: 15:05:54 - tomlurge: Send out mail about mteam server to tor-dev@. 15:06:00 anything missing there? 15:06:43 otherwise I'll end the meeting in 5, 4, 3, .... 15:06:49 erebus? 15:07:03 that's clv's relay monitor. 15:07:07 didn’t cvl want to add that to the wiki? 15:07:17 where? 15:07:30 ah! 15:07:31 roadmap 15:07:34 Erebus 1.0 release - atagar 15:07:39 there's that for october 2016. 15:07:48 ah, okay, sorry 15:07:51 of course, clv might want to edit that. 15:08:02 - clv: Possibly edit the roadmap wiki wrt. erebus. 15:08:03 there, 15:08:04 yeah, taliking with atagar about it 15:08:21 cool! 15:08:30 2, 1... 15:08:31 #endmeeting