14:29:33 #startmeeting metrics team 14:29:33 Meeting started Thu Jul 13 14:29:33 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:41 https://pad.riseup.net/p/PDvVmllKcUFD <- agenda pad 14:30:24 ! 14:30:36 hi isabela! 14:30:55 just lurking and wondering if you saw the final report email 14:30:58 :) 14:31:23 yes, I did. skimmed it. looks like work. :) 14:31:28 lol 14:31:32 indeed 14:31:41 is there a due date? 14:31:45 not really 14:32:02 but of course, would be nice to it in like 2 weeks or something 14:32:15 yes. 14:32:20 i was wondering about that 14:32:26 i want to check if that sounds ok for gerv 14:32:34 hi there! 14:32:37 oi! 14:32:44 sorry for hijacking your meeting :) 14:32:48 hi iwakeh! 14:32:53 no worries at all, isabela! 14:33:09 should we briefly talk about those 2 weeks, before you go and ask? 14:33:18 yes 14:33:21 that would be nice 14:33:36 put on the top of the agenda. 14:33:46 cool 14:34:37 alrigt so you want to consume my email ? 14:35:02 ah, give us a few minutes to build the agenda. 14:35:10 sorry 14:35:13 hehe 14:35:24 * isabela goes get another coffee! 14:37:15 okay, I can't think of more agenda items needing immediate attention today. 14:37:22 looks complete. 14:37:25 shall we start with the MOSS topic? 14:37:32 yep. 14:37:51 did you read the message? 14:37:54 (I'm still reading..) 14:38:04 I see, they'd like a nice final report, more informally. 14:38:15 praise and publicity. 14:38:28 which is fully justified. 14:38:53 okay. makes sense. 14:39:09 Maybe, isabela could put together the monthly 14:39:11 I wonder how many pages they expect. 14:39:24 reports and then we make it a new yearly one. 14:39:34 doesn't matter. 14:39:37 i dont think they want us to go crazy 14:39:40 it should be useful. 14:39:46 they want us to just answer things 14:40:08 some answers will be shorter than others 14:40:17 Most we already answered in the initial proposal and the monthly reps, I think. 14:40:20 but i dont think this is as formal as 'have xx pages of report' 14:40:28 yes 14:40:30 * iwakeh agrees. 14:40:34 I'm thinking that less is more. 14:40:40 always :-) 14:40:56 i think what matters is honesty and good examples of impact :) 14:41:04 true. 14:41:32 okay, so the plan is to start a google doc? 14:41:39 (there's a template?) 14:41:40 so my suggestion is to start by organizing information that will help answer questions in a doc 14:41:51 sounds good. 14:42:02 like i can link to reports, or the original proposal 14:42:36 i would say 2 weeks for this should be fine 14:42:43 but i might not include the blog post on that not sure 14:42:51 should we set a date for "first round of thoughts added to the doc"? 14:43:06 maybe say, we will write after the report is done 14:43:26 karsten: maybe monday EOD? I will be travelling that day but could do some work on friday 14:43:27 sounds good. ideally, we'll reuse parts from the report. 14:43:33 karsten: yes 14:43:55 monday EOD works for me. 14:44:08 alrigt 14:44:11 alright 14:44:12 :) 14:44:19 iwakeh: you cool? 14:44:28 isabela: can you start a doc? 14:44:32 yes sir 14:44:32 then we'll have a better overview how long it could take in total. 14:44:35 with the template? 14:44:42 yes 14:44:45 fancy fancy 14:44:55 sounds good! :) 14:44:55 hehe 14:45:28 isabela: yes, that all sound like a plan. 14:45:56 okay. moving on? 14:46:03 * isabela out of your meeting o/ 14:46:04 isabela: thanks! 14:46:14 bye isa! 14:46:18 ah, shall we warn/inform others? 14:46:28 whom? 14:46:30 like, tommy? 14:46:32 about what? 14:46:36 ah! 14:46:39 sure 14:46:39 that we might need their help. 14:46:47 i will do it 14:46:51 yes, definitely. 14:46:51 thanks! 14:46:56 he has a couple of deadlines going on till july 24th 14:47:03 so he can jump in on this after that 14:47:07 might be more sane for him :) 14:47:10 hehe 14:47:12 sounds good! 14:47:26 okay, next topic: 14:47:30 - CollecTor 1.2.0 release/deployment 14:47:38 it's still running on corsicum. 14:47:40 released and announced. 14:47:44 ok. 14:47:45 yes and yes. 14:48:02 I don't expect it to explode at this point anymore, but it might explode on colchi. 14:48:03 maybe, corsicum should do more? 14:48:20 hmm, you mean as backup + testing in one? 14:48:29 to see all modules working? 14:48:38 yes, for the moment. 14:48:45 maybe. 14:48:55 we could let it collect more things but not sync them. 14:48:59 it is not really visible. 14:49:15 corsi could sync from colchi 14:49:30 like, sync bridgedescs from colchi, download exitlists, download onionperf. 14:49:48 sounds good to me. 14:49:56 do you want to make that change? 14:50:16 and if it survives the weekend we update colchi? 14:50:17 oh, true. I could do that :-) 14:51:03 also sync relay descs etc? 14:51:44 answered on the pad. 14:51:46 ah, no. 14:51:52 all fine. 14:51:55 because colchicifolium syncs from corsicum. 14:51:58 circles. 14:52:13 no problem, 14:52:13 let's leave relaydescs unchanged. 14:52:25 ok. 14:52:29 that already happened with the old mirrors. 14:52:47 but, let's avoid circles for now. 14:52:59 okay. :) 14:53:11 alright, moving on? 14:53:15 yep. 14:53:20 - CollecTor 1.3.0 planning 14:53:55 https://trac.torproject.org/projects/tor/query?group=status&milestone=CollecTor+1.3.0 14:54:29 what are the overall goals for that release? 14:54:41 not speaking of tickets yet. 14:54:48 Add more syncs and 14:55:12 what syncs are missing? 14:55:17 use the persist-functionality as much as possible reducing code. 14:55:18 as in, needed but not present? 14:55:25 onionperf 14:55:28 webstats 14:55:45 this is not much effort. 14:55:56 okay, but is that a priority? 14:55:57 onionperf is already there for review. 14:56:01 okay. 14:56:06 not saying we shouldn't do it. 14:56:10 but what are the priorities? 14:56:20 webstats in the first place, I guess. 14:56:25 like, download + sanitize. 14:56:29 yes, and then use the persist-functionality 14:56:37 as part of that, okay. 14:56:43 as much as possible to only have very few places for 14:56:48 adding descs. 14:57:15 right. it sucks to touch many places in the code for a single thing. 14:57:37 true. 14:57:44 that's webstats. 14:57:54 Some questions will come up, like on the onionperf ticket. 14:57:56 other than that: bridge descs. 14:58:11 ah, ok? 14:58:16 rehi 14:58:25 hi nickm! 14:58:52 hi! 14:59:00 iwakeh: that's based on my plan to reprocess bridge descriptors next month or so. 14:59:11 ok. 14:59:20 keep contact lines, put in bridge auth fingerprints, maybe do other things. 14:59:30 which needs discussion and then code. 14:59:37 true. 14:59:55 I mean, we could also leave that for 1.4.0 and try to get out 1.3.0 with only webstats things. 15:00:06 actually, good timing to simplify the storing functionality. 15:00:20 and do the discussion in parallel. 15:00:33 let's see how the discussion starts and 15:00:56 then we have a better idea how much coding that will be (next week). 15:01:09 yes. 15:01:20 related to that, would you want to review #22827? 15:01:28 sure. 15:01:48 that might also help in finding things that need more/less/different sanitizing. 15:02:08 just the txt? 15:02:12 sure. 15:02:33 by the way, it was really helpful to write that document. 15:02:43 yes, 15:02:56 I was quite certain that we're sanitizing fingerprints in a different way, and when I looked that up just to be sure, ... well... :) 15:03:03 the specification is important. that's why it is done first usually ;-) 15:03:15 there is one! on the website. 15:03:24 but yeah. 15:03:30 true. 15:04:27 okay. 15:04:34 anything missing on the pad that we concluded today? 15:04:40 anything else that needs discussion? 15:04:50 anything from tickets that we can quickly discuss now? 15:04:57 * iwakeh thinking... 15:05:57 maybe, take a look at #21759 next (when you have time) 15:06:08 other than that we covered all. 15:06:15 will do right after this meeting. 15:06:28 thanks! 15:07:03 okay. anything else? 15:07:08 all fine. 15:07:28 maybe, 15:07:34 yes? :) 15:07:50 metrics-lib test for #22912 :-) 15:07:59 ah. 15:08:24 I can look, but maybe not today anymore. (next meeting in ~20.) 15:08:33 that will catch any future issue like that. 15:08:41 no hurry, the fix works. 15:08:55 okay. 15:09:19 that ought to be all :-) 15:09:29 alright, back to asynchronous? 15:09:44 yup 15:09:52 great! thanks and bye! 15:10:00 #endmeeting