15:59:35 #startmeeting metrics team 15:59:35 Meeting started Thu Jan 10 15:59:35 2019 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:58 I assume gaba wrote her item earlier and is not around? 16:00:24 maybe gaba just meant for us to discuss it, I added the (gaba) 16:00:42 although she was around a little earlier fixing my timesheets 16:00:53 did you receive the sandstorm invite, too? 16:00:55 at 15:22 utc 16:01:08 yes 16:01:41 I didn't look in detail, tbh. 16:01:54 they are both money for "privacy" 16:02:39 hmm, ok. I think this discussion makes more sense with gaba. 16:02:39 which means either it's going to be easy, or that it's going to be that we write up an SOI and it wasn't what they were looking for because the CFP wasn't specific enough 16:03:04 they are both vague enough that I think we could submit the same SOI to both 16:03:11 hehe 16:03:23 this is problematic if we win both 16:03:26 but not terrible 16:04:10 looks like the second deadline is feb 1. 16:04:20 so, I need more context. 16:04:31 and I think that requires talking to gaba. 16:04:35 and you. 16:04:48 ok, let's do this by email after unless gaba appears 16:04:51 I'll ask her in an hour in another meeting. 16:04:54 cool 16:05:14 alright. 16:05:18 * OnionPerf quick progress report (irl) 16:05:45 so one thing is already done, there is now op-ab set up! 16:05:52 https://op-ab.onionperf.torproject.net/ 16:05:57 neat. 16:06:01 it's not done a nightly logrotate yet though 16:06:12 i think perhaps at the next week's meeting we could add this to collector if it's been stable 16:06:21 it's going to be a stable instance, not a testing instance of some sort? 16:06:30 that is the intention yes 16:06:37 stable? 16:06:55 a stable instance that should run for at least a year but hopefully more and possibly forever 16:07:01 okay, cool. 16:07:09 it gives us a comparison to the greenhost vms which i think is needed 16:07:13 so, yes, adding that to collector next week sounds good. 16:07:17 our diversity at the moment is just 1 AS 16:07:21 right. 16:07:40 on the onionperf code, i've stripped out the webserver so we don't have to maintain that bit of it and we can just use apache/nginx instead 16:07:46 like we do for collector at the moment 16:07:59 we're looking to port it to python 3 in the longer term 16:08:13 did you talk to rob about these plans? 16:08:32 like, is he going to review and merge them? 16:08:39 i spoke to rob a while ago, he is not really maintaining the code at the moment 16:08:53 so, possibly fork? 16:08:55 i've submitted a pull request and maybe he will review and merge it or maybe he will just give me permissions to do that 16:08:58 or we just fork 16:09:15 we will probably know this by next week's meeting 16:09:16 okay. 16:09:23 great! 16:09:24 acute has been working on adding the pluggable transport support and is making some progress 16:09:32 hi acute! 16:09:38 hi! 16:10:03 I have it working with meek and obfs4 (provisionally) 16:10:14 neat! 16:10:19 the code needs a lot of tidying up :) 16:10:27 the new code or the old one? :) 16:10:31 which will happen over the next month 16:10:43 the new one 16:10:46 ok. 16:11:23 sounds like things are moving forward nicely. anything needed from me? 16:11:35 will also be in Brussels next month to sync with folk and make sure tor metrics can run this later in the year 16:11:51 great! 16:12:07 nothing for now, will ping if I run into issues 16:12:22 hiro answered a question today about the port numbers we use 16:12:24 and also try email, just in case I ignore the irc world. 16:12:40 i think we chose 80 because of exit policies but we might switch that to 443 16:12:53 just because lets encrypt needs port 80 for renewing the certs and it simplifies the operations side 16:13:01 unless that is a bad idea for some reason 16:13:17 well, it changes a variable. 16:13:53 not sure if that's bad, but if you also change another variable (PT), you might not know which variable changed the output. 16:14:23 ok, we can perhaps think about this more later in the year when we come to deployment/operations 16:14:29 doesn't need to be fixed now 16:14:31 ok. 16:15:05 i think this is all on the onionperf topic for the quick update 16:15:19 okay, cool! thanks for the update! 16:15:26 * Technical report for Sponsor13 (irl) 16:15:56 so i'm thinking about working on this jan 21st to jan 25th, i wanted to check this timeframe is ok 16:16:16 sure, it is. 16:16:23 probably not finishing it in that time but i will be away from home and it will be easier to work on this than on onionperf 16:16:35 i also had a question about adding onionperf to it 16:16:55 i think it is useful for us to have the same documentation about onionperf as part of this report, which perhaps acute can produce while working on it 16:17:06 is it worth including this if we have it? 16:17:19 I think so, yes. 16:17:25 cool 16:17:31 that is all of my questions on that topic (: 16:17:37 it's probably not required, but I can see how it can be useful as part of the report. 16:17:44 "where the data comes from" 16:17:53 right 16:18:10 okay! 16:18:33 I don't really have topics for today. I'm hacking on metrics-web and don't really have anything to discuss at the moment. 16:19:01 ok, i'll look out for an email about the grants 16:19:10 regarding the funding stuff, it might be that we need to do something on short notice. 16:19:35 that is fine 16:19:45 i've done proposals in 24 hours before 16:19:47 okay. will keep you posted there. 16:19:49 hah 16:20:25 alright. thanks for your time, irl and acute! next meeting next week. 16:20:28 bye! 16:20:30 bye! 16:20:38 bye! 16:20:42 #endmeeting