14:28:50 #startmeeting metrics team 14:28:50 Meeting started Thu Oct 18 14:28:50 2018 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:28:50 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:28:52 irl: hi! 14:28:56 hello 14:29:20 three topics on the agenda. want to add more, or shall we start? 14:29:31 we can start 14:29:35 ok. 14:29:38 * Moving the "Research" page off Tor Metrics and onto new research portal (irl) 14:30:05 i just wanted to get your opinion on this 14:30:25 how far is the new research portal? 14:30:32 i think that the tools section is probably going to be better looked after on the research portal than on metrics for example 14:30:38 https://research-staging.torproject.org/ 14:30:41 secret preview link 14:31:04 we wouldn't remove the page from metrics until this one is live though 14:31:19 I'm fine with this plan. 14:31:32 ok cool 14:31:35 that is all of that topic (: 14:31:37 is there going to be a dev portal? 14:31:45 that's another thing entirely 14:31:59 a question for the ux team 14:32:04 okay. but when there is such a thing, we might want to do the same with our dev page. 14:32:15 i will keep that in mind 14:32:27 okay. sounds good to me. 14:32:42 cool. moving on? 14:32:47 yep 14:32:51 * Ticket priorities (karsten) 14:33:04 so, I think I ran dry with my list of tickets to work on. 14:33:11 which means I might pick at random, 14:33:26 or we take some other approach for keeping me busy. :) 14:33:34 is there anything you need me to work on? 14:33:57 i've been kept busy with the ye campaign, research portal, sponsor 19 reporting and admin things 14:34:04 whee. 14:34:07 so i'm not blocking on you 14:34:37 I wonder if I should then work on something that doesn't keep you busy soon after for reviews. 14:34:43 hi! 14:34:46 hi gaba! 14:35:30 karsten: i think for now work on tickets that you wouldn't otherwise work on because they're not urgent, but they are important 14:35:44 maybe next week we could pick roadmap items to start tackling 14:36:31 okay, sounds like a plan. and if something specific comes up that you think might be useful if I work on it, just let me know. 14:36:43 yep, will do 14:36:58 ah, one more thought on this: 14:37:26 should we reserve some tickets to give them out to applicants? 14:37:47 you want to give applicants a test? 14:37:55 that seems like a reasonable idea 14:38:03 I think we considered that with erin. 14:38:13 not for every applicant, just the shortlist 14:38:16 yes 14:38:18 yes, right. 14:38:19 it sounds good 14:38:55 okay, I'll look out for those tasks and try not to work on those tickets myself. ;) 14:39:20 if they can be new graphs, consensus weight based graphs or continent based graphs are in demand 14:39:40 that's a lot of dev environment to bootstrap though 14:39:45 can you explain the second? 14:39:53 continent based in rs? 14:39:59 something that does not require a lot of time would be good 14:40:01 users by continent or relays by continent 14:40:07 instead of by country 14:40:12 but in rs? 14:40:18 metrics-web 14:40:35 is there a ticket for that? 14:41:05 no, but i've seen people making their own because we don't have them 14:41:16 ok. 14:41:17 well, we have tickets for things by consensus weight 14:41:21 not by continent 14:41:22 yes. 14:41:50 how much time do we expect applicants to work on a task? 14:42:10 1-2 hours 14:42:18 yes 14:42:22 we might give them an OVA with a dev environment in it 14:42:31 OVA? 14:42:45 open virtual appliance is a rough guess 14:42:55 it's a vm container format 14:43:03 ah, neat. 14:43:04 virtualbox 14:43:45 sounds good! 14:43:57 moving on? 14:44:07 ok 14:44:12 * Status messages (karsten) 14:44:34 ahf has a script to log status message of fellow team members. 14:44:53 should we run it and use these messages for reports? 14:45:02 or retrospectives. 14:45:11 that sounds like a good idea 14:45:14 not in the sense of a metric, but to remember what we did. 14:45:22 yes 14:45:30 I have it running and added you there :) 14:45:40 ah, do you have a log already? 14:45:51 yes 14:46:08 can you share the log with us? (assuming that irl is okay with that?) 14:46:09 but you can run it too. Otherwise I get the log for the retrospective. 14:46:17 yes 14:46:17 ah, that works, too. 14:46:21 ok 14:46:34 if there's something you'd like the script to do, please let me know. right now it's very much geared towards the network-team, but could be made to handle things for other teams :-) 14:46:40 i would like to have the log of what i've been statusing 14:46:44 i wonder how often i do it 14:47:00 thanks, ahf! 14:47:38 I don't need the log during the month. I'd appreciate having it when the next month begins, as input for the monthly report. 14:47:44 and for the retrospective. 14:48:13 and it'd be good to know that somebody is logging these messages. makes much more sense for me to write them. 14:48:28 ok. irl, I can send you the log now so you have an idea but I share it for the retrospective. 14:49:12 gaba: can you share it shortly before the actual retrospective? 14:49:41 sounds good 14:49:43 yes 14:49:48 awesome! 14:50:30 okay, I think we ran out of topics. 14:50:33 anything else? 14:50:35 as gaba is here 14:50:39 task 10c? 14:51:25 I will check today with other people in the network-team to see if soembody can take it. 14:51:31 awesome thanks 14:51:39 i can go over it and review it, or even flesh out an outline 14:51:49 but i'm not sure where to start 14:51:53 do you have a draft somewehre already or outline? 14:51:59 not for 10c 14:52:03 ok 14:52:03 i've done 10a and 10b though 14:52:13 whoever take it can talk with you then 14:52:14 11a-c are also on track for completion today 14:52:30 i won't be around this evening 14:52:52 i've been doing too many evenings this week 14:53:06 i'll send you a summary and some thoughts to share though? 14:53:08 ok, can you just write down your thoughts on it? 14:53:10 yes 14:53:12 that^ 14:53:12 ok cool (: 14:53:32 i'm out of topics now 14:53:38 me too. 14:54:06 alright, thanks, irl and gaba! 14:54:10 bye! :) 14:54:13 bye! 14:54:18 #endmeeting