17:00:15 #startmeeting Network team meeting, 28 october 2019 17:00:15 Meeting started Mon Oct 28 17:00:15 2019 UTC. The chair is ahf. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:21 c1e0: i dont know, i use lektor build && lektor server 17:00:22 hello everyone o/ 17:00:32 o/ 17:00:39 hi all! 17:00:44 our pad today is at https://pad.riseup.net/p/tor-netteam-2019.1-keep 17:01:23 the meeting next week is gonna be on wednesday the 6th of november at 23:00 UTC, so remember we wont have a meeting on monday :-) 17:01:24 o/ 17:01:43 let us start by looking at our 042 status 17:01:49 https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases/042Status 17:02:07 we have some owner = none tickets it seems 17:02:21 what do you hope happens there, nickm? we delegate owners to them or? 17:02:45 looking... 17:03:03 #32103 has a patch, so it doesn't need an owner unless it needs substantial revisions. 17:03:10 no priority = very high tickets have shown up since last week, that is good 17:03:20 #32140 and #32141 seem like they should get split between asn and dgoulet, given the topic? 17:03:37 #32143 doesn't block a release IMO. 17:03:48 what is ALL_BUGS_ARE_FATAL ? 17:04:13 a compile-time option that turns tor_assert_nonfatal() and BUG() into crashes. 17:04:21 should we move #32143 to 043? 17:04:26 oh, ok, smart. i didn't know of that 17:04:38 Unless teor wants to do it themself? Not sure. 17:04:59 i will ask on the ticket 17:05:29 ok, commented 17:05:47 I've assigned #32140 and #32141 17:05:53 thanks, dgoulet! 17:06:20 ok, and catalyst is set as reviewer of #32103, great 17:06:28 anything else we need to dive into around 0.4.2 today? 17:07:08 not by me. 17:07:22 okay, let's move on to our roadmap: https://pad.riseup.net/redirect#https%3A//dip.torproject.org/torproject/core/tor/boards 17:07:52 hm, i wish we could somehow merge the anti-censorship items and these here 17:07:58 scrolling sideways should work nicer now 17:09:10 ok, both this and anti-censorship one looks ok for me 17:09:26 my tickets look ok to me. everybody else see there work there? 17:10:13 a yes will do 8) 17:10:26 looks fine on my side 17:10:56 are we just the 4 of us today? 17:11:03 mikeperry, asn: you two around? 17:11:44 ahf: yah 17:11:55 oki, cool! 17:12:06 okay, let's go to review assignments 17:12:13 i think dgoulet did it earlier today 17:12:18 yup 17:12:25 only 3 tickets, I killed one right away :P 17:12:25 does anybody have anything they need to shuffle around or wont have time ot do this week? 17:12:29 nice :-D 17:12:39 i got rid of mine pretty quickly after assignment i think, was also a small one 17:13:06 i wonder if there was only 3 because people have been so good at asking each other for reviews during the week. if that is the case, awesome! 17:14:15 we have #32213, i am gonna take that one for now and hope to give it a skim tonight, but i might need someone to help me follow up with teor over the week as i will be less online than usual 17:15:00 ok taken 17:15:24 please remember to update the october pad with updates to what you have been up to. i'd like to send out the october status email on monday 17:15:44 remember next week there is the s31 meeting on the 5th of november at 23 UTC 17:15:51 We have some work to do to get it in that state; I think you may need to start chasing people down 17:15:59 I've made notes there, but they could be expanded into paragraphs 17:16:10 nickm: yeah, i will 17:16:30 and i will also expand some of it, last month the report was largely taken from a sponsor report, but i think i will need to do some expansion for this one too 17:16:48 okay, to the discussion points 17:16:54 * C style poll: results sent to the network team list. What next? 17:17:02 i think nickm wants to lead that one 17:17:36 ... unless someone else added it? 17:17:41 I send out the responses last week 17:18:01 My next step was to write up my opinions on what the responses show us, and my opinions on next steps in each area. 17:18:10 I've got those written, and I want to send them out after the meeting 17:18:22 (I finished writing them 15 minutes before the meeting, and didn't want to be distracting.) 17:18:49 In some cases we have clear consensus; in sme we have none, and in some cases our only consensus is that we should follow through on the consensus that we do not have :) 17:18:59 but there are lots of areas where we broadly agree 17:19:13 I think next steps is for people to react to what I write and let me know what they think? 17:19:49 i think that sounds like a good next step 17:20:25 maybe split things up in the "easy ones" (the ones where we have mostly consensus) and then the ones where we are a bit further away from each other, so we don't end up spending too much time on things we mostly agree on? 17:21:11 maybe! I think we can make some good progress pretty fast. 17:21:24 oki, cool! 17:22:25 anything else to this? 17:22:44 otherwise we hve the commit bits for ci and review roles proposal by teor that is in status = voting right now, so people should be voting! 17:23:26 * ahf moves to needs help with 17:23:39 catalyst needs some help with #32103 - some additional review would be nice 17:23:53 it is related to some threading stuff now that the bot wont say the ticket info 17:23:58 anybody up for helping here? 17:24:14 I'm not seeing the first round review? 17:24:21 looks like CI is failing on that ticket... 17:24:34 nickm: i'm going to write up my first round soon 17:24:44 catalyst: kick it to me once that is done? 17:24:46 nickm: CI failure is practracker; i'll make a note in my review 17:24:55 ack 17:25:18 dgoulet: asn have a question for you on the pad for S27 october report 17:25:23 yes 17:25:49 you are on it? cool! 17:25:54 yes yes 17:25:56 anybody else who have anything we need to talk about this week? 17:26:30 i will be traveling some of the time this week, so will be less online. send an email or expect a bit slowness on irc 8) 17:26:51 cool! 17:26:54 happy hacking everyone! 17:26:56 #endmeeting