17:01:28 #startmeeting network team meeting 17 Jun 17:01:28 Meeting started Mon Jun 17 17:01:28 2019 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:28 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:01:31 hi folks! 17:01:45 https://pad.riseup.net/p/tor-netteam-2019.1-keep is our pad 17:02:47 hi 17:02:59 o/ 17:03:03 looks like a new tor browser came out last week, and we _aren't_ getting flooded with bug reports on 0.4.1.2-alpha 17:03:06 so that's good news! 17:03:15 o/ 17:03:22 looking at the 041 status page: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases/041Status ... 17:03:51 hello hello 17:03:54 Nearly all of the tickets we have there are unassigned. They're pretty much all "should" rather than "must", so that's good. 17:04:05 hi dgoulet gaba catalyst ahf ! 17:04:18 asn and mikeperry are headed to mozilla allhands, and teor is asleep. 17:04:42 cool 17:05:35 What should we do with the remaining unassigned 041-should tickets? I think maybe we should see if we believe that any are important to do before rc. If so, we should assign them. If not we should defer them? 17:08:03 hm. sounds like nobody else is sure either 17:08:12 do any of these look must-do to anybody? :) 17:08:27 hm 17:08:34 weird we haven't gotten more bugs on #27331 17:09:04 hm, david has hit it, once 17:09:05 hmmm #30871 needs to be looked at 17:09:34 been a while I hit that iirc ^ 17:09:42 (hmmm #27331 I meant) 17:09:45 dgoulet: do you think you or asn could take it? it seems to be hs code. Alternatively it should be mike or asn, since it could be caused by the "keep open" logic for padding 17:10:14 what about #30409? 17:10:22 nickm: yeah I'll need to check it out 17:10:37 ok, thanks! 17:10:54 gaba: It's not a must-fix, but it _is_ a should 17:11:16 I can try running the tests again on a laptop with networking turned off... 17:11:24 ... but I don't have a nice convenient no-net setup ready to go 17:13:11 I'll try it with what I can reproduce, though, and defer the rest till there is better info 17:15:11 next topic is roadmap 17:15:14 do we have anything to update there? 17:15:18 let's have a look! 17:15:31 once we're done with that, let's look at reviews 17:16:47 sorry, my internet is very slow today for some reason, still loading :-/ 17:19:17 ok, looks ok to me 17:22:09 it looks like the WIP schedule for the tor meeting is still there, so let's keep working on it 17:22:12 I'm not seeing new other announcements this week, but please remember the old ones. 17:22:31 yep 17:22:34 with that, I think we might be out of fresh discussion topics 17:22:45 is there anything else to talk about? 17:23:36 (asn has a "help needed" message for teor) 17:24:01 Would it make sense to schedule IRC meetings for proposals 303 and 305 between now and Stockholm? 17:24:47 I'm personally fine with public email discussions on those. They aren,t that big 17:25:13 ok 17:25:36 I was wondering whether the amount of feedback had crossed the point where we needed an IRC meeting, but if we can still do it on tor-dev, then great 17:25:48 gaba: do you know anything else we should talk about this week? 17:25:51 or does anybody? 17:27:35 * ahf is good 17:27:51 no, I think we are good 17:27:52 i have arranged with asn that i'm on this weeks ci/coverity as well in case there is anything 17:27:55 haven't updated the rotation page with it 17:27:56 thanks ahf 17:28:37 ahf: thanks. have you updated the rotations wiki page? 17:29:24 nope, gonna do that 17:29:43 thanks! 17:30:20 okay. Sounds like we're out of stuff for now. Cool! 17:30:27 I'll see you all online in that case 17:30:30 cheers! 17:30:31 #endmeeting