15:00:24 #startmeeting metrics team 15:00:24 Meeting started Thu Sep 5 15:00:24 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:58 https://storm.torproject.org/shared/5h1Goax5eNusxjXJ_Ty5Wl7hFR1uqCReUiN8xdlBG8T <- agenda pad 15:01:49 let's start! 15:01:52 Bug Smash Fund campaign has been on (gaba) 15:02:19 yes. this is mostly a request/announcement 15:02:42 we have been running a campaign to get funding in August 15:02:57 so, we tag tickets, and somebody else reviews tagged tickets and does something with them? 15:02:59 that could fund any non-sponsor bug 15:03:16 yes, you tag the tickets that are non-sponsored that you are working on 15:03:35 what about adding metrics code bases to gitlab's CI? 15:03:37 and then people can follow all the non-sponsored work that could be sponsor with this campaign 15:03:45 yes 15:03:56 it's done as of 1 hour ago. 15:04:03 seems like a good bug smashing task 15:04:05 with credits going to irl, just mentioning this here. 15:04:10 yes, that sounds good 15:04:28 are you tagging that ticket, or shall I? 15:04:42 if you have the query, go ahead 15:05:20 alright, keeping this in mind for future tickets. 15:05:46 thanks 15:05:49 great! 15:05:52 moving on? 15:06:17 Data or possible viz for fundraising on impact of Tor? (gaba) 15:06:26 this is related to the mail that Antonela sent 15:06:30 right. 15:06:39 any thoughts on what they can use? 15:07:03 we did some things for one of the last fundraising campaigns. 15:07:37 was that in mexico when we brainstormed about this? 15:08:24 I do not know. 15:08:25 but, going one step back: we should ask when they need this. 15:08:36 heya! sorry to storm your meeting. i wanted to jump in and add that this is for a printed piece. 15:08:39 the proposal seems more urgent+important than this. 15:08:46 hi! 15:08:46 I think is mostly ongoing for the materials that Isa will give. 15:08:52 oh hi! 15:09:05 i think what you want is numbers of how many bugs were smashed? 15:09:12 do you remember if we came up with anything that would be suitable for printed materials? 15:09:16 this is a low priority. antonela updated the color on an old visualization that we are using now 15:09:20 i think this is not related to the bug smashing campaign 15:09:28 oh ok 15:09:59 but it would be great to have updated data, or perhaps something completely different and better 15:10:09 sounds good! 15:10:15 can you send us what you have? 15:10:20 https://dip.torproject.org/torproject/ux/team/uploads/6010583986f430be762b47f44e49851a/Tor_Hexagons.png 15:11:34 sstevenson: mostly you need some other metric that could be helpful/impactful. You need numbers and not really a visualization, right? 15:11:35 i have no idea where i would start for making that visualisation 15:11:53 we didn't make this visualization. 15:11:58 the numbers of users per country are easy 15:12:15 gaba: we are looking for a visualization to show tor’s impact 15:13:12 karsten: right, that is why we are reaching out to see if we can produce something that gets the same idea across 15:13:44 sstevenson: do you know about https://people.torproject.org/~karsten/tor-brochure/tor-brochure-en.pdf ? 15:13:53 for printed material 15:13:54 something that shows amount of traffic through the network or use of Tor because censorship would be good :) 15:14:27 i have about 150 of those in my swag kit printed and i've been leaving them places i go 15:14:43 I wonder if we could ask the makers of that visualization to make an updated one. 15:14:48 this is mostly about impact for funders 15:14:51 irl: i’ve never seen that one 15:14:55 it is great 15:15:09 I vaguely remmber answering their questions about which user numbers to use. 15:15:19 they ended up using the numbers until before the botnet. 15:16:18 should I ask them? 15:16:30 yes, why not :) 15:17:16 okay, let's try that, and if we need more, go back to this topic after submitting the proposal, okay? 15:17:31 that seems like the easiest solution. thanks, karsten! 15:17:38 .oO( started and ended a sentence with okay? check! ) 15:17:41 ok 15:17:43 great! 15:17:44 :) 15:17:55 :) 15:18:06 thanks, everyone! let me know if you hear back. 15:18:13 will do! 15:18:20 Scalability proposal (gaba) 15:18:42 should we have another meeting for that? 15:18:48 video meeting. 15:18:59 yes 15:19:02 soon? 15:19:05 soon :) 15:19:06 yes. 15:19:11 monday? 15:19:31 mike was worry that we may drop " the object model for path queries and basically the ability to spin up many onionperf test instances" 15:19:35 from that project 15:19:38 Monday works for me 15:19:59 1400 UTC ? 15:20:06 or can we do a quick video call after this meeting? like in 15 minutes? 15:20:08 it is early here but works better for me than later on Monday 15:20:16 mm, that works too 15:20:16 being able to run test instances is happening anyway, we should write it in the project but it may even happen before the official project start 15:20:40 that's also one of my questions: which of the parts that we need will be done before we even start with this project? 15:21:07 We can write the project that we need AND if we finish anything from there before the project starts then awesome 15:21:13 or is in 15 minutes too soon? 15:21:20 15 min is fine for me 15:21:23 irl? 15:21:43 in 15 min? 15:21:48 i lost the thread 15:21:50 like, after this meeting. 15:22:09 i run out of work time at 1600 utc 15:22:18 if we can be done before that then ok 15:22:21 we have other meeting 1600 utc 15:22:22 yes, that would be fine. I have another meeting at 1600 utc. 15:22:26 ok cool 15:22:29 great! 15:22:45 roadmap? 15:22:48 yes! 15:23:36 a note: the onionperf/ansible stuff went through one round of review, and is now back on review after things were addressed 15:23:40 so that's not stalling there 15:23:50 ok 15:23:52 Two of my tasks are in the On Review swimlane. 15:24:18 so, they're ongoing. 15:24:32 #31558 will need to be reviewed monday 15:24:34 out of time 15:24:41 regarding #19332, I did look at that, but it seemed like it needs work on the anti-censorship team side first. 15:24:51 sounds good. 15:25:00 #29461 seems merge ready 15:25:02 I think I'd want to leave #19332 where it is. 15:25:09 ok 15:25:14 yes, that is merge-ready, but it requires releases. 15:25:20 #31398 is already moved to done 15:25:21 well, a metrics-lib release. 15:25:34 what is #30777 up to? 15:25:44 that seems to have stalled 15:25:51 phw is working on that one 15:26:03 with communications for what I understand 15:26:33 i think if there is nothing needed from metrics we can put that in done 15:26:40 right. 15:26:43 ok 15:27:36 alright, I think the roadmap is good for now. 15:28:07 #29461 is done for metrics too, right? 15:28:27 almost. we need that metrics-lib release before merging that code. 15:28:40 and then we need to merge the metrics-web part of it, too. 15:28:58 not done yet, though no major parts left. 15:29:09 ok 15:29:45 anything from backlog to work on next week? 15:29:58 I'd like to focus on the proposal. 15:30:07 ok 15:30:09 and do #19332. 15:30:27 does #19332 have a sponsor? 15:30:55 sponsor 30 15:31:47 any other change? 15:31:54 #31558 probably needs a sponsor 15:31:59 either 28 or 30 15:32:42 or if they are both happy sponsors we can call it bug smashing 15:33:16 either works for me. gaba? 15:33:17 let's call it bug smashing 15:33:34 will do. 15:33:39 ok cool, so sponsorz on the roadmap, tag it in trac 15:34:16 ok 15:34:25 anything else? 15:34:30 not from me. 15:34:39 not from me 15:34:47 sounds good 15:34:49 i expect that there will be more onionperf/ansible tickets for acute once the two on review have been merged (: 15:34:58 sounds great! :) 15:35:14 nice 15:35:19 yay 15:35:35 cool, I think that's all for today's meeting. 15:36:14 ok, see you at the next meeting 15:36:21 thanks, everyone, bye! o/ 15:36:26 #endmeeting