[tor-project] Network team meeting notes, 22 July 2019

Nick Mathewson nickm at torproject.org
Mon Jul 22 17:28:48 UTC 2019


The IRC logs from our weekly meeting are available at

Below are the contents of our pad.

= Network team meeting pad! =

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

July schedule:
    * Wednesday 3 July 2300 UTC - Changed Day!
    * Monday 8 July at 1700 UTC
    * (In-person meeting 12-14 July)
    * Monday 22 July 1700 UTC
    * Monday 29 July 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 list archive for older notes.)
3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html
10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html
17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html
24 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002373.html
3 July:  https://lists.torproject.org/pipermail/tor-project/2019-July/002389.html
8 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002390.html
In-person meetings:

== 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:
      Click on 'all boards' and then the network team one. Filter by
your name and check the 'in progress' column is correct.

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

Here are the outstanding reviews, oldest first, including sbws

Any blocker from last week?

== 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.

---- 22 July 2019

== Announcements ==

reminder: catalyst will be AFK Jul 29 through Aug 18
nickm will be AFK August 12 through August 16
ahf will be AFK all of August for BornHack and CCC Camp, but will be
on IRC every now and then

== Discussion ==

Rotation updates:

See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRotations


catalyst -> catalyst & teor


the defect browser was down last week; it seems to be back now

(Waiting on update after merging coverity fixes: Coverity does not
seem to have noticed 30150 yet.)

Looking at coverity -- it seems our builds may have been stuck. I've
cancelled the stuck builds. Also, they say they are going to have a
planned outage to upgrade their backend, starting today and lasting
about 3-4 days.  Friday would be a good day to have another look. -nm

stuff got unstuck on 28 Jun or maybe earlier? -catalyst

Correct; we've been getting updates since then.  I opened tickets for
the first day's updates; there are more I hope to get to soon.


some intermittent failures that could be network-related


teor did some work on stem failures, we need to add a control message
trace to tor to diagnose (#30901)

waiting for catalyst's advice, because they are refactoring this code


Bug triage

ahf -> asn

Things are looking OK asfaik.

catalyst asks if we want to re-evaluate
https://trac.torproject.org/projects/tor/ticket/31081 or stay with
"make the spec match the code"

Please give feedback on proposal 306: IPv6 "Happy Eyeballs" for Tor clients

== 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):

This week (planned):

. tor meetup

Help with:

teor: (offline at the usual meeting time)

    Week of 8 July (actual):
            - Taking time off before long-haul travel and Stockholm meeting
            - Travel preparation
            - Ticket triage
            - Proposal responses
            - code reviews
            - add tor controller trace logging to diagnose stem hangs (#30901)
            - disown or quick fix the rest of my tickets:
                - I should only be owner on tickets I will work on in
the next month
            - fix sponsor on tickets?
            - CI for pluggable transports (#29267) <-- this is
priority over #29224 and 29227 in the roadmap --gaba
            - Update EndOfLifeTor.md with our latest end of life
process (#30839)
            - document disabled CI (#30745)
            - triage remaining backport backlog

    Week of 15 July (actual):
        - Attend PETS reception
        - Take it easy post-meeting
        - Travel home
        - More work on refactorings for 29211 (config.c redesign)
        - Several practracker improvements
        - Catch up on email and expenses
    Week of 22 July (planned):
        - Review and merge
        - Try to release
        - Backports for 0.4.0.x?
        - More 29211 work (config.c): can I get all the backend code written?
        - Reply wrt proposal 295
        - Reply wrt proposal 306
        - More practracker fixes, time permitting

Mike (afk: jetlagged and recovering from 12 days travel+work)


    week of 07/08 (2019-W28) (planned):
        - travel prep
        - Stockholm meeting
    week of 07/08 (2019-W28) (actual):
        - travel prep
        - Stockholm meeting
    week of 07/15 (2019-W29) (actual):
        - travel
        - time off to recover from travel
    week of 07/22 (2019-W30) (planned):
        - Season of Docs selection due 07/23
        - expense reports
        - follow up from Stockholm meeting
        - hand off some reviews to teor
        - working partial days this week

   Week of 07/01 (actual):
   - Pushed #26294 branch to needs_review.
   - Some more thoughts on the DoS thread.
   - Some more thoughts on scaling thread.
   - Lots of hackerone activity/triaging/rewarding (#31022, #31001,
plus one more not yet filed)
   - Finished review/merge backlog.
   Week of 07/08 (planned):
   - Triaged a few wtf-pad related tickets but need more work: #30649, #31098.
   - Tor meeting in Stockholm.
   - Allhands expenses

    Last N-weeks:
        - Send vacation info to the network team ML.
        - Traveled to Stockholm, had a good time with you all.
    Week of 22/7:
        - 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

dgoulet: (offline)
  Week of 07/01 (actual):
    - s27 DoS work: #15516, #24963/#24964
    - Tor-dev update on the DoS experimentation:
  Week of 07/08 (planned):
    - Stocklholm.
    - Need to address urgently a series of pending bad-relays email.

More information about the tor-project mailing list