16:59:42 <nickm> #startmeeting weekly network team meeting
16:59:42 <MeetBot> Meeting started Mon Mar  6 16:59:42 2017 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:42 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:07 <nickm> ahf dgoulet asn isabela dgoulet teor: hi!
17:00:12 <ahf> hi!
17:00:18 <nickm> mikeperry armadev: hi to you too!
17:00:19 <isabela> !
17:00:37 <nickm> so, status updates.
17:00:59 <dgoulet> hi
17:01:03 <nickm> last week I tried to do a bunch of sponsor4 research, and I put out a bunch of releases
17:01:13 <isabela> release machine!
17:01:22 <nickm> this week I hope to get a bunch of code reviewed and merged, and to get some actual code written for sponsor4 stuff
17:01:38 <nickm> after the meeting I hope to work on 031 ticket triage
17:02:00 <ahf> good job on the releases - that was impressive to observe
17:02:42 <nickm> I'm planning to try to take it a little bit easy towards the end of next week, to ensure I show up to the amsterdam meeting in a well-rested state; I suggest others plan to focus on taking care of themselves too. :)
17:02:46 <nickm> thanks!
17:02:54 <nickm> and that's about it for me.
17:03:02 * ahf can go
17:03:04 <haxxpop> Hello everyone !!
17:03:06 <nickm> plesae do!
17:03:09 <nickm> hi haxxpop !
17:03:15 <ahf> Hello. Finished the sampling period for #21205 & #21206. Wrote a Python script for parsing the logs and extracting the useful data needed by us (cell count sent/recv, size, directory documents, etc.). Need to make it look nice and understandable now such that it can be used to compare results as we progress with Sponsor4 tasks. Discovered Facebook's zstd compression scheme randomly on Twitter, extended our
17:03:21 <ahf> compression 'bench' tool to include zstd. The
17:03:23 <ahf> results looks promising. Got feedback from Nick & Tim on the HTTP compression content negotiation proposal, which will be out on tor-dev@ for public discussion, fixed an issue that is causing our FreeBSD BB's to fail. This week will hopefully mostly be coding 8)
17:03:49 <ahf> and i'm starting to looking forward to the amsterdam meeting too! everyone says it's very intense as well :-D
17:03:56 <ahf> that's it
17:05:13 <nickm> (also please don't forget to open those tickets from our pad this morning)
17:05:16 <nickm> who's next? :)
17:05:18 <dgoulet> here
17:05:21 <nickm> hihi
17:05:22 <dgoulet> Hello! Reviewed some HS tickets. teor opened many of them and I need to go over them again. Reviewed also asn's prop224 branch for the current descriptor code to match the spec for the superencrypted scheme.
17:05:26 <dgoulet> I'm *almost* done I believe with circuit/cells implementation for #20657. We are on the last stretch here for this huge branch that I still want almost done for AMS. Last piece will be the upload descriptor logic.
17:05:38 <ahf> nickm: nope, wont forget it - almost there for it
17:05:42 <nickm> great
17:05:45 <dgoulet> bad relays took a bit of my time last week as well, quite a surge of those
17:06:06 <dgoulet> so yeah basically we see the light at the end of the tunnel for prop224 service
17:06:21 <nickm> that will rock
17:06:24 <dgoulet> AMS will bring many discussions about logistics with me and asn at least about how to present that HUGE thing for review and merge
17:06:30 <dgoulet> but we are confident :)
17:06:33 <dgoulet> done
17:06:46 <nickm> I just reviewed asn's revised encoding branch again; it looks good
17:06:56 <dgoulet> yeah just saw, _great_! :)
17:06:57 <nickm> anybody else?
17:07:03 <nickm> asn / isabela ?
17:07:04 <isabela> i was in seattle last week meeting everyone about everythign )
17:07:28 <isabela> brad (cfo) armadev, cass (grant writer), linda and alison and so on
17:07:49 <isabela> this week i am trying to finish reports and help out with organizing to the next release
17:07:53 <isabela> done
17:08:00 <nickm> asn: you around today?
17:08:07 <nickm> anyone else with an update?
17:08:19 <dgoulet> asn is in a some mountain cabin ;)
17:08:24 <nickm> ah awesome
17:08:38 <nickm> I hope he's having a good time
17:08:48 <haxxpop> I'm still working on generating responsible hsdirs but having some problems with ed25519 id key
17:08:48 * isabela looks for smoke signs
17:08:55 <ahf> :-S
17:09:07 <dgoulet> haxxpop: maybe I can help after the meeting?
17:09:11 <mikeperry> I needed to review the TBB design doc updates for GK. I will also be doing the Firefox networking code review for the ESR 52 switch for the TBB team this month, too
17:09:14 <haxxpop> dgoulet, thank you
17:09:52 <mikeperry> so I may not be very network-teamy this month :/
17:09:55 <nickm> mikeperry: I propose the following plan for your open needs_review stuff then...
17:10:31 <nickm> If you get all the spec issues done (or have them done already) I will do my best to grab you and roger in Amsterdam.  But if I can't, I'll plan to merge immediately after amsterdam anyway. This deserves testing.
17:10:55 <nickm> It would be good if armadev got back to me before amsterdam, hint hint :)
17:11:01 <nickm> how does that sound?
17:11:09 <dgoulet> [testing network standing by] :D
17:11:24 <mikeperry> thayt sounds fine. the spec changes are there, I just need to copy-paste them back into the proposal
17:11:29 <nickm> So, my only discussion issue this week is 031 triage.  Any more?
17:11:40 <nickm> mikeperry: thank you!
17:12:21 <dgoulet> no discussion point from me
17:12:26 <nickm> ok. right now we have 144 tickets in 031.  We probably won't get them all done by the freeze date in Mid-May.
17:13:07 <nickm> so, better to focus early than late.  It's easier to add more if we get ahead than to recover when we're running late
17:13:50 <nickm> So what I propose is, after this meeting, we try to categorize the items in 0.3.1 now.
17:14:04 <nickm> 1. If it belongs to a sponsor, please assign it to that sponsor, either with the sponsor field or a keyword.
17:14:22 <nickm> 2. Please make sure it is accepted/assigned iff the owner actually plans on doing it.
17:14:36 <nickm> 2a. Especially if the owner is you
17:15:02 <dgoulet> may I propose also that we identify and prioritize the big feature we want in
17:15:03 <nickm> 3. If it has neither a sponsor nor someone who plans on doing it, please mark it "High" severity or higher if you think it's super-important to fix.
17:15:16 <nickm> dgoulet: sounds good!
17:15:27 <nickm> as in https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases ?
17:15:45 <dgoulet> nickm: yeah the list at the bottom basically
17:16:03 <nickm> I'm thinking we call the first three "Yes" and the remainder "nice to have"
17:16:05 <dgoulet> and we could use "Priority" field for the Enhancement there for 031 so we know which ticket we must push forward before mid-may
17:16:19 <nickm> err, right.
17:16:24 <nickm> in my "3." above, I should have said
17:16:40 <nickm> 3. If it has neither a sponsor nor someone who plans on doing it, please mark it "High" _priority_ or higher if you think it's super-important to fix.
17:16:49 <dgoulet> great
17:17:20 <isabela> (btw here has some resources e.g. guidance on how to add points https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/ReleaseGuidelines)
17:17:21 <nickm> Some time tomorrow, I'm going to plan to defer most or all of the items that are none of: {assigned, accepted, sponsored, needs_{review,revision}, high-priority}.
17:17:37 <nickm> and please make sure there are "points" set for anything you're planning to do
17:18:08 <nickm> if your points total is higher than ~25 you're probably going to have a bad time
17:18:18 <nickm> or maybe not
17:18:21 <nickm> we'll see :)
17:18:24 <isabela> hehe
17:18:45 <nickm> Any more to talk about on this meeting or for the triage?
17:19:07 * dgoulet is good
17:19:28 <isabela> everyone knows the right query to see what is on 031 now (the 144 tickets)
17:19:29 <isabela> ?
17:19:49 <nickm> https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&milestone=Tor%3A+0.3.1.x-final&group=status&max=150&order=priority
17:19:54 <isabela> tx nickm
17:22:36 <nickm> ok.  I'll start working on triage and points.
17:22:41 <nickm> oh! it's isis!
17:22:50 <nickm> hi, want to drop a status report?  we're just about to wrap up.
17:22:57 <isis> hello :)
17:23:03 <dgoulet> nickm: I'm triaging anything with tor-hs and 031
17:23:21 <nickm> dgoulet: cool!  Please also look through the non-tor-hs tickets to see if any of them _should_ be tor-hs?
17:23:56 <dgoulet> yes
17:24:00 <nickm> woo!
17:24:34 <dgoulet> nickm: I'll bump priority of prop224 ticket also just so we keep it on top of the list :)
17:24:38 <isis> sure, i spent most of last week working on the spec paper thing, and some time actually coding the credentials and working out some logic about the zero-knowledge statements we need to make inside the anonymous credentials
17:25:30 <isis> some other time was spent making travel arrangements for amsterdam, doing monthly reports, etc
17:25:36 <isis> that's it for me
17:26:08 <jvsg> isis: Did you get my email regarding prop270?
17:26:16 <nickm> ok; cool!  we're doing 031 triage today, so please check the meetbot logs for instructions if there's anything you care about that should go into 0.3.1.x
17:26:40 <isis> jvsg: i did, it's on my list of things to do to answer
17:26:48 <jvsg> isis : thanks :)
17:27:10 <isis> nickm: ok, will do
17:27:25 <isabela> isis: 031 is schedule fo may - in case this influence the otf work you are doing
17:27:29 <isabela> *for
17:28:27 <nickm> #endmeeting