[tor-project] Network team meeting notes, 19 August 2019

Nick Mathewson nickm at torproject.org
Mon Aug 19 18:27:34 UTC 2019


You can find the contents of our latest meeting logs here:


Below are the contents of our meeting pad:

= Network team meeting pad! =

This week's team meeting is at Monday 19 August 1700 UTC on
#tor-meeting on OFTC.
We have changed the day from Tuesday to Wednesday.

August schedule:
    * Monday 12 August 1700 UTC
    * Monday 19 August 1700 UTC
    * Monday 26 August 1700 UTC

Welcome to our meeting!
First meeting each month: Wednesday at 2300 UTC
Other meetings each month: Mondays at 1700 UTC until 3 November 2019,
when daylight saving time changes
On #tor-meeting on OFTC.

(This channel is logged while meetings are in progress.) (See
for background.)

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!

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 tor-project mailing list archive for older notes.)
In-person meetings:
22 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002401.html
29 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002408.html
7 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002418.html
12 August: https://lists.torproject.org/pipermail/tor-project/2019-August/002431.html

== Stuff to do every week =

* Let's check the 0.4.1 release status page.
  See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases/041Status
  (This page automatically shows the latest trac ticket status.)

* Let's check and update the roadmap.
  What's done, and what's coming up?
  We're using a kanban board:

* Check reviewer assignments! How reviews from last week worked? Any blocker?

Here are the outstanding reviews, oldest first, including sbws

== 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 the 'actual point' field when you close a
ticket. We need those to calculate velocity.

* Check other's people call for help in their entries.

* When you are overloaded, it is ok to say "no" to things.
    * And it is ok to reschedule things.

---- 12 August 2019

== Announcements ==


reminder: catalyst will be AFK Jul 29 through Aug 18

ahf will be AFK all of August for BornHack and CCC Camp, but will be
on IRC every now and then

On September there is a technical writer from Google Season of Docs
starting to work with us on rewriting the Tor manual page. She will be
participating in the network team meetings. Her project:

We are moving the kanban board from storm into
https://dip.torproject.org/torproject/core/tor/boards . This will help
lead a plan for migration into dip.torproject.org.

The release date for 0.4.1.x-stable is postponed to 20 August, so that
it will come out _after_ Nick is back from vacation.  Please get all
041 blockers fixed and merged if possible?

== Discussion ==


When should we do the next 0.2.9 - 0.4.0 releases?
Should we do a new release after updating dizum's IP address? (#31406)

armadev says:
    usually we wait for a particularly compelling security or compatibility fix
    please, consider users in your choice. that is, making people
upgrade their stable when they don't 'need' to will make them less
inclined to do it when they do need to.
    i think doing it just for a new dizum ip address is borderline.
since the old address will work for a long while yet (years, was
alex's estimate)
    there is also something to be said for "a sufficient threshold of
items which by themselves wouldn't be enough"
    but i would err on the side of being conservative, in the same way
we should err on the side of being conservative of what needs a
    and they are tied together, since if you don't backport much, you
don't need to release much, and if you don't release much, you tend to
not want to backport as much

Here is a draft policy for deciding which tickets need backports:
Here is a draft policy for deciding when to do a backport release:
    Summary: as needed, when there is an important, user-visible change


Sebastian wants to do a Rust refactor that raises the minimum required
rustc to 1.32.
Is that ok?


Are we all okay with with releasing as stable?  If not, please
let nickm know before 1200 UTC on Tuesday.

== Recommended links ==

== Updates ==

    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.


Leave the "Planned" parts!
Leave the parts for last week and this week!


Last week (actual):

. catching up

. s30

. roadmap

This week (planned):

. s28

Help with:

teor: (online first week of the month, offline at the usual meeting time)

    Week of 12 August (planned):
            - config.c refactor code review (#30914), because we want
to get it done by the end of August
            - finish add tor controller trace logging to diagnose stem
hangs (#30901)
                - try nickm's suggested a simpler implementation
                - split off bugs I found while writing the control trace code
            - finish small 0.4.1 tasks
            - code reviews

    Week of 12 August (actual):
            - 2 days off sick

            - finished a few reviews, some still to go
            - ticket triage
            - cleared backport merge backlog
            - Tried to help get Rust working on BSD (#31390)
            - IPv6 funding proposal - extra objectives as people bring them up
            - update draft backport and release policies - maybe I
should turn these into proposals?
            - helped anti-censorship team find the tor function that
provides complete bridge PT lines (#29128)

    Week of 19 August (planned):
            - config.c refactor code review (#30914), because we want
to get it done by the end of August
            - finish add tor controller trace logging to diagnose stem
hangs (#30901)
                - try nickm's suggested a simpler implementation
                - split off bugs I found while writing the control trace code
            - finish small 0.4.1 tasks
            - finish remaining code reviews, except for neel's big PR
that I will split up

    Week of 19 August (actual):
            - finished some code reviews
            - worked on #21003 so I could see the IPv6 addresses in
logs to review #31088

    Week of 12 august (planned):
        - ON VACATION
    Week of 12 August (actual):
        - ON VACATION
        - Poked at #29211 a little on long car rides when not driving
        - Read a little bit about lektor
        - Read some Rust code.
    Week of 19 August (planned):
        - Release (stable)
        - More 29211 (configuration refactor) work. Hoping to reach
the point where 1 module is module-wise configured
        - Review and merge
        - Revise old branches after they're reviewed.
        - Finish and submit walking onions paper.

Mike (may have to leave early):
    Week of 8/7 (planned):
        - Fix https://trac.torproject.org/projects/tor/ticket/30992 and/or
        - Clean up #30942
        - Catch up on researcher and scalability related mail
    Week of 8/7 (actual):
        - Fix https://trac.torproject.org/projects/tor/ticket/31343
    week of 8/12 (planned):

    Need help with/at risk of dropping this month:
        - Deep-thought-required research project followup (masque,
BGP, ECN, etc)
        - Private browsing meetings
        - Relay community drive/mgmt (and related LTS herding)
        - Circpad documentation + Sponsor 2 report
        - Firefox ESR network code review
        - Code reviews?


    week of 08/19 (2019-W34) (planned):
        - catching up after leave
        - skimming IRC highlights; please email me if you think i've
missed something important
        - reorient on current CI status

   Week of 12/08 (planned):
   - More onionbalance v3
   - Work on WTF-PAD #30992
   - Do reviews/merges.
   Week of 12/08 (actual):
   - Revised my #30381 branch.
   - Wrote a spec patch for #26294 and #31392.
   - Reviewed the DoS ticket #30924 as part of s27
   - Reviewed #31356, #31375, #29879, #31353, #31352, #31175.
   - Talked with Damian about onionbalance v3 and opened #31369 for v3 desc
     support in stem.
   - Did merges.
   Week of 19/08 (planned):
   - Read [tor-dev] [prop305] Introduction Point Behavior
   - Check open hackerone issue.
   - Finish up with reviews and merges before CCC camp.
   - Attend CCC camp and participate in the talk.
   - Speak with the onionbalance maintainer during camp to make plans for v3

ahf: - on leave
    Week of 22/7 (planned):
        - Do reimbursement
        - Go over all notes from Stockholm that seems relevant to me.
        - Follow up on pre-Stockholm items:
            - Continue figuring out some info on a potential Danish funder.
            - Continue with #5304 and #28930
    Week of 22/7 (actually):
        - Did reimbursement
        - Went over all notes from Stockholm.
        - Followed up on pre-Stockholm items:
            - Continue figuring out some info on a potential Danish
funder (postponed until they are back from vacation).
            - Continued work with #5304 and #28930
    Week of 29/7 (planned):
        - Finish off #5304 and #28930 before going on vacation.
        - Review Roger's DEFCON slides.
        - Do you need any help from me before I leave?

  Week of 12/08 (actual):
    - prop305 #30924 finalized and tested. Got a first round of review with
      asn also.
    - A little bit of tor-scaling work continuing my cell tracing timings +
      EWMA adjustments work.
    - Worked with dizum (Alex) to change IP: #31406
    - Wrote "[tor-dev] [prop305] Introduction Point Behavior" per
discussion with
      asn on IRC. Part of #30924.
  Week of 19/08 (planned):
    - Get #30924 revised from asn's review and into merge_ready state.
    - Start on the HS timeout issues (#30200 + #28841).

More information about the tor-project mailing list