13:59:12 #startmeeting metrics team 13:59:12 Meeting started Thu Apr 7 13:59:12 2016 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:14 hi there! 13:59:17 yay, hi there 13:59:25 hi iwakeh and Letty! 13:59:28 hi there! 13:59:46 hi oma formerly known as thms! 13:59:55 * qbi is also here, but probably not for the whole meeting. 14:00:00 new quarter new nick? ;) 14:00:03 hi qbi! 14:00:12 karsten: no, this is it! 14:00:23 unti next quarter :) 14:00:29 i swear!! 14:00:42 and I'm currently listening to Letty. :-)) 14:00:53 https://pad.riseup.net/p/zUNzEIFRq5S4 14:01:00 oops..^^i hope you have fun 14:01:01 ^ agenda pad 14:01:48 please add items to the agenda 14:03:42 okay, let's start with the items on that list. but feel free to append more items during this meeting. 14:03:47 * Meeting time and frequency (karsten) 14:04:02 we decided on the meeting schedule, every other week, six months ago. 14:04:11 and we picked the meeting time back then. 14:04:34 does this still work for everybody, or should we find a better time and/or frequency? 14:05:01 no need to decide right now, but I could imagine starting a doodle for this and collect opinions over the next week or so. 14:05:04 time is ok, but i'll have to leave at 15:00UTC, usually 14:05:18 for me both works 14:05:26 that would work, we should try to keep these at 60 mins max. 14:05:31 works for me too 14:05:52 frequency (bi-weekly) is ok 14:06:07 Well, this is a time where I usually have to work. 14:06:14 So quite often I'm distracted by work. ;) 14:06:27 when would be a better time? 2 hours later? 14:06:50 not for me, i often work offline at that time 14:06:53 which would collide with iwakeh's requirement to leave in 1 hour from now. but maybe it would work on another day. 14:07:01 ok. 14:07:21 wednesday 14:07:41 should we do a doodle, and maybe the result is to keep the date and time unchanged? 14:08:07 and maybe we find a time that works similarly well or even better for everyone? 14:08:20 A time later than 1900 UTC would be fine for me and also a time between 0700 and 1000 UTC would work. 14:08:40 However if this doesn't work for anyone else, it's fine. 14:08:47 maybe the doodle would be a good idea 14:08:51 ok! 14:09:00 will do, after the meeting. 14:09:11 * Valencia roadmap (karsten) 14:09:27 the pad has the updated Valencia roadmap. 14:09:34 which is also on the trac wiki page. 14:09:39 we should update that every now and then. 14:09:55 how about we update the items that are due in march (oops) and april? 14:10:10 we can also add new items, of course. 14:10:35 I'll copy the output back to the wiki page after the meeting. 14:12:04 oma, Letty: want to update your items? 14:12:17 iwakeh: want to adopt "Make CollecTor more robust against data loss" ? 14:12:36 yes, was about to suggest that 14:12:51 great. feel free to just put in your name or even split it up into more items as needed. 14:13:13 karsten: i added just my name. and adjust the date next time. 14:13:28 sure. 14:14:32 I’m hopelessly behind already. First vacation, now refactoring the converter (and another vacation coming up soon…) 14:14:45 sounds stressful. ;) 14:14:50 :D 14:14:57 you have no idea ;-) 14:16:31 iwakeh: I should have explained the format: it's "sentence starting with a verb; task owner(s); date in YYYY-MM-DD format" 14:16:58 no ellipses, ok ;-) 14:17:05 maybe I should add a sentence for that to the wiki page. 14:18:01 and the timeframe. i.e. the end time is missing :-) 14:19:01 when we created the first version of this roadmap we picked dates rather arbitrarily. 14:19:22 it was a session of 45 minutes, and we were glad to identify tasks we'd like to put on that roadmap. 14:19:35 * qbi disappears. 14:19:56 but the idea was that we would make these dates more precise when revisiting this roadmap every few weeks. 14:20:01 bye, qbi! 14:20:43 morning 14:21:03 okay, I'd say let's move on, or we're running out of time before running out of topics. 14:21:06 hi nickm! 14:21:25 * Discontinuing Weather (karsten) 14:21:31 (whoops, sorry for interruption. carry on.) 14:21:48 I'm briefly bringing this up here, because we counted Weather as part of the metrics space. 14:22:09 it's unmaintained for years now, and all previous attempts to find a maintainer failed. 14:22:21 that's why I kinda took it offline this week. 14:22:58 ah, weather was a email notification service to get notified when your relay goes down or earns you a t-shirt. 14:23:20 so, the link to subscribe to weather is now gone, and new welcome messages are not sent out anymore. 14:23:35 the plan is to remove it in july. 14:24:09 that's all about that topic, I'd say. 14:24:16 now, let me re-arrange two items on the agenda: 14:24:31 * CollecTor improvement project (iwakeh) 14:24:46 what we missed was doing an introduction. 14:24:48 yes, started the central wiki page https://trac.torproject.org/projects/tor/wiki/doc/CollecTor/Improvements 14:24:59 and am busy creating issues for the tasks necessary for the different goals. 14:25:14 and, the next topic is probably part 14:25:41 of what i suggested as a place for the project guidelines. 14:26:03 yep :) but regarding this project, 14:26:16 I think we're doing quite okay with using Trac tickets for discussions, 14:26:31 except that it's probably news for people here that you're working on this project. (my guess) 14:26:48 would you want to introduce your project on the mailing list at some point? 14:26:59 I'd bet people are very curious. 14:27:00 that's on my agenda, 14:27:20 i just wanted to have the first meeting here. 14:27:25 ok, cool! 14:27:36 still wandering, 14:28:02 if i should or shouldn't cross-post to tor-dev and metrics-team lists? 14:28:20 ah, cross posting... 14:28:32 I think tor-dev@ is fine for this introduction. 14:28:43 everyone on metrics-team should also be on tor-dev. 14:29:12 i guess so too. 14:29:34 this may be different for discussions of single aspects of collector. 14:29:53 but announcing this project is very likely interesting for non-metrics-team members, too. 14:31:22 btw, oma, you'll be interested in the upcoming metrics-lib changes. 14:31:36 which are partly a result of iwakeh working on collector. 14:31:46 changes =[ 14:31:49 iwakeh: do you have the ticket number for 2.0.0? 14:31:56 good changes :-) 14:31:57 improvements! 14:32:05 a second 14:32:18 still changes =8-[ 14:32:22 let me also add a roadmap item for that. 14:32:32 #18746 14:32:42 ah, you can easily stick with 1.1.0 if you'd rather not want to upgrade yet. 14:33:10 you'd feel even older though. ;) 14:33:40 version 2! what have you done?! 14:33:43 okay, looking forward to the project announcement! 14:33:48 heh 14:33:52 * metrics-team Git repository (karsten) 14:34:07 yes! 14:34:07 or maybe that should say (iwakeh), because it was really you suggesting that. 14:34:27 well, we have these guide docs in many 14:35:02 different projects like Onionoo, metrics-lib, metrics-db ... and those i don't know yet 14:35:20 and some of these docs generally relate to contributing or 14:35:27 programming style 14:35:50 and can be written once for all java projects for example 14:36:10 agreed. 14:36:24 a central place would offer room for the other languages used in metrics-team 14:36:49 and we'd have a place for the bigger roadmap and 14:36:52 right. and metrics-web for example may contain non-java parts. 14:37:06 similar team docs. 14:37:21 yes, the web part and scripts 14:37:34 ah, metrics-*web* 14:37:41 not the web part of metrics-db. 14:38:03 if only it wouldn't be a mess to rename git repositories... 14:38:12 why rename? 14:38:22 metrics-web -> metrics, metrics-db -> collector 14:38:41 because I think the current names are slightly confusing. 14:38:50 it's no mess to rename? 14:39:01 it's not? 14:39:10 what happens to peoples' git remotes? 14:39:20 it's just the containing folder 14:39:37 they can set a new origin 14:39:56 yes, but they'll have to do that, and I think that might cause some confusion. 14:40:22 well, we're churning out releases for the people who use the code. 14:40:46 those who program can 14:41:10 clone another repo or set the new origin? 14:41:22 hmm, ok. 14:41:43 let's move that discussion to the mailing list, so that others who aren't here can object or state their opinion, too? 14:41:59 good idea. 14:42:04 cool! 14:42:09 so, git repo for team stuff. 14:42:14 how about metrics-team ? 14:42:42 https://gitweb.torproject.org/ <- list of all repos. 14:42:43 sounds fine. 14:43:18 would you want to have push access? 14:43:44 why not? 14:44:05 ok. we'll have to get you an LDAP account. good thing we signed keys. 14:44:17 I'll create tickets for all that. 14:44:26 ok. 14:45:12 let's move on if there are no objections/further thoughts. 14:45:29 * Directory authority disagreement visualization (Letty) 14:45:39 oh hi, i'm still coding on the integration of my viz to metrics server (first i had a local file that i converted in a datastructure perfect for my viz http://letty.io/tor/) 14:45:48 i finished implementing the converter functionality in java 14:45:53 need to figure out how the datastructure is and change the current filebased converter. 14:46:01 thanks karsten for the short introduction to metric modules, i will have a look on that on the weekend. Should i add your intro to the readme file? 14:46:24 i will code that, hopefully, on the weekend. and if i have some time left until the next meeting, i also want to rethink the design/text amount of the viz 14:47:06 hmm, I'm afraid the documentation in metrics-web is a mess. would you want to add a new README to your module only? 14:47:24 and once we're cleaning up there (ha), we're including that in a more general metrics-web documentation? 14:47:47 unless you find a place where the new documentation would fit in nicely. I'm not overly optimistic though. 14:48:00 also, glad it worked. I didn't test it. ;) 14:48:35 i didn't had any time to test that.. i think i miss an if somewhere^^ 14:48:54 i will test it the next days. it was more a generell question 14:48:55 ah ok. heh 14:49:39 okay, happy to help more if needed. thanks for working on this! 14:49:42 i will document my way and we can decide where it fits 14:49:58 sounds great! 14:50:25 i hope my code is not just a huge mess! (didn't code any java since 2 years..) 14:50:38 no worries. happy to do a review. 14:50:43 :) ok 14:51:11 okay, cool, should we move on? 14:51:14 jup 14:51:19 * Analytics server (thms) 14:51:28 err 14:51:32 * Analytics server (oma) 14:51:41 stuck with Java refactoring - singletons, factories, IoC, no more statics, enums, generics, you name it. "improvements", "good changes"… 14:52:23 ok. anything you need a fresh pairs of eyes for? 14:52:29 will take more time, not sure how much (hence my reluctance towrds other changes) 14:52:30 pair* 14:52:51 oh, you don't have to worries about these changes. 14:52:56 read a lot, now trying to implement it. maybe next week? 14:53:06 one is removing something that's deprecated for over a year, 14:53:17 removal is GOOD :-) 14:53:18 another is adding javadocs (finally). 14:53:23 ah, cool 14:53:35 not sure about the others. /me looks at the ticket.. 14:53:50 not more yet 14:53:53 true. 14:54:10 well, it’s not really a problem either. once my code runs again i’mm happy to tweak a few details, really 14:54:13 but again, it's cool to keep using 1.1.0 if you don't want to upgrade. 14:54:38 okay, just let me know when you're ready, and I'll take a look. 14:54:39 yeah, just use 1.1.0 14:54:40 next week is fine. 14:54:56 okay, cool - thanks! 14:55:13 that’s it from me 14:55:25 great! and we ran out of topics before running out of time. 14:55:46 well, we also did that 2 weeks ago with only Letty and I being here and ending the meeting after 5 minutes.. 14:56:10 I'd say feel free to edit the roadmap on the pad for another hour or so, and I'll then push the changes to the wiki. 14:56:17 possibly after cleaning up a tiny bit. 14:56:52 thanks for attending! talk to you in two weeks. and keep an eye out on the doodle that I'm about to create later today. 14:56:56 thanks everyone! 14:57:01 #endmeeting