17:00:22 #startmeeting weekly network team meeting, 27 Nov 2017 17:00:22 Meeting started Mon Nov 27 17:00:22 2017 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:26 hi everybody!!! 17:00:31 hello 17:00:32 \o/ 17:00:32 o/ 17:00:35 hi 17:00:45 hello 17:00:47 Pad is at https://pad.riseup.net/p/takGJ0e0100J 17:01:02 hello 17:01:38 whoa, lots of updates 17:01:44 * asn starts reading updates 17:02:27 let's all read the updates, answer little questions, and boldface discussion issues 17:03:21 wrt "On the roadmap spreadsheet", can we have the link to spteadsheet? 17:03:27 or is it not on the pad for a reason? 17:03:32 one moment 17:03:38 dont have those emails on this laptop 17:04:02 added it 17:04:16 o/ 17:04:20 hi isis ! 17:04:43 hey nickm! how's it going 17:04:50 hoho dgoulet getting an android XD 17:04:57 not bad! Trying to get my brain back into code 17:05:03 asn: not a phone! :P 17:05:25 :-D 17:05:31 a big phone 17:05:44 i see we have dragons 17:06:43 * nickm has an old collection of quotations and needed a place to put them 17:06:45 lovely 17:07:42 i like the quotation :) 17:08:03 mikeperry: we have "List of guard discovery proposals to write" in November in the pad, but i haven't actually thought much about it. should we move to december? 17:08:04 $ fortune --cypherpunk 17:08:20 i think december i will finally have time to do this stuff 17:09:10 asn: I thought about it a bit as part of writing https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorV 17:09:36 I couldn't find anything that really needed an immediate proposal other than updates to prop247. 17:10:12 I want to think about how conflux could help mitigate congestion attacks, but I don't have concrete ideas there yet, and I think the other work should be done first 17:10:33 so we can wait on that item until december I suppose 17:10:37 maybe we will think of more to do 17:10:59 right 17:11:02 So, make sure to check the announcements this time -- they're all things that we need to do in order to keep organized 17:11:12 i guess the improvements on prop247 can also be seen as microproposals 17:11:48 since i dont think they are just gonna be trivial changes 17:11:53 nickm: i will move the bucket stuff to december so we can try have armadev catch up with it 17:11:59 isabela: ok 17:12:27 mikeperry: moved it to dec 17:12:35 first discussion topic I see is isabela's question for isis 17:13:05 isabela: are you/we going to do s8 reporting/network tests this week or is that going to be sometime in december? 17:13:30 ahf: i will write the report for Q4 in january 17:13:33 isabela: also, question for you: Is there anything we should be doing this week to help you out? 17:13:40 isabela: oki, cool! 17:13:41 isabela: you have a question for me? 17:13:42 help me with? 17:13:52 isis: checking on the status of moat server 17:14:38 isabela: it's done, but i got an email about a bug that i need to look into where if you do the captcha succssfully it doesn't give bridges 17:16:24 isis: is that the issue mcs mentioned on those check in emails? 17:18:13 mikeperry: actually i marked the "list of proposals" as DONE, and I will move "All guard discovery proposal drafts written" to december 17:18:24 mikeperry: since your work on sponsorv wiki page is indeed the list 17:19:36 isis: question for you above? 17:19:54 isabela: i am a bit behind on email, but assuming it is the one i saw last week, then yes 17:20:01 isabela: help you with reports and whatnot. 17:20:07 and proposals and deadlines and all those things 17:20:32 nickm: i dont have anyone know related to network team work, thanks tho! o/ 17:20:44 *anything 17:20:45 hehe 17:21:15 so, next person with discussion topics seems to be me 17:21:29 I'm going to be doing backporting and security fix prep this week 17:21:29 isis: yep, do you mind sending an update on that email from last week? 17:21:31 i'm not sure if there is an issue because the unittests and the integration tests are happy so it might just be that something in the test environment setup went wonky 17:21:32 (yes, I'll get CVEs) 17:21:36 isis: so we don't need follow-up tickets for the remaining things of #22871? 17:21:40 isabela: nope, will do 17:22:07 isis: thank you 17:22:08 GeKo: also will do that, i forgot 17:22:09 I'm going to need folks to help review and test this stuff again; sorry there's so much of it 17:22:33 dgoulet: there's the -12 issue, and there's the issue that teor believes should be -13. 17:23:18 nickm: yes what do you need from me on those? basically weigh in for the -13 ? 17:23:25 yes please on that one 17:25:23 I think I"m going to propose a revision in our security policy to split "high" into "high"/"critical" 17:25:33 so, that'll be going around too, and I'd like comment 17:26:00 critical > high ? 17:26:04 y 17:26:13 and the last thing is that I think I was useful last week when people grabbed blocks of time for me to chat about their ongoing design stuff. Please feel free to do that again this week if you're trying to figure anything out 17:26:18 and that's all for me 17:27:27 anything for me , 9or do we move on to asn below? 17:27:46 dgoulet: i didn't have any rotation duties in november, but you had one, do you mind if i take your rotation duties next week? 17:27:52 ahf: sure go 17:27:53 asn's question is "is asn missing aqnything we need asn to do"? 17:28:24 dgoulet: thanks 17:29:19 asn: not on my side 17:29:19 nickm: i guess we good here 17:29:33 ok. So, I think we may be out of discussion topics. Does anybody have anything else? 17:30:01 if not we can end early 17:30:09 and everybody can review one of the tickets in review-group-26 17:30:13 oh! should we find a conclusion for the meeting time before next week? 17:30:22 oh, indeed we should. 17:30:42 What does the takeaway from the thread look like? 17:30:49 i interpret the consensus as 18:00 UTC is ok but opinions mixed on tracking DST; does that sound right? 17:30:54 yep 17:31:11 so one hour up 17:31:17 I didnt reply yet. I am in favor of tracking DST 17:31:20 and on the ml thread it was mentioned if europeans were OK with it, and i think both asn and i said ok during last meeting? 17:31:40 okay. So let's say that it's 1800 UTC, and defer a DST decision for a couple of months :) 17:31:41 wait, it's 17:30 UTC now, right? so 18:00 is one hour later 17:31:42 we will have to figure out how to avoid conflicting with tbb-team once they go back to 18:00 UTC 17:31:47 im good with 18:00 change, and fine with tracking DST 17:32:06 i like that so i dont eat as i am in the meeting :) 17:32:26 Let's say that we _are_ tracking DST (us or eu?) and that we can change our mind between now and the dst transition? 17:32:33 nickm: yes ye syes 17:33:13 okay. Anything else for this meeting? 17:33:26 cool! so 18 next week 17:33:33 great 17:34:15 GeKo: isabela: i created #24432 and #24433 17:34:24 thanks 17:34:53 okay. Going to call the meeting done; I'll be hanging around on #tor-dev for at least another 30 min before I go grocery shopping though 17:35:24 cool 17:35:31 Thanks, everybody! Let's end 2017 in privacy-enhanching style. 17:35:33 #endmeeting