[tor-project] Network team meeting notes, 2 July 2018
Nick Mathewson
nickm at torproject.org
Tue Jul 3 17:50:57 UTC 2018
Logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-07-02-16.58.html
Pad contents below:
====
= Network team meeting pad, 2 July 2018 =
Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC.
(This channel is logged while meetings are in progress.)
Want to participate? Awesome! Here's what to do:
1. If you have updates, enter them below, under your name.
2. If you see anything you want to talk about in your updates, put
them in boldface!
3. Show up to the IRC meeting and say hi!
Note the meeting location: #tor-meeting on OFTC!
(See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.html
for background.)
== Previous notes ==
23 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001747.html
30 April: https://lists.torproject.org/pipermail/tor-project/2018-April/001750.html
7 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001760.html
14 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001769.html
21 May: https://lists.torproject.org/pipermail/tor-project/2018-May/001806.html
11 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001828.html
18 June: https://lists.torproject.org/pipermail/tor-project/2018-June/001835.html
25 June: https://lists.torproject.org/pipermail/tor-project/2018-July/001863.html
== Stuff to do every week =
* Let's check and update the roadmap. What's done, and what's coming up?
url to roadmap:
https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=856122210yy
* Check reviewer assignments at
https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=95993070
* Also, let's check for things we need update on our spreadsheet! Are
there important documents we should link to? Things we should
archive?
* Check rotations at
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRotations
* Community guides, it's time to hand off to the next guide!
* Let's look at proposed tickets!
== Announcements ==
* Tor 0.3.1 has reached end-of-life.
* Remember to "/me status: foo" at least once daily.
* Remember that our current code reviews should be done by end-of-week.
* Make sure you are in touch with everybody with whom you are doing
work for the next release!
* The git master branch is now 0.3.5!
== Discussion ==
Any volunteers for handling backports to stable?
teor asks: what's the timeframe?
Can people help out for particular releases? End of life for 0.3.2 is
October, and 0.3.3 is February.
(I don't know if that will work so well unless we coordinate. It
would be messy if something were backported to e.g. 0.2.9 but not
0.3.2. -NM)
Any volunteers for leading 0.3.5 triage process?
teor asks: 0.3.5's feature freeze is September 15, so do we need
triage done in July or August?
(IMO now -NM. Working on with ahf.)
Do we need a volunteer to focus on the remaining bugs in 0.3.4?
(isis will make sure every must bug has a person who remembers
they're working on it.)
Where is the work-in-progress guide for big patches in Tor? Is this
based on the Seattle notes or is there more info there? [komlo]
[catalyst will send komlo a link. We're keeping this unpublished
until we like it more, since it has potential to read as obnoxious if
we get it wrong.]
== Updates ==
Nick:
* Last week:
* Get 26479 and 26480 (appveyor failures) fixed so I can
release 0.3.4.3-alpha.
* Release 0.3.4.3-alpha.
* Prepare for an 0.3.3.6 release
* Continue refacatoring src/common
* Make the dependencies in src/libs acyclic.
* This week:
* Plan an order of operations for splitting src/or.
* Open tickets about remaining cases of #25386 (sanitizers, rustdoc).
* Document src/lib.
* Make requested post-merge cleanup changes in src/lib structure.
* Release 0.3.3.8
* Finish PETS reviews
teor (offline):
last week:
- Reviewed juga's patch to put bandwidth file headers in votes (#3723)
- Other small bwauth suggestions and feedback
- Helped answer some fallback questions
- We have 30 new fallbacks, we need another 40 fallbacks for
censored clients to bootstrap
(Maybe it will take a few more weeks to get there.)
https://trac.torproject.org/projects/tor/ticket/24805#comment:33
- Two successful experimental PrivCount data collections
- And the research is done!
this week:
- Review PrivCount in Tor blinding and secret sharing branch
- Implement PrivCount in Tor noise
- Work on a per-relay / per-consensus / per-counter noise spec
for PrivCount in Tor
- Reduce my review and revision backlogs
ahf
Last week:
Sponsor 8:
- Better process handling for #25502 update: started to
write the Windows related code, but ran into #26594 as a blocker.
Spend some time trying to figure out what the issue was.
Misc:
- Reviewed #24104, #26594, first look at #24546.
- Continued study of Chrome's Windows sandbox implementation.
This week:
Sponsor 8:
- Finish Windows specific parts of #25502 (reading of output from
subprocesses).
- Memory profile work with Nick and David(?)
Misc:
- Look at the remaining Coverity issues from week 25 (bug #26521).
- Rotation role: Bug triage.
- Figure out Mexico logistics: We have no meetings before
the team day? No
meetings after the schedule on trac?
(This is correct -NM.)
- Hope to be able to lift Chrome's Windows sandbox out as a small
C++ library to play around with.
- I'm away most of Wednesday (US time).
- Do phase 1 triage with Nick:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TicketTriage
haxxpop:
Last week:
- Revise the PR according to dgoulet's comments
This week:
- Continue revising the PR
komlo (offline):
- Last week:
- Prepare for some public talks (not much hands-on tor work)
- This week:
- Follow up and test out #24249 with
https://github.com/eqrion/cbindgen. Overall, I think we definitely
want to compile Rust->C types, as opposed to using bindgen as we would
still need manual translation for libc types. More analysis on the
ticket if anyone is interested.
Mike:
Last week:
- Feeling a bit paralyzed by choosing which semi-urgent thing to
prioritize (Sponsor2 work, Sponsor2 report, PETS Research Blog posts,
vanguards experiments, vanguard packaging, vanguards blogposts,
figuring out how the hell to pay PETS attendance, accumulated
bureacracy since vacation). Treaded a bit of water trying to figure
out which thing to do.
This week:
- Hopefully now have a plan:
- Backburner Vanguard performance experiment and just choose
consservative 2-3-8 params
- Write a vanguards release blogpost draft, circulate to asn
- Write PETS research blogpost draft, circulate to ???
- Ignore the bureacracy because fuck it.
asn:
Last week:
- Finalized #25552. Been testing it for the past weeks and it's working great!
Ensured that it addresses the issues onionshare has been seeing as
well as #26549.
- Reviewed #26479, #26480, #26425.
- Discussed onion name systems with Mike and others. Now that v3s are getting
more and more deployed, it's important to start fixing this big UX barrier.
This week:
- More reviews.
- Catching up with leftover 035 deliverables.
catalyst:
last week (2018-W26):
- CI rotation -- included some Jenkins issues like #26503
- reviewed some cross-compilation tickets (#25895, #25977)
- made some progress on the big patches doc
- helped with a few minor glitches from the refactoring
commits (thanks for working on the refactor, Nick!)
this week (2018-W27):
- Coverity rotation
- code review
- more work on big patches doc
- follow up on some Rust-related tickets as needed
- dealing more with flaky internet access
- July 4 off because holiday
isis:
last week:
- took tuesday through thursday off to attend zcon0
- reviewed #25386 #24249
this week:
- back to the create cell work
- catching up on backlog
- 1:1:1 meeting on tuesday at 10am PST
- july 4 off
More information about the tor-project
mailing list