14:30:15 #startmeeting metrics team 14:30:15 Meeting started Thu Jun 15 14:30:15 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:50 https://pad.riseup.net/p/3M7VyrTVgjlF <- agenda pad 14:32:33 hi iwakeh! 14:32:38 Hi :-) 14:32:47 any more agenda items, or should we start? 14:33:04 jsut start and add if necessary later. 14:33:11 ok. 14:33:11 just 14:33:17 - collector webstats integration: #22428 (iwakeh) 14:33:37 I have all necessary old code and 14:33:56 log examples, but put more prio into working on metrics-lib 14:34:02 currently. 14:34:07 yep. 14:34:26 so, all other discussion will be on the ticket. 14:34:35 sounds good! 14:35:05 so, next? :) 14:35:08 sure. 14:35:12 - metrics-lib 1.9.0 and 2.0.0 releases (karsten) 14:35:16 2 weeks left. 14:35:26 days flow by ... 14:35:37 #22141 14:35:43 I think we're almost done there. 14:35:53 agreed 14:35:54 there's a tiny question in the comments. 14:36:02 and I'm testing locally, which looks good so far. 14:36:12 good to hear. 14:36:33 shall we go through the other tickets, too? 14:36:41 a moment. 14:36:50 comment:24 says 14:36:58 something related to collector 14:37:04 Is that for testing? 14:37:20 yes. 14:37:32 the sync part uses DescriptorReader. 14:37:43 ah, ok I'll look into that. 14:37:43 I briefly tried to update that, but I don't think I did it right. 14:37:54 the main question is: will it work with the new interface? 14:38:01 no need to write a clean patch now. 14:38:13 ok. 14:38:17 just confidence that we're not making this unnecessarily hard with #22141, which I sure hope we don't. 14:38:20 just test-code. 14:38:24 yep. 14:38:36 https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=%5EMetrics%2Fmetrics-lib&group=milestone&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority 14:38:59 should we go through the 1.9.0 tickets? 14:39:08 yes. 14:39:13 #16225 14:39:15 #19640 14:39:24 these fit together 14:39:26 I think we could do something there, as time permits. 14:39:31 after #22141. 14:39:40 but we don't have to. 14:39:44 true, I'm looking at 19640 14:40:01 yes. 14:40:05 and #17861 14:40:08 there are so many ways of restructuring and 14:40:11 heh 14:40:35 yes, and the new microdesc interface. 14:41:11 What date do we have for 1.9.0? 14:41:29 we have 2 weeks left for 2 releases. 14:41:35 in 1 week, maybe? 14:41:38 wed? 14:41:43 fine. 14:42:07 alright. 14:42:10 next one? 14:42:18 ok 14:42:24 #22139 might be fixed by #22141. 14:42:45 because we're skipping unparseable descriptors with that, rather than skipping the entire file. 14:43:01 good. 14:43:08 #22141 is almost done. 14:43:13 true. 14:43:13 #22196... 14:43:19 we could postpone that. 14:43:47 nothing urgent. 14:43:49 maybe depending on time. 14:44:00 true 14:44:01 but I feel we shouldn't squeeze anything in. 14:44:08 we already have a lot of changes. 14:44:22 #22583 should be quick, right? 14:44:24 yes and pretty large ones. 14:44:27 yep. 14:44:37 This could wait, too. 14:44:46 #22583 is very defined 14:44:57 and could be done any time. 14:45:02 sounds good. 14:45:19 Maybe, revisit the list for 190 on monday 14:45:22 that are all for 1.9.0. 14:45:25 yes, sounds good. 14:45:30 once we know how the testing goes. 14:45:47 mail is fine. 14:45:50 ok. 14:45:52 2.0.0? 14:45:58 fine 14:46:07 #19616 14:46:07 #19616, yep, should do. 14:46:22 what name? 14:46:29 #21932 should be relatively quick, because it's already prepared. 14:46:38 what name? hmmmmmm 14:46:39 all prepared. 14:46:55 and, what will be changed with the name? 14:46:59 today I thought about just dropping the DescripTor part and keep the metrics-lib part on its own. 14:47:10 hehe 14:47:17 But, true 14:47:42 but, I don't know. 14:47:50 just saying that we should have a decision in, well, 2 weeks. 14:48:03 Descriptor is very ambiguous 14:48:08 #22154 should be doable. 14:48:09 yep. 14:48:20 yes, that has to go in. 14:48:45 I think 2.0.0 is all set and prepared. 14:49:03 #22208 might be relatively easy if we just add partially recognized lines to the same list as entirely unrecognized ones. 14:49:17 yes, and #22295 is really easy. 14:49:36 I think 2.0.0 will be easier than 1.9.0. 14:49:46 there are hardly any changes affecting the tutorials. 14:49:51 yep. 14:49:54 right. 14:50:17 by the way, keeping a few well-defined tickets for volunteers might also make sense. 14:50:28 maybe somebody reads the blog post and wants to start hacking on something. 14:50:46 yes, 14:50:58 then I would make two tickets from 14:51:09 #22583 14:51:21 and remove from milestone? sure. 14:51:24 want to do that? 14:51:51 fine, but not 14:52:01 let this ticket dangle forever ;-) 14:52:08 hehe 14:52:24 okay! 14:52:26 blog post? 14:52:34 yep. 14:52:49 I'm currently collecting thoughts what could go into that. 14:52:54 I don't have a draft yet. 14:53:07 but once I have I'll share with you and stephanie and tommy. 14:53:11 Is that an official writer task? 14:53:20 right! 14:53:23 I think we'll get support from them. 14:53:44 it will be posted with 2.0.0? 14:53:57 Or shortly afterwards 14:53:57 yes. 14:54:00 in june. 14:54:13 I don't know the exact timing. 14:54:28 we might want to pre-release 2.0.0 a few days early and test it a lot. 14:54:38 to avoid a 2.0.1 one day after the blog post. 14:54:41 makes sense. 14:55:04 okay. 14:55:13 anything else re: metrics-lib? 14:55:19 nope. 14:55:29 anything else for this meeting? :) 14:55:35 neither :-) 14:55:41 whee! 26 minutes! 14:55:47 record time! 14:56:04 hehe. thanks, this was a good meeting! bye! 14:56:13 #endmeeting