13:59:41 <karsten> #startmeeting metrics team
13:59:41 <MeetBot> Meeting started Thu May  5 13:59:41 2016 UTC.  The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:41 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:15 <karsten> I guess this will be a smaller meeting, with oma being on vacation and Letty possibly distracted by other things as I hear.
14:00:32 <karsten> but that could mean we'll have more time per topic.
14:00:39 <karsten> https://pad.riseup.net/p/zUNzEIFRq5S4 is the meeting pad.
14:00:44 <karsten> hi iwakeh!
14:00:45 <iwakeh> hi there!
14:01:04 <karsten> please add topics to that pad.
14:01:35 <karsten> or remove topics if they contain your name and don't make much sense to you. this was just me making some suggestions.
14:04:04 <karsten> is virgil around?
14:04:24 <karsten> if not, I wonder if I should just start with my topic, and then we have the rest of the meeting for collector and team documentation.
14:04:39 <iwakeh> that'll be fine
14:04:59 <karsten> ok!
14:05:00 <karsten> * Discontinuing Globe (karsten)
14:05:25 <karsten> the latest update there is that we're trying to find a time for a meeting to go through trac tickets.
14:05:36 <karsten> globe and atlas tickets, that is.
14:05:49 <iwakeh> ah, who we?
14:06:13 <karsten> and then we decide which of them we want to keep and reassign to atlas, which of them need to be completed before shutting down globe, and which ones we can close.
14:06:16 <karsten> https://lists.torproject.org/pipermail/tor-project/2016-April/000299.html
14:06:48 <karsten> we = phw, isis, and I, but whoever else wants to attend is welcome to come.
14:07:14 <karsten> my original plan was to meet in 1 week from now using this time slot, but I think phw cannot make that.
14:07:26 <karsten> so, I might start a doodle later today or tomorrow.
14:08:24 <karsten> after that meeting we'll need to implement the remaining tickets.
14:08:39 <karsten> hopefully with help of friendly volunteers.
14:09:08 <karsten> I don't expect that to be many tickets. right now there are 3. there shouldn't be more than twice as many.
14:09:11 <karsten> I hope.
14:09:33 <karsten> okay, that's all I wanted to say here.
14:09:48 <karsten> happy to move on if there are no questions.
14:10:16 <karsten> ok!
14:10:18 <karsten> * Team documentation wiki page (iwakeh)
14:10:35 <iwakeh> yes, we finished the first collection
14:10:42 <iwakeh> and got a pretty good
14:10:51 <iwakeh> selection of questions.
14:10:56 <karsten> agreed!
14:11:00 <iwakeh> These need to be answered now.
14:11:03 <iwakeh> And,
14:11:26 <iwakeh> as a next step I would like to names
14:11:42 <iwakeh> of people who anser specific topics
14:12:20 <karsten> where is the wiki page again? ... looking.
14:12:45 <karsten> https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam/Documentation
14:12:54 <iwakeh> maybe, we should link it soon to the team page :-)
14:13:06 <karsten> right. can you do that?
14:13:22 <iwakeh> yes, I'll look for a good place.
14:13:53 <iwakeh> i think
14:14:08 <iwakeh> operation and coding answers
14:14:20 <iwakeh> can be provided from the guide docs.
14:14:37 <iwakeh> open are the team and funding etc questions.
14:15:29 <karsten> I guess I should try to answer them. or rather, write a first draft of an answer that we can then improve.
14:15:41 <iwakeh> good!
14:15:56 <iwakeh> that's a start.
14:16:02 <karsten> isabela: I wonder if you'd enjoy answering the funding questions together with me?
14:16:11 <karsten> https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam/Documentation#Funding
14:16:57 <karsten> iwakeh: okay, so we put my name next to "About the Metrics-Team", "Road-map, ...", and "Funding",
14:17:04 <isabela> karsten: yes
14:17:11 <isabela> i love this faq :)
14:17:23 <isabela> will pass this over to other teams to do something like that
14:17:28 <karsten> isabela: perfect! much appreciated.
14:18:02 <karsten> iwakeh: and yours next to "Contribution and Operation"? or what was the plan?
14:18:07 <iwakeh> yes,
14:18:14 <iwakeh> and guide documents.
14:18:25 <karsten> right. sounds great!
14:18:41 <iwakeh> I'll add this to the doc.
14:18:46 <iwakeh> later.
14:18:59 <karsten> thanks! and where do we write answers? below questions in the same document?
14:19:12 <iwakeh> I thought about that too
14:19:15 <iwakeh> maybe,
14:19:25 <karsten> we could also use a pad.
14:19:32 <karsten> and copy results back to the wiki later.
14:19:38 <iwakeh> rather a wiki page.
14:19:51 <karsten> works for me.
14:19:54 <iwakeh> maybe, have one wiki page
14:20:08 <iwakeh> per person answering and/or topic
14:20:18 <iwakeh> I don't
14:20:29 <iwakeh> know if trac has concurrency issues ;-)
14:21:07 <iwakeh> in case we edit at the same time.
14:21:16 <karsten> hmm, what we can do to avoid those is pre-write answers in a local tool and copy them over to the wiki when we're done.
14:21:32 <karsten> if we divide the work by topic we shouldn't run into major issues.
14:21:47 <iwakeh> that would work, too.
14:21:55 <iwakeh> so, same doc?
14:22:02 <karsten> btw, always keep a copy of your edits locally before submitting.
14:22:06 <karsten> sure, same doc is fine.
14:22:13 <iwakeh> should we have a length limit?
14:22:15 <karsten> we had cases of trac eating your changes.
14:22:22 <karsten> and that hurts.
14:22:31 <karsten> huh, probably.
14:22:35 <karsten> 100 words, or what's a good limit?
14:22:50 <iwakeh> oh, that's a lot.
14:23:03 <iwakeh> or?
14:23:06 <karsten> "What skills are required for participating? What tools are used? What languages are supported (maybe even in addition to the languages used in a project)? "
14:23:09 <karsten> that's 25 words.
14:23:31 <iwakeh> ok, try 100 words.
14:23:33 <karsten> between 50 and 100, where 50 is better?
14:23:39 <iwakeh> yes.
14:23:44 <karsten> ok.
14:24:12 <iwakeh> so, that's it.
14:24:20 <karsten> great!
14:24:29 <karsten> moving on..
14:24:33 <karsten> * another CollecTor instance (iwakeh)
14:24:38 <iwakeh> yep,
14:24:59 <iwakeh> I'll soon have access to a server for setting up
14:25:07 <iwakeh> another CollecTor instance.
14:25:20 <iwakeh> I would like to use it for the first
14:25:47 <iwakeh> non-cron-job instance and while setting
14:25:57 <iwakeh> it up rewrite the operator guide.
14:26:03 <karsten> neat!
14:26:11 <iwakeh> this means
14:26:11 <karsten> is the non-cron-job part already written?
14:26:39 <iwakeh> first priority is the timed-java changes.
14:26:57 <karsten> ok. please let me know which tickets that are, and I'll prioritize those.
14:27:12 <iwakeh> well, I'll need to write these.
14:27:29 <karsten> ah, right, I meant prioritize review of those.
14:27:36 <iwakeh> ok.
14:27:57 <iwakeh> that sort of leads seemlessly
14:28:03 <iwakeh> into the next topic
14:28:04 <karsten> heh
14:28:09 <karsten> * CollecTor improvement project (iwakeh)
14:28:31 <iwakeh> we implemented quite a few things already.
14:29:06 <iwakeh> the next steps need prioritization
14:29:23 <iwakeh> there is the analysis of
14:29:29 <iwakeh> missing descriptors.
14:29:54 <iwakeh> the design and implementation and the guide docs.
14:30:41 <karsten> okay, let's see. missing descriptors analysis is half way done, right?
14:30:49 <iwakeh> right.
14:30:53 <karsten> with the analysis of missing consensuses/votes/etc. not done yet.
14:31:10 <karsten> though we'll get that almost for free once we have synchronization between collector instances implemented and deployed.
14:31:21 <karsten> because then we'll see how many descriptors have 1 vs. 2 @source tags.
14:31:43 <iwakeh> so, sync-tasks first?
14:31:49 <karsten> well, assuming that's the design that will be implemented.
14:31:52 <iwakeh> together with non-cron?
14:32:01 <karsten> non-cron seems most pressing.
14:32:06 <karsten> so that you can set up your instance.
14:32:11 <iwakeh> yep.
14:32:26 <iwakeh> I'll tackle that
14:32:38 <iwakeh> first and at he same time make a better list
14:32:47 <iwakeh> for prioritization.
14:33:00 <karsten> the sync part is important, too, but I think we can also sync offline by copying over tarballs and import them.
14:33:15 <iwakeh> I still have the feeling that the analysis
14:33:16 <karsten> that means, you could set up your instance now, and we sync descriptors in a few weeks.
14:33:31 <karsten> the descriptors you collect now.
14:34:36 <karsten> (that the analysis... ?)
14:34:48 <iwakeh> will
14:34:59 <iwakeh> point to other places
14:35:09 <iwakeh> that need care. or
14:35:17 <iwakeh> might need improvement?
14:35:20 <karsten> ah, I think so.
14:35:44 <iwakeh> maybe, sync in parallel to second
14:35:46 <karsten> but if you set up your instance now and start collecting, even if we're missing descriptors, we have a backup.
14:35:57 <iwakeh> wrong. non-cron in
14:36:17 <karsten> I'm also thinking about importing tjr's descriptors from the past months once we have sync in place.
14:36:18 <iwakeh> in parallel to second analysis.
14:36:44 <karsten> (tjr is running an older version of collector since, what, a year or so, and we never exchanged data.)
14:36:58 <iwakeh> ok, interesting.
14:37:11 <iwakeh> summary:
14:37:22 <iwakeh> non-cron for third CollecTor
14:37:33 <iwakeh> goes first.
14:37:39 <karsten> yep
14:37:56 <iwakeh> I think the other
14:38:05 <iwakeh> task will fall in place once
14:38:14 <iwakeh> I'll start on that.
14:38:33 <karsten> keeping notes for the guide while you're setting things up sounds like a good plan, too.
14:38:42 <iwakeh> yes.
14:39:00 <iwakeh> shouldn't we update the roadmap?
14:39:11 <karsten> the team roadmap?
14:39:28 <iwakeh> just noticed that it's outdated
14:39:31 <iwakeh> partially.
14:40:04 <karsten> I noticed, too, but I knew that some people would be missing today, so I didn't put it on the agenda. but let's update collector-related tasks if you want?
14:40:29 <iwakeh> or before the next meeting would be fine.
14:40:30 <karsten> should I copy it over to the pad?
14:40:34 <karsten> sure, or that.
14:40:54 <karsten> I'll put it on the next agenda.
14:40:58 <iwakeh> ok.
14:41:25 <iwakeh> well, that's all.
14:41:29 <karsten> okay, what else can I do than seemingly randomly go through open tickets and respond?
14:41:44 <iwakeh> oh, that's fine.
14:41:58 <iwakeh> I'll make myself heard when
14:42:04 <iwakeh> necessary ;-)
14:42:04 <karsten> can you maybe set priority to something above medium if you need a response faster?
14:42:09 <karsten> that's good!
14:42:18 <iwakeh> ok, good point
14:42:37 <karsten> not that we'd use the priority field consistently, but we could start here.
14:42:57 <karsten> okay, great. anything else to discuss today?
14:43:14 <iwakeh> All said.
14:43:21 <karsten> perfect!
14:43:45 <karsten> next meeting in 2 weeks, and doodle for the globe meeting some time next week.
14:43:53 <iwakeh> fine.
14:44:21 <karsten> great, let's talk more on tickets! ttyl
14:44:33 <karsten> #endmeeting