14:29:48 #startmeeting metrics team 14:29:48 Meeting started Thu Sep 21 14:29:48 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:51 https://storm.torproject.org/shared/Ou-1QRctynWbF4yedi-MfDsjImFMFSIEP20fbVGCPRa <- agenda pad 14:29:54 irl: you around? 14:29:59 yep, added all. 14:30:28 there is 'irl' and 'irl_' even. 14:30:28 last meeting before the berlin meeting next week! 14:30:35 true. 14:30:40 irl_: ^ :) 14:30:57 In the OnionSpace? 14:31:03 okay, I'd say let's start with the first topic. 14:31:06 yes! 14:31:18 * java 8: next steps (iwakeh) 14:31:25 I'll still need to get instructions for us to get in, but I'm told that's possible. 14:31:35 cool. 14:31:43 okay. java 8! 14:31:57 You closed all java 8 tickets which is fine as these 14:32:09 were ancient, but I just wanted to 'warn' 14:32:32 that I will open quite a few tickets for the actual java 8 improvements. 14:32:50 sounds good! 14:32:51 we're using the j8 compiler, but hardly any j8 features, yet. 14:32:55 true. 14:33:03 I'll use some 14:33:19 in the webstats code. 14:33:25 great! 14:33:32 Also good as examples. 14:33:42 absolutely. I don't know much about java 8 yet. 14:33:52 You'll have fun. 14:33:55 happy to learn by example. 14:33:57 hehe 14:34:03 so, sure, please open tickets. 14:34:11 FWIW, I closed many old tickets that were not actionable, 14:34:19 but I'm happy to have tickets open that are actionable. 14:34:24 true, I couldn't avoid noticing ;-) 14:34:28 hehe 14:34:38 It's fine to have a cleaner ticket list. 14:34:41 but, let's talk about trac email flooding later on. 14:34:52 * webstats in metrics-lib & collector: status (iwakeh) 14:35:01 Thanks for the logs! 14:35:26 yep! 14:35:41 I think I have an approach for CollecTor now (also thanks to your input on the ticket) 14:35:49 sounds good! 14:35:56 you're not blocking on anything from me there, right? 14:35:58 and now I want to settle that, test with the logs and 14:36:18 also document some decisions a little more detailed in the source code. 14:36:24 ok. 14:36:50 no, all resources available. The logs already have the time 00:00:00 14:36:53 I'm planning to spend most of my time this and next week on preparing Berlin, but I can review code. 14:36:55 set. 14:37:07 That's fine. 14:37:58 There should be something to review before next Thursday. 14:38:08 great! 14:38:20 this whole project is really time-consuming. 14:38:32 just something to keep in mind when we plan to add other data sources. 14:38:40 maybe we'll learn from this project and be faster next time. 14:38:46 but maybe it just takes time to do it right. 14:38:55 yes, that's true. 14:39:18 And, mostly collecting the actual requirements. 14:39:23 maybe we should have a retrospective of this project after it's done. 14:39:31 In Berlin? 14:39:36 probably too soon? 14:40:04 could as well be in november or december. whenever it's done. and running. and all bugs are fixed. hah. 14:40:07 ;) 14:40:08 I think, now 14:40:43 we have all requirements and the other stuff is easy. 14:41:06 that's all for webstats. 14:41:11 great! 14:41:19 * Preparing a roadmapping session in Berlin (karsten) 14:41:43 so, I hear there's a change in getting funding for development work. 14:41:52 oh? 14:42:05 so far we would have written a grant proposal for something we want to do, and once we have the grant, we can start working on it. 14:42:35 the new approach is that we write a roadmap with all the stuff that we think needs doing, and the grants people then go find funding for that work. 14:42:49 sounds good. 14:42:58 we should write a roadmap! :) 14:43:11 yep! 14:43:15 my idea was that we collect ideas before berlin and have a draft to discuss there. 14:43:42 we then take that refined draft to montreal (well, I will do that) and get more input from other teams. 14:43:57 and also discuss it with grants people. 14:44:09 and after another revision in the team that will be our roadmap. 14:44:09 sounds like a plan. 14:44:27 cool. :) 14:44:47 would you want to think about the most important things we should be working on in the next 6 to 12 months? 14:44:53 and then send me that list? 14:45:00 Sure. 14:45:07 I'm also preparing a draft with my ideas. 14:45:25 I'm currently using the categories on the metrics website to organize these ideas/tasks. 14:45:39 but any other organization would work, too. 14:45:53 ok, what about cross-product concerns? 14:46:13 what's important is that we can explain why we think these tasks will make tor better. 14:46:28 sure, include them as well. 14:46:37 True, the impact part for funding proposals. 14:46:38 the product is all-of-metrics. 14:46:42 yes. 14:47:43 alright, I think that's all for this topic. 14:47:51 ok. 14:48:00 we'll discuss this more in berlin. 14:48:11 * Trac housekeeping, preparing a joint ticket triage session in Berlin (karsten) 14:48:21 you noticed that I changed a few tickets. 14:48:28 * iwakeh nodding 14:48:42 I hope to be able to resolve more tickets, in particular in Metrics/Analysis, over the next few days. 14:49:19 my plan/hope is that we can have a session in berlin where we go over open tickets and decide what to do with them. 14:49:22 on a high level. 14:50:01 maybe you can look over tickets before berlin and see if you can resolve some of them. 14:50:08 the shorter the list, the more useful that session will be. 14:50:28 something else that would help is to fix assignments and priorities and maybe other fields. 14:50:48 sure, should I wait for your removal-attempt? 14:51:04 for example, can you go through the tickets that are currently assigned to you and see which of these you're actually working on? 14:51:11 ah, just ignore Metrics/Analysis, I'd say. 14:51:26 Yes. 14:51:52 Just those assigned to me or those I created? 14:52:05 Both? 14:52:22 well, all that are assigned to you. 14:52:28 ok. 14:52:29 that's just an example. 14:52:46 whatever tickets I can improve or resolve. 14:52:59 it would be cool if "assigned to somebody" actually means that the person is going to act on the ticket in the next, say, few weeks. 14:53:02 yes! 14:53:20 oh, another ask: 14:53:38 please think about things that we can achieve during next week's triage session. 14:53:59 my rough idea is that we'll have the list of ~250 tickets and batch-modify them together. 14:54:09 'achieve'? 14:54:22 so, check all that we try to get done in Q4/2017 and batch-add a keyword for that. 14:54:43 yes, what are useful results from going together through all the open tickets next week. 14:54:52 ah, ok. 14:54:57 I'll do the same. 14:55:40 ok. that's all on trac, I think. 14:55:56 moving on? 14:56:15 yep 14:56:20 * Preparing a visualization review session in Berlin (karsten) 14:56:29 that's a thought what we could do in berlin. 14:56:44 look at all the graphs? 14:56:44 review existing visualizations on metrics-web, 14:56:47 yes. 14:56:58 and review open tickets asking for more visualizations. 14:57:06 true, and 14:57:13 then think about which we might remove, and which we might add next. 14:57:24 also sketch possible new graphs and other visuals. 14:57:28 yes. 14:57:42 ah, you mean in addition to the ones mentioned in tickets? sure. 14:58:01 We should have a flipchart then. 14:58:21 maybe we'll have one. 14:59:19 we'll also have my tablet where we can sketch things and later put them up somewhere as a pdf. 14:59:37 should work. 14:59:40 yep. 14:59:49 okay, next topic? 15:00:03 fine 15:00:07 * Planning the two documentation deliverables in Berlin (karsten) 15:00:28 we don't have a contract yet, so there are no news about that. 15:00:38 but we should take the opportunity to make some plans. 15:00:45 yes, are there deadlines and other constraints from the final contract? 15:01:04 oh, I see. Yes I also added that to the planning pad. 15:01:05 I don't know. we'll have to wait for the contract, I think. 15:01:17 speaking of, mind moving that to the agenda pad? 15:01:27 it'll get more attention (at least from me) there. 15:01:30 ;) 15:01:30 Take a look at the pad 15:01:41 ah ok. 15:02:08 okay, I don't mind as much. separate pad is fine. 15:02:16 let's fix the storm issue, too. 15:02:23 It's more long term planning there. 15:02:36 true. 15:02:47 What's the storm secret? 15:02:57 hmmmmmmm 15:03:04 you'll need a @torproject.org address. 15:03:09 How do you create pads there? 15:03:30 yes, I logged in with that, but nowhere to create a new one. 15:03:32 you enter your user name, and it'll send you a token. 15:03:36 oh. 15:03:49 do you have a sidebar on the left? 15:03:55 yes 15:04:01 grow sidebar. 15:04:05 then go to apps. 15:04:15 wait, I need to login again ... 15:04:18 hehe 15:05:50 * iwakeh has 'Apps' ... install now 15:06:40 or 'upload app'? 15:06:59 I don't know. I have Etherpad listed there already. 15:07:03 maybe search for it? 15:08:03 want to try it after the meeting and ping me if that doesn't work? 15:08:25 There is nothing installed, the app market failed to install the app. 15:08:30 oh. 15:08:53 with an error message? 15:08:56 Maybe, I'll try again later and then open a ticket. 15:09:04 ok. 15:09:08 'must sign-in' 15:09:35 okay, last topic for today: 15:09:39 * Making a list of open projects that we should discuss in Berlin (karsten) 15:09:45 It's not too urgent; I'll play with that later. 15:09:47 for example, the webstats project comes to mind. 15:09:52 ok. 15:09:58 or moving websites to metrics-web. 15:10:30 not the reason for having this meeting, but when we're there anyway, why not discuss some things that we'd otherwise discuss via email/irc. 15:10:54 true, discussion will be easier. 15:11:00 yes. 15:11:14 alright, I ran out of topics here. 15:11:29 what about you? anything else? 15:11:35 well, the 45min target is reached. 15:11:38 hehe 15:11:40 all fine :-) 15:11:55 great! looking forward to next week! 15:12:13 back to work. Bye bye :-) 15:12:21 indeed! bye, bye. :) 15:12:24 cu in berlin! 15:12:32 ! 15:14:12 #endmeeting 15:14:12 #endmeeting