[tor-project] Network team meeting notes, 6 November 2018
Nick Mathewson
nickm at torproject.org
Wed Nov 7 02:28:25 UTC 2018
Hi!
IRC logs are at
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-11-06-23.00.html
The contents of our pad are below
````````````````
= Network team meeting pad! =
This week's team meeting is on Tuesday at 2300 UTC on #tor-meeting on OFTC.
(If the time doesn't work for you, we'll see you the week after.)
Welcome to our meeting!
First meeting each month: Tuesday at 2300 UTC
Other meetings each month: Mondays at 1800 UTC (1 hour later for
daylight saving time)
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.)
After each week's meetings, the contents of this pad will be sent to
tor-project @ lists.torproject.org. After that is done, the pad can
be used for the next week.
== Previous notes ==
(Search the list archive for older notes.)
1 Oct: No online meeting; in-person meeting in Mexico City.
9 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002005.html
15 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002027.html
22 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002032.html
29 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002036.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
* Let's look at proposed tickets!
0.3.5 (bugs only):
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&keywords=~035-roadmap-proposed&max=200&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority
0.3.6: 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&keywords=~035-roadmap-proposed&max=200&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority
== Reminders ==
* 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 releases
* Remember to fill up actual point when you finish a task (as well as
"fix" the estimate when starting the issue).
* Add planned PTO to the calendar
https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbdGmxx
<< Remember that priority is Sponsor 8 - roadmap is sort out by
priority >> Activity O2.5 is the one we are missing and need to do in
2 months.
In November everybody need to start checking snowflake as it is
something that is coming in December.
-------------------------------
---- 6 November 2018
-------------------------------
== Announcements ==
Please don't bulk-delete all the old entries from this pad any more.
Instead, delete the "planned" and "actual" for the previous week, but
leave the "planned" for this week in place. <--- Check other's people
call for help in their entries.
Alpha/Master maintainer doc:
https://trac.torproject.org/projects/tor/ticket/28225
catalyst asks: which time zone switch are we following for the meeting? US?
A: Monday meeting will switch with US DST.
patch party remains fixed at 23:00 UTC.
(The EU/AU optional catch-up time is moving with EU DST.)
US DST switches on 04 Nov, but first meeting of the month is at
patch party time. So 12 Nov meeting is at 18:00 UTC.
== Discussion ==
* sponsor 8 work
O2.5 (bootstrap reporting) is most important
- right now working on this: catalyst, ahf, dgoulet, teor. any of you
need help with it?
* who else want to do snowflake?
schedule snowflake intro meeting
* who is going to answer these emails?
Dealing with frequent suspends on Android:
https://lists.torproject.org/pipermail/tor-dev/2018-November/013529.html
Why is the execute bit set on onion service keys:
https://lists.torproject.org/pipermail/tor-onions/2018-November/000338.html
Both have answers... ?
I wrote this question 24 hours ago
* neel wrote a new ClientAutoIPv6ORPort option that makes Tor choose
between IPv4 and IPv6 client connections at random:
https://trac.torproject.org/projects/tor/ticket/27490
It works well, but it could be smarter about relay weights and
systems that only have IPv4 (or only have IPv6):
https://trac.torproject.org/projects/tor/ticket/17835
Should we merge it as an experimental feature?
Decision: Merge it as an experimental feature, and if it causes
bugs, fix those bugs.
For details, see
https://trac.torproject.org/projects/tor/ticket/27490#comment:21
== Recommended links ==
Cool talk on communication in teams
http://lenareinhard.com/do-you-read-me-better-communication-for-stronger-teams/
== Updates ==
NOTE NEW FORMAT!
Name:
Week of XYZ (planned):
- What you planned for last week.
Week of XYZ (actual):
- What you did last week.
Week of ABC (planned):
- What you're planning to do this week.
Help with:
- Something you may need help with.
PLEASE DO NOT BULK-DELETE THE OLD ENTRIES!
Leave the "Planned" parts!
Nick:
Week of 10/29 (planned):
- Implement pubsub message dispatch API and subsystems API.
- Do something with consensus mmap patches. (But what?)
- release 0.3.4.next?
- Get un-stuck on #27359?
- Try to design an "extra dormant mode" for #2149
Week of 10/29 (actual):
- Implemened pubsub message dispatch API (#28226)
- released 0.3.4.9
- Started implementing subsystems logic
- Finished #27359 (family representation), adding prop298 as a
followup. Thanks to teor for brainstorming help!
- Met with S Chakravarty from IIITD
- Talked with Catalyst & Teor about bootstrapping designs and plans
- Merged memory-map patches (#27244)
- Met with asn to learn about wtf-pad
- Worked on pending funding proposal with gaba, al, isa, asn, and others
- Wrote a PETS meta-review
- Reviewed and mergedvarious patches
- Wrote a "subsystem manager" branch (#28330)
Week of 11/5 (planned:
- Comment on new version of crypto thing /prop295
- Review wtf-pad design and code (waiting on status update for
proposal revisions)
- Meet with B Bhumiratana to chat about net privacy
- Plan and possibly start working on #2149 ("extra dormant")
with dgoulet
- Revise or merge #28226 (messaging system)
- Release 0.3.5.4-alpha?
- Possibly, design for testing sustems that use pub/sub.
Want help with:
Mike:
Week of 10/29 (planned)
- Write more tests for wtf-pad; help asn with review and/or chutney tests
- Write diff for nickm's datagram paper
- Update WTF-PAD proposal
- Maybe help Jaym diagnose why #23512 seems off?
Week of 10/29 (actual)
- Updated WTF-PAD proposal
- Rebased WTF-PAD for nickm
- Wrote more tests for wtf-pad; helped asn/nick/teor with review; fixups
- vanguards fixes and features
week of 11/5 (planned)
- New GPG subkey. Kill me.
- More WTF-pad proposal updates
- Vanguards release?
- WTF-PAD updates, fixups, tests
- Datagram paper diff for nick
help with:
ahf:
Week of 10/29 (hopefully):
Sponsor 8:
- Continue implementation for #28179
- Talk with HC about ARM64 Orbot
Sponsor 19:
- Spend some time (half a day? a morning maybe?) on some
of the Snowflake tasks.
Misc:
- End of month tasks.
Week of 10/29 (actually):
Sponsor 8:
- Continued work on #28179.
- Talk with dgoulet+dcf about #28180 (and some S19 stuff).
Sponsor 19:
- Began looking at our S19 roadmap tickets.
- Looked at the HTTPS Proxy PT for the "Backup PT" roadmap task.
- Looked at Snowflake design.
Misc:
- October Harvest report done.
- Looked a bit at the Graphite data collection code with David.
- Got through my review backlog.
Week of 11/05 (hopefully):
Sponsor 8:
- Finish #28179 and get it reviewed+landed.
- If the above gets done, look into next S8 item(s).
- Look into #27100.
Sponsor 19:
- Continue wrapping my head around PT tasks for s19 (mostly
focusing on Snowflake).
- Help UX with #27385.
- Anti censorship team hire.
- Write email about Snowflake meeting last Tuesday of
november, 23 UTC
Misc:
- Review #28298.
- Do reimbursements from Mexico.
help with:
- Don't think anything right now(?)
asn:
Week of 10/29 (planned):
- Continue reviewing/testing WTF-PAD code.
- Do reviews.
Week of 10/29 (actual):
- Spent most of my time reviewing, refactoring and testing the WTF-PAD code
and proposal.
- Did reviews
- Merged an HSv3 branch in upstream tor!
- Helped with bridgedb funding proposal.
- Helped with a few hsv3 tickets.
Week of 11/05 (planned):
- Continue reviewing, refactoring and testing the WTF-PAD code.
- Try to come up with a useful WTF-PAD state machine that we actually want
to merge.
- Do reviews.
help with:
dgoulet:
Week of 10/29 (planned):
- Get further into #25502 meaning taking care of #28180 and hopefully
starting to implement soon.
- Reviews and 035 tickets as much as possible.
- Draft the stable maintainer policy with teor's help.
Week of 10/29 (actual):
- Discussion with dcf1 and ahf on the spec side of #28181.
- Worked on doc/HACKING/Maintaining.md document.
- Merge a series of HS ticket upstream.
- Discussion about #28275 which in the end turns out to be a bad idea so
we'll take a different route.
- Review and discuss HSv3 tickets.
- Looked at the "subsystem manager" branch from nickm as a first skim. No
comments yet.
- Some side project with ahf on exporting various Tor stats using Graphie
format and Grafana/Prometheus to visualize.
Week of 11/5 (planned):
- Planned, review and/or work on #28335 with nickm.
- Available for ahf to review #28179 and then start working on the code
for #28180 (s8).
- Finalize whatever s8 other tasks come up this week.
gaba:
Week of 10/29 (actual):
- OTF Summit in Taipei
- week 1:1
- fundraising & proposals
- roadmap: I will check on people about sponsor8 tickets
Week of 11/5 (planned):
- gettor follow up
- hackweek cancel KU reservation
- get into ooni work/roadmap
- start looking at CVs that come up for data architect position
for metrics team
- several weekly meetings (ooni, metrics, fundraising, las vegas) and 1:1s
help with:
- communicating anything about sponsor8-bootstrap help/needs and progress
catalyst:
week of 10/29 (2018-W44) (planned):
- reviews
- hiring stuff
- more detailed outline of sponsor8 work
- 0.3.5 bugfixes as needed
week of 10/29 (2018-W44) (actual):
- wrote up outline of new abstractions for bootstrap tracking (#28281)
- cleaned up #28018 children
- started reviewing #28226 (pubsub)
week of 11/05 (2018-W5) (planned):
- reviews
- bug triage rotation
- 0.3.5 bugfixes as needed
help with:
haxxpop:
Week of 10/29 (planned):
- Continue writing the man page
Week of 10/29 (actual):
- End up fixing #28184 instead of writing the tor-keygen man page.
Week of 11/5 (planned):
- Probably discuss about #28275. A lot of ideas are going through. So
fun :). And I will fix it if there is something to be changed.
- Write the tor-keygen man page, if I have time left.
help with:
teor (online!):
Week of 29 Oct (planned):
- Get my timesheets and post-travel admin done (awaiting
advice from accounting)
- Work on PrivCount in Tor prototype
- minor fixes to privcount_shamir
- module design, merge privcount_shamir, stub other modules
- finish off the travis CI config for chutney / turn it into
a config to test PrivCount in Tor
- Make the fallback script ignore addresses in the whitelist,
so we can rebuild the fallback list
- Work on code review backlog. Maybe small revision and small
ticket backlog if I have time
Week of 29 Oct (actual):
- Hackfest, meeting planning, and lots of timesheet and
post-travel admin admin
- Finished all my outstanding code reviews, and did some
re-reviews, and some quick fixes
- Merged some chutney debugging improvements
- Helped nickm with MyFamily RAM usage reduction (#27359)
- Worked with nickm and catalyst on s8 bootstrap
- Worked with Karsten on a metrics bug that we want to avoid
in PrivCount (#28305)
- Fix our Windows version detection (#28096)
- Helped with a ~ path handling bug (#28311)
Week of 5 Nov (planned):
- Pick up a s8 bootstrap ticket, and do it
- Try and make progress on the s8 chutney consensus failure
bugfix tickets
- Work on PrivCount in Tor prototype
- merge the crypto_rand_double() C code in #23061, and write
a Rust equivalent
- minor fixes to privcount_shamir
- finish off the travis CI config for chutney / turn it into
a config to test PrivCount in Tor
- Make the fallback script ignore addresses in the whitelist,
so we can rebuild the fallback list
Week of 5 Nov (actual):
- Started "pick guards from a reasonably live consensus"
(#24661), found #28319
- More admin
- Go through my ticket email backlog, lots of little ticket updates
- Planning for s8-bootstrap
Help with:
- I am stuck on #28096. It's a tinytest fake Windows fork issue.
nickm, can you help?
Details here:
https://trac.torproject.org/projects/tor/ticket/28096#comment:11
Answer: nickm will look at the ticket
- Can I have a second opinion on #26376? I am not sure which
cross-compiling doc we should be merging.
Answer: we will try out the process, and maybe rewrite the
instructions based on what we learn
- When can I stop doing Sponsor 8 and move on to PrivCount and
the fallback directory mirrors? This week?
Answer: Maybe for a day every week for a break
- How do we feel about adding a Windows Server 2016 build to
Appveyor? (#28318)
Answer: Let's try it, and then think about moving to Travis
when it has C support
juga (offline):
Week of 10/29 (planned):
- sbws
- relase 1.0, update deb
- start using sbws in production (#28224)
- tor code
- start with #21377: DirAuths should expose bwauth bandwidth files
- prioritize open tickets
- bandwidth file specification
- whatever needs to get fixed after review
Week of 10/29 (actual):
- sbws
- relased 1.0.0, and 1.0.1, updating debian package to 1.0.1
- bandwidth file specification
- created pull requests with updates
- tor code
- started with #21377: DirAuths should expose bwauth bandwidth files
- some prioritization of open tickets (sbws and tor code)
- looked at bridge bandwidth scanner code
- started using sbws in production (#28224)
Week of 11/05 (plan):
- tor code
- continue with #21377: DirAuths should expose bwauth
bandwidth files
- continue with #22453: Relays should regularly do a
larger bandwidth self-test
- start with #26698: Authorities should put a hash of the
bandwidth file in their votes
- undecided on trying to start some tasks that are not
priority but on which the rest of the work on bandwidth stuff might
depend
More information about the tor-project
mailing list