17:00:06 <nickm> #startmeeting weekly network team meeting
17:00:06 <MeetBot> Meeting started Mon Jun 27 17:00:06 2016 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:06 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:14 <huseby> GeKo: ok
17:00:23 <nickm> hello! it's 1700 UTC and time for the weekly network team meeting
17:00:29 * huseby slowly backs out of the network standup :)
17:00:36 <nickm> apologies to GeKo and huseby: you seem to be very productive. :)
17:00:40 <GeKo> huseby: see my comment 1 in that bug
17:00:47 * GeKo is following huseby
17:00:55 <huseby> nickm: no worries mate :)
17:01:03 <nickm> athena, dgoulet, asn, isis, armadev, isabela, yawning-who-is-not-here-today: hi hi
17:01:12 <athena> greetings meeting
17:01:15 <nickm> hello!
17:01:28 <nickm> athena: would you like  to do first checkin this time?
17:01:58 <U039b> hello
17:02:06 <nickm> hello uppercase-lambda! :)
17:02:13 <athena> status: the plumbing, but not the actual kill-some-connections heuristic for #18640 is done; i put the ticket in needs_review in hopes someone will look at it and tell me if it looks silly before i write that bit
17:02:14 <U039b> :)
17:02:41 <athena> #19323 can answer queries about consensus downloads but not the other three occurences of download_status_t yet
17:02:52 <athena> that's it
17:02:57 <nickm> neat
17:03:23 <nickm> I've been workign on a revised revision of prop259, trying to turn it into something less synchronous with a less stale proposal.
17:03:47 <nickm> (the old proposal draft refered to no-longer-used terms, and had some gaps, and didn't do too well with multiple circuits launched at once)
17:04:16 <nickm> after that I want to do reviews and then try to bang my long-dormant #15055 branch into something like a good shape to finish
17:04:49 <nickm> We picked up a huge amount of needs_review stuff over the weekend: anybody who can review any of them would take a big load off me.
17:04:53 <nickm> and that's it for me.
17:04:56 <nickm> who's next?
17:05:21 <nickm> (I believe Yawning is off trying to get all his end-of-month PT stuff done.)
17:05:42 <isabela> yep
17:05:43 <nickm> earlier, armadev said that he is going to try to do "some thing" on each of his end of june tickets.
17:06:02 <nickm> Yawning: whoa!
17:06:10 <nickm> hey, welcome.  I just said:
17:06:12 <isabela> i was working on proposals last week this week will be pt stuff
17:06:14 <nickm> > (I believe Yawning is off trying to get all his end-of-month PT stuff done.)
17:07:16 <Yawning> indeed
17:07:29 <nickm> isabela: anything we should be doing to help you out?
17:07:30 <Yawning> trying not to be distracted by the world burning down around me
17:07:39 <nickm> isabela: next week we
17:08:03 <nickm> isabela: next week we will need to pick July work.  Will you have time to help finish 029 triage for S and U before we reach that point?
17:08:12 <isabela> yes
17:08:16 <isabela> that is on my list too
17:08:29 <Yawning> nickm: quick question, should I clean up our openssl v 1.1.0 stuff, or is my branch that just puts const in strategic locations sufficient?
17:08:41 <nickm> I haven't looked yet, hang on.
17:09:00 <Yawning> k
17:09:12 <Yawning> I sort of think ti's orthogonal
17:09:16 <nickm> #19497 , right?
17:09:49 <Yawning> uh
17:09:50 <nickm> isabela: okay. Could I ask you to schedule any meeting you want to have about that with me (and maybe others) soon, so that I know what time to reserve?
17:10:02 <Yawning> 19499
17:10:13 <nickm> Yawning: ok
17:10:22 <isabela> sure -- better mid-end of week for me
17:10:23 <Yawning> the other one is someone that has a messed up toolchain, autoconf issues, or didn't build openssl right
17:10:26 <nickm> Yawning, dgoulet, athena : btw, was there a patch I was supposed to look at for the coverity stuff?
17:10:30 <nickm> Yawning: ok
17:10:37 <Yawning> I didn't write one
17:10:42 <isabela> thursday would be a good day
17:10:47 <Yawning> I can, since it broke my build, but I'm busy with other stuff
17:10:51 <isabela> or wed
17:11:01 <nickm> I think Wed would be better for other stuff.
17:11:04 <nickm> err
17:11:14 <nickm> I think Wed would be better; Thursday I expect to be super busy with other stuff
17:11:18 <isabela> ok
17:11:20 <isabela> ;)
17:11:23 <isabela> wed it is
17:11:36 <nickm> isabela: should we pull in athena and yawning, or shall we just wrap this up ourselves? I think we're close enough.
17:11:57 <isabela> we should have everyone
17:12:14 <isabela> so wed - what time is good for folks, my schedule is pretty easy
17:12:24 <athena> i have no plans on wednesday
17:12:38 <nickm> I can do all day wednesday from 830am to 4pm edt.
17:12:49 <nickm> == 1230 through 2000 UTC I think
17:13:31 <isabela> 12pm pdt 3pm edt
17:13:33 <isabela> is that ok?
17:14:01 <nickm> athena, Yawning: how is that for you?
17:14:05 <athena> hmm, 9pm my time - yeah, I think that's fine
17:14:15 <isabela> we can do earlier too
17:14:34 <Yawning> dunno, depends on how on fire my life is
17:14:37 <Yawning> and it's really on fire
17:14:51 <nickm> Yawning: your #19499 branch looks fine to me.  A cleanup would be okay in 029 if you want to but I don't think it's an 028 blocker
17:15:01 <nickm> Yawning: (you agree?)
17:15:41 <isabela> (ok lets keep it at noon pdt on wed for now)
17:15:50 <nickm> ok.
17:16:09 <Yawning> nickm: ack, though if I do clean up, 028 would be nice to keep code divergence down
17:16:12 <nickm> Yawning: if you won't be able to make that, please ping me or isabela some time around that day?
17:16:19 <Yawning> yes
17:16:39 <Yawning> but I think the current code is readable and maintainable, so even that is just a "would be nice" thing
17:16:40 <nickm> anybody else with a checkin ?
17:17:00 * nickm wonders where my sponsor R peeps are
17:17:07 <dgoulet> hi!!
17:17:10 <nickm> hi dgoulet !
17:17:11 <dgoulet> so sorry
17:17:11 <isabela> hehe
17:17:32 * dgoulet typing a report
17:17:58 <dgoulet> No surprise, I worked on prop224 (#18571 in particular). asn is currently doing a first pass on the encoding part. I'm finalizing the decoding part (still ongoing work). Update happened on the proposal as well from asn for which I went over it.
17:18:17 <dgoulet> Also some random review and ticket work also, nothing major patch wise just few things on the baseXX APIs among other things.
17:18:37 <dgoulet> Also did a release candidate of torsocks 2.2.0. I cleaned up in a big way the torsocks tickets so yay! cleaner trac.
17:18:46 <dgoulet> I think that's about it for little-t
17:20:58 <nickm> ok
17:21:01 <nickm> asn: you around?
17:21:06 <nickm> or anybody else with an update?
17:21:17 <nickm> if not, we can move to discussion!
17:21:26 <nickm> anybody with topics for discussion other than me?
17:21:28 <nickm> My topics are:
17:21:35 <nickm> - code review status
17:21:40 <nickm> - next 0.2.8 release
17:21:53 <nickm> - that indentation convention we talked about
17:22:04 <nickm> any others?
17:22:57 <nickm> ok.
17:23:08 <nickm> then let's talk about indentation, since that is absolutely not a bike shed
17:23:31 <dgoulet> what is this about?
17:23:49 <nickm> that thread about "hey should we have an indentation/braces convention".
17:23:58 <dgoulet> oh the one I sent?
17:24:01 <nickm> yeah
17:24:03 <dgoulet> that was just for {} around if  :)
17:24:05 <nickm> ah
17:24:07 <dgoulet> indentation is fine for me
17:24:14 <dgoulet> what I asked was for {} around oneliner if
17:24:19 <nickm> I don't think we're going to require { around every if.
17:24:46 <dgoulet> discussion over then? ;)
17:25:07 <nickm> we should probably get a builder that uses gcc6 though, so we find out about this stuff nice and early.
17:25:24 <nickm> discussion can be over then.
17:25:33 <Yawning> yeah, if gcc6 didn't warn about it, I'd consider it
17:25:56 <Yawning> if people want to explicitly add braces around stuff that's subtle/needs to be unambiguous, they should feel free
17:25:57 <Yawning> imo
17:26:10 <dgoulet> nickm: so right this ^ are you fine with it
17:26:13 <nickm> 0.2.8 release: I see 6 changelog entries in the current 028 directory.  I think another release candidate this week might be in order.
17:26:32 <nickm> dgoulet: you mean, "am i okay with adding braces" ?  Yeah.
17:26:47 <dgoulet> nickm: yup if I do oneliner if with {}, you won't nack?
17:26:55 <nickm> nope; go ahead.
17:26:58 <dgoulet> ack
17:27:08 <Yawning> I just don't want to be forced into putting braces around something trivial :P
17:27:13 <nickm> also I think that we should never have "} else" or "else {".  Only "else" or "} else {" ;)
17:27:27 <Yawning> nickm: ack
17:27:32 <dgoulet> Yawning: triviality is not the point here but blah... discussion over and you all got my points on that anyway :P
17:27:43 <Yawning> braces should be consisent
17:27:46 <dgoulet> nickm: +1
17:27:53 <nickm> anybody think we should do anything different from what I said above on the 028 issue?
17:28:16 <dgoulet> nickm: sounds good
17:29:29 <nickm> ok. code review status: I saw a lot of tickets with tiny little patches this weekend -- many to the spec.  If anybody grabs any of them for review, that would be grand.
17:29:41 <nickm> most would take like 3 minutes each, I hope
17:30:10 <nickm> any other questions and discussion topics? Any tickets where people need answers from me on something?  Anything blocking on me that I don't know about? :)
17:30:23 <dgoulet> nickm: yes
17:30:34 <nickm> go for it!
17:30:35 <dgoulet> nickm: you are still aware of the ticket of making it harder to become a HSDir?
17:30:36 <dgoulet> :)
17:30:47 <nickm> dgoulet: hrmgn. what's the status there?
17:30:55 <dgoulet> #19162
17:31:00 <dgoulet> nickm: we need your help on an issue
17:31:57 <nickm> ah, hm.
17:32:13 <dgoulet> nickm: there is a possibility that our uptime computation is either broken or we don't use it right or ..
17:32:14 <nickm> okay, I can try to make some progress there maybe, but I am pretty full up this week
17:32:21 <nickm> I'll try to take a look though
17:32:24 <dgoulet> nickm: it's 029 so no rush
17:32:34 <Yawning> yeah cuz everything is on fire
17:32:35 <dgoulet> nickm: just that we really need you in the end :)
17:32:48 <Yawning> and I'm having beer for breakfast
17:32:57 <dgoulet> Yawning: _not_ a good idea
17:33:25 <isabela> +1 (especially after the 'beer man' saying it)
17:33:37 <dgoulet> oh dear I have a label ahah
17:34:16 <nickm> beer is a dinner food. even if it says "breakfast stout"
17:34:31 <nickm> any other discussion topics for today?
17:34:32 <dgoulet> agree, rarely at lunch but neer ideal anyway
17:34:40 * dgoulet is good
17:35:40 <isabela> ok i will jump back to my stuff is a packed week
17:35:57 <Yawning> I have nothing to say, so have a picture of Scalia and Ginsburg on an elephant https://i.imgur.com/ivq26Vj.jpg
17:37:28 <dgoulet> wat the..
17:37:35 <U039b> I sent an email about rb tree and ds, I just wonder what's next :)
17:37:43 <nickm> U039b: let's do that after the meeting?
17:37:50 <nickm> I will need a 2 minute break to make myself some tea
17:37:59 <U039b> nickm: ok
17:38:04 <nickm> (I started writing a fast response over the weekend, then realized I was wrong)
17:38:06 <nickm> #endmeeting