14:29:31 #startmeeting metrics team 14:29:31 Meeting started Thu Sep 7 14:29:31 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:47 we have a long list on the agenda pad.. 14:30:02 true 14:30:06 https://storm.torproject.org/shared/Ou-1QRctynWbF4yedi-MfDsjImFMFSIEP20fbVGCPRa 14:30:21 shall we just start? 14:30:42 sure. 14:30:53 * oo-hetzner-03, rotation or new primary (karsten) 14:31:01 I didn't look at munin today, 14:31:13 but is it still the case that most requests go to oo-hetzner-03 and not to the other hosts? 14:31:13 seems the same. 14:31:33 is hetzner much more capable? 14:31:38 hmm. any idea how oo-hetzner-03 can handle all the requests that the ... hehe 14:31:47 I don't know. 14:32:07 alright, I think we need to ask the admins. 14:32:10 who does this? 14:32:17 you :-) 14:32:21 ok. 14:32:30 as you made initial ticket here. 14:32:40 yep. 14:32:46 next topic? 14:32:52 yep 14:32:55 * Web server logs specification #23243 (iwakeh, karsten) 14:33:02 I didn't look at the ticket in the last 45 minutes. :) 14:33:04 gettin' there 14:33:09 all answered. 14:33:13 anything that is faster to discuss here? ok. 14:33:23 nope 14:33:30 in that case we can leave it on trac. 14:33:31 * iwakeh was in the pad window. 14:33:58 hmm? 14:34:07 ? 14:34:13 what was in the pad window? 14:34:25 Oh, my initial 'nope' from above. 14:34:31 all fine now. 14:34:31 ah! :) 14:34:46 next topic? 14:34:58 yep 14:35:00 * Input for proposal 280 PrivCount discussion (iwakeh) 14:35:06 preparing input for the end of this week, we could go over it beginning next week (before Sep 13) 14:35:09 (pasting from the pad) 14:35:15 sounds great to me. 14:35:31 good. 14:35:35 another topic solved :-) 14:35:41 we'll need to be done by sep 12 evening, right? 14:35:53 it's sep 13 in the early, early, early morning. 14:36:05 I think so , yes. 14:36:12 2am cest 14:36:14 by the way, I think it's very unrealistic that I can make that time. 14:36:36 I pondered it, but I don't see how it would work. 14:36:39 maybe, we only end up with few discussion points. 14:36:48 right. 14:37:01 alright, next topic: 14:37:07 * Salted IP hashes (iwakeh): still waiting for a reply (wrote about setup Aug 18, ping Sep 4). 14:37:18 and, if there is something serious we have another meeting, anyway. 14:37:23 true. 14:37:41 so, sep 4 is a few days ago, how about I do another ping next week? 14:37:43 waiting, but 14:37:48 yes? 14:38:03 currently is some holiday in USA? 14:38:12 yes, ping again then. 14:38:19 is it? I don't know. 14:38:49 ok. 14:38:57 next one? (we're fast!) 14:39:03 * New releases for Java 8 (iwakeh): 14:39:18 yep. 14:39:22 Now, having metrics-lib fixed on 1.7 14:39:41 we can just release when the tickets are done, i.e., 14:39:50 no hurry b/c of J8. 14:39:56 okay. 14:40:11 works for me. 14:40:16 Only after releasing j8 14:40:36 the work for finally using the new features starts. 14:40:51 yes. 14:41:25 6 14:41:29 (sorry) 14:41:45 okay, moving on. 14:41:50 * Tor Metrics website logo and style guide #23383 (karsten) 14:41:51 fine 14:42:07 I noticed that. 14:42:45 just saw the new comment from linda there. 14:43:29 * linda lurks 14:43:36 hi! :) 14:43:37 hi linda! 14:43:39 :D 14:43:41 o/ 14:43:55 sounds reasonable to me. 14:44:19 to me, too. 14:44:29 cool! 14:44:36 I can move that forward then. 14:44:39 +1 14:44:42 +1 14:44:49 another problem solved. :) 14:44:54 hehe 14:45:16 great. thanks, linda! :) 14:45:24 o/ 14:45:31 thanks! 14:45:51 next topic: * End-of-September meeting: when, how long, where, who? (karsten) 14:46:03 (afk for .5 min) 14:46:33 so, 14:46:42 when == end of september, roughly. 14:46:44 (paper calendar) 14:46:57 ah, hmm, good idea. afk for .5 min... ;) 14:47:14 Sep 28 14:47:20 a Thursday. 14:48:38 maybe we should talk about "how long" first. 14:48:49 is 1 day a good duration? 14:48:58 yes, seems fine. 14:49:43 sep 28 looks empty in this paper calendar, but I'll have to check. 14:49:53 maybe tue sep 26 as alternative? 14:50:02 also fine. 14:50:20 okay, let me check that here and then get back to you afterwards. 14:50:26 and to irl. 14:50:38 anybody else we should ask? 14:50:52 not that I'm aware of. 14:51:05 ok. 14:51:07 where? 14:51:18 I'd have to check whether the onionspace is available. 14:51:22 as in district of berlin? 14:51:27 :-) 14:51:37 as in meeting location. 14:51:39 :) 14:51:44 there are plenty here. 14:52:01 we had a meeting in betahaus a few years back. 14:52:21 ah, i think such meeting could also happen in c-base. 14:52:59 how about I ask for onionspace availability first, and just in case that's not available, we look for alternatives? 14:53:06 yep. 14:53:08 3 people, 1 day shouldn't be too difficult. 14:53:13 true. 14:54:12 okay. 14:54:17 next topic? 14:54:24 fine 14:54:29 * Split ExoneraTor into query.json and JSP frontend, revised ExoneraTor branch #16596 (karsten) 14:54:54 this topic and the next few ones are mostly a reminder that these tickets still need review. :) 14:55:00 oh, 14:55:10 that must have been during the trac outage. 14:55:10 maybe there are parts that we can quickly discuss now to make the review easier. 14:55:20 oh, trac.. 14:55:41 so, the next four topics are in that category. 14:55:48 I see many 'fixed'. 14:56:06 yes, I fixed a few things there. 14:56:33 Then I just try to review this today or tomorrow. 14:56:56 #16596, right? 14:57:07 * iwakeh notices the earlier comment now 14:59:19 do you want to look at these four after the meeting and see which of them you can review or which you can't because you need more information from me? 14:59:32 From glancing over it, I don't see a huge discussion. I'll just review again. 14:59:44 the other three being #22836, #23391, and #23285. 15:00:09 (where #23285 doesn't need code review yet, but input on the idea.) 15:01:23 ah, 22836 is owned by karsten, which results in a very lonely discussion. I cc myself. 15:01:35 oh, heh. 15:02:32 okay. should we keep the rest on trac? 15:02:37 yes. 15:02:38 (of these four topics?) 15:02:39 ok. 15:02:51 last topic for today (unless we come up with more): 15:02:54 * Trac housekeeping thread on metrics-team@ (karsten) 15:03:08 did you see that thread? 15:03:12 some thing already happened there. 15:03:16 yes! 15:03:16 yes. 15:03:33 my hope is that we can resolve a couple more tickets just by asking people whether they still care. 15:04:02 And, very ancient tickets could be batch-closed? 15:04:23 probably. 15:04:29 Stating: this should be re-opened if important. 15:04:30 though let's do that as step 2. 15:04:38 true. 15:04:57 I also started to look 15:05:16 I think as step 1 I'd like to ask the network team folks whether they still care about the many analysis tickets. 15:05:20 through tickets and resolve or close or add a milestone. 15:05:31 sounds good! 15:05:48 true, the analysis is mostly for core-tor 15:05:54 yep! 15:06:38 ok. 15:07:00 anything else on this topic or on other topics? 15:07:13 13 / 37 min -> record. 15:07:20 haha 15:07:46 let's wait another 2 minutes to make that 3.0 per item. 15:07:47 no, I'm already coding 15:07:55 cool! 15:07:59 the webstats changes following from the spec 15:08:11 that's why these funny questions come up there. 15:08:29 The big issues seem to be resolved. 15:08:36 those questions are important. 15:08:45 Only the devilish details ;-) 15:08:49 yep. 15:09:14 alright, all discussed! 15:09:19 39 steps 15:09:28 minutes ;-) 15:09:44 ! more via trac/email then. bye, bye! :) 15:09:51 bye bye! 15:09:54 #endmeeting