14:31:04 #startmeeting metrics team 14:31:04 Meeting started Thu Jun 1 14:31:04 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:04 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:11 https://pad.riseup.net/p/3M7VyrTVgjlF <- agenda pad 14:31:46 shall we wait or just start? 14:31:58 let's wait just 2 minutes or so. 14:32:00 ok 14:32:15 Hi there! 14:32:20 hi 14:32:43 we're waiting another minute or so and adding things to the pad. 14:32:50 sure. 14:34:05 okay, let's start? 14:34:09 - Atlas 1.0 (irl) 14:34:53 ok, so, i've been distracted with many things and i don't think we're any closer to a plan for the first release of atlas 14:35:12 but i do like karsten's suggestion that we use the same release process as other metrics team things, like metrics-lib 14:35:23 cool. 14:35:26 and i've been working on merging patches as they've appeared, so we don't have a large backlog 14:35:35 i think there are 6 patches i need to review at the moment 14:35:57 speaking of patches, do you want to include an item in the monthly report? 14:36:21 there weren't any big changes this month afair 14:36:31 ok. 14:36:42 we can say that there have been incremental updates or something like this 14:36:47 just one sentence 14:37:30 hmm, not sure if that helps. 14:37:42 there have been incremental updates to other code bases, too. 14:37:56 if it's normally not mentioned, then i would leave it out this month 14:38:01 Usually we try to only include finished things. 14:38:05 yep, that's fine 14:38:10 okay. 14:38:41 cool. please bring up the release plan again when there are fewer distractions. 14:38:48 will do 14:39:09 great! shall we move on? 14:39:16 yep 14:39:23 - webstats migration to CollecTor: sync or not to sync? (iwakeh) 14:39:43 I lean towards not sync. 14:39:53 hmm, 14:39:57 why not? 14:40:00 sync is most important for relay descriptors where we'd lose data if an instance fails. 14:40:15 mostly because of the added effort. if it's easy, sure, put it in. 14:40:24 Well, but we the web-stats will be important, too. 14:40:33 but we'll likely only have a single collector instance scrubbing webstats. 14:40:44 And, third party operators might be interested. 14:40:47 and if that fails for a few days, it will just catch up, right? 14:41:07 will it? 14:41:41 how does the current webstats host get its data? 14:41:48 These logs are quite interesting and the sync-functionality is not too complicated anymore. 14:42:05 folders. 14:42:13 file-system 14:42:24 as far as the code says. 14:42:25 yes, but how do the original logs find their way to the host? 14:42:28 rsync? 14:42:41 anyway, details. 14:42:51 just saying that sync will not be as critical as for relaydescs. 14:43:02 where being offline for an hour means missing a consensus and nine votes. 14:43:06 true, if anything unforseen makes it 14:43:14 more complicated I'll drop it. 14:43:19 sounds good. 14:43:33 I also sent you sample data. 14:43:38 original data. 14:43:45 sanitized logs are on webstats.tpo. 14:43:47 cool :-) 14:43:55 it just arrived 14:44:02 great! 14:44:06 I have these. 14:44:15 the clean ones. 14:44:24 that's all here. 14:44:26 okay. 14:44:38 moving on then? 14:44:43 sure. 14:44:48 - Collecting input for monthly report (karsten) 14:44:52 this time of the month again. 14:45:02 I started putting some items on the pad. 14:45:10 Switch there? 14:45:12 but I didn't go through my inbox or trac yet. 14:45:22 sure, we can briefly switch to the pad. 14:45:34 * karsten puts on elevator music here.. 14:45:40 hehe 14:45:52 there are ascii notes 14:46:17 nice! :) 14:46:27 ♩♩♩♬ 14:46:43 :-) 14:46:43 (for the elevator music) 14:46:50 sorry if i crashed anyone's irc client 14:47:05 ah, you didn't. just looked confused: ???? ;) 14:47:16 makes a strange sound ... 14:47:21 heh 14:52:16 #music off 14:52:17 music off. 14:52:23 okay! 14:52:24 you were faster. 14:52:27 heh 14:52:35 next item? 14:52:47 yes. 14:52:51 - metrics-lib 1.8.0/1.9.0 release 14:53:19 see the large patch I dropped on trac yesterday night. 14:53:34 yes, trying to read through ... 14:53:46 GeKo: I'm back. Is there anything you'd like me to focus on right now? 14:54:10 https://trac.torproject.org/projects/tor/query?milestone=^metrics-lib+1.8.0&or&milestone=^metrics-lib+1.9.0 14:54:35 should we go through that list at some point? 14:54:48 https://trac.torproject.org/projects/tor/query?milestone=^metrics-lib+1.8.0&or&milestone=^metrics-lib+1.9.0&group=milestone&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority 14:54:55 group by milestone 14:55:21 Maybe, just see how much is done 14:55:29 next week, Monday? 14:55:45 sounds good! 14:56:06 By mail? 14:56:27 or shall we have a quick meeting on monday just for this? 30 min? 14:56:36 sure. 14:56:42 14:30 utc? 14:57:10 Monday is Pentacostl (pfingsten). 14:57:20 oh. 14:57:21 Tuesday? 14:57:31 arthuredelstein: see backlog in #tor-project as there is a meeting here 14:57:42 that's close to the planned release date on wednesday. 14:57:43 same time? 14:57:50 shall we try email first then? 14:57:51 or earlier. 14:57:57 yes, all fine. 14:58:04 okay! 14:58:17 I'll try to check 14:58:40 great! 14:58:45 if tasks are clearly in mine or your 'field'. 14:58:55 By Friday. 14:59:27 okay. 14:59:39 anything else for today? 14:59:47 I'm fine. 15:00:35 okay. 30 minutes for the weekly meeting. great! let's talk more next week! 15:00:39 bye, bye! 15:00:49 (and via email/tract) 15:00:51 trac* 15:00:55 bye, bye. :-) 15:01:03 #endmeeting