[tor-project] Network Team Meeting Notes, 7 October 2019

Alexander Færøy ahf at torproject.org
Wed Oct 9 23:55:21 UTC 2019


Hello,

Here is a short summary of the network team meeting from Monday:

1) We started out by looking at the 0.4.2 status page on Trac to see how we are
   doing there. Some tickets were pushed to 0.4.3. We use the keyword `042-deferred`
   for tickets pushed to 0.4.3 in Trac.

2) We went over our kanban board to see if it is up-to-date. A lot of people
   are back to working on sponsored items as well as 0.4.2 items.

3) We went over the reviewer assignments by David and George. Everyone should
   have gotten around 1.2 reviews each this week. #31943 got priority as it is
   part of our GSoD project.

4) Alex asked for people to comment on a pad such that we can begin doing
   monthly network team reporting to tor-project at lists.torproject.org

5) A question was asked on how to handle the S27 ticket #14389 for 0.4.3
   inclusion and the answer was that it was going to be discussed at the S27
   meeting Tuesday this week.

6) No new policies to discuss this week. The other policies continues to be
   discussed on the internal network team mailing list.

7) Nobody had anything additional to discuss.

--- end of summary ---

You can read today's network team meeting log at:

http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-07-16.59.html

Below are the contents of our meeting pad:

gaba: (updated on september 30th)
    Last week (actual):
    . s30
    . s31
    . 1:1:1s
    . get up to date with trac tickets

    This week (planned):
    . s30 coordination with all teams involved
    . roadmap update (bring october tickets)
    Help with:

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

    Week of 23 September (planned):
        Take Time for:
            - gitlab signup / config
            - team policies:
                - faster reviews
                - commit bit and roles?
            - 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
        Roadmap:
            - Sponsor 31 outstanding bugs / tasks
            - Sponsor 31 possible coding tasks for me - follow up email
        Other:
            - finish off bug smash logging bugs

    Week of 23 September (actual):
        Take Time for:
            - gitlab signup / config
            - team policies:
                - faster reviews
                - commit bit and roles
            - kept working on add tor controller trace logging to diagnose stem hangs (#30901)
                - split off bugs I found while writing the control trace code
                - did some preparation work
        Roadmap:
            - Sponsor 27
              - Add IPv6 HSv3 chutney tests to CI
            - Sponsor 31 reviews
            - Sponsor 31 modularisation: disable relay mode when compiling
              - Initial design and strategy to move forward
              - Preparation work - speed up CI
        Other:
            - Finish off bug smash logging bugs
            - Quick bug fixes x3

    Week of 30 September (planned):
        Take Time for:
            - team policy discussions
            - meetings x3
        Roadmap:
            - add tor controller trace logging to diagnose stem hangs (#30901)
                - try nickm's suggested a simpler implementation
            - Sponsor 31 modularisation: disable relay mode when compiling
              - First cut: disable DirCache, DirPort, ORPort, and sets --disable-module-dirauth
            - If I stall on coding, finish sponsor 31 documentation that's assigned to me
        Other:
            - Reviews and revisions
            - Check CI & backports

    Week of 30 September (actual):
        Urgent:
            - 
        Take Time for:
            - team policy discussions
            - meetings x3
        Roadmap:
            - Sponsor 31 config refactor
              - control trace logging #30901
              - preparation work - fix conflicting bugs
              - started work
            - Sponsor 31 modularisation: disable relay mode when compiling #31851
              - Initial design and strategy to move forward
              - Preparation work - speed up CI
        Other:
            - Revisions
            - Check CI & backports
            - Quick bug fixes x2
            - tor-relays moderation

Nick:
    Week of 30 September (planned):
        - One more PETS review.
        - Work on 042-must/should items
        - Start on another alpha, if all the -must items are done?
        - Kick off a C style poll
        - More review and feedback on pending refactoring
        - Review and merge stuff
        - Finish circuit-padding editing
    Week of 30 September (actual):
        - More editing on circuitpadding docs
        - another PETS review
        - Resolve a coverity issue (31948)
        - Mock DNS resolution to avoid slowdown in addr/parse (31841)
        - Review and merge
        - Work on draft C style poll more
        - Prepare an 0.4.2.2-alpha release
        - 042-must items:
            - 31796 practracker warning (investigated, no fix needed)
            - 31611 investigate causes of 31495.
            - 31634 investigate module topology vs initialization order
            - 31898 crash on shutdown with tor-api
        - Retrospective
        - Proposal for revised merge policy
    Week of 7 October (planned):
        - Actual 0.4.2.2-alpha release
        - Start a maint-042 branch, open master as 043
        - remaining 042-must/should issues
        - keep an eye on blog comments
        - Review and merge
        - tor-guts documentation work
        - Work on a blog post about an upcoming paper.
        - Back to 29211 (config refactoring)?

Mike:
    Week of 10/02 (planned):
        - Finish Firefox networking review
        - Check in with Tobias re circpad perf issues and simulator plan
        - Perhaps update circpad doc with perf notes
    Week of 10/02 (actual):
        - Firefox networking review ~80% done?
        - Minor circpad dev doc updates
        - Assited w/ our Mozilla all hands session proposals
    Week of 10/07 (planned):
        - Finish Firefox networking review
        - Do some of Firefox Feature Review
        - Check in with Tobias re circpad perf issues and simulator plan
        - Blog post writing?
    Need help with/at risk of dropping this month: <-- do you still need help with this?
        - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser
        - Deep-thought-required research project followup 
          - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...)
        - Relay community drive/mgmt (and related LTS herding)

catalyst:
    week of 09/30 (2019-W40) (planned):
        - reviews
        - #30984
        - review policy proposals
    week of 09/30 (2019-W40) (actual):
        - reviews
        - more feedback about C style
        - many meetings
    week of 10/07 (2019-W41) (planned):
        - reviews
        - look at policy proposals some more
        - be available for GSOD help as needed

asn:
   Week of 02/10 (planned):
   - Bring OB hsv3 descriptor encoding closer to completion.
   - Attend s27 meeting about error passing over SOCKS vs HTTP vs control port
   - Handle remaining 042 bugfixes.
   Week of 02/10 (actual):
   - Working on hsv3 descriptor encoding (#31823)
     - Can now do blinding #31777 (also ported the tor ed25519 to python3 on the way #31912)
     - Can now do descriptor layer encryption
     - Can do the superencrypted layer
   - Stem hsv3 descriptor decoding is merged upstream (#31369)!
     - Reviewing and testing
   - Did 042 tickets assigned to me. Also reviews and merges.
   Week of 07/10 (planned):
   - Bring the hsv3 descriptor encoding branch to some browseable state so that
     I can show atagar before I leave for vacations on Friday.
   - Attend the s27 meeting about error passing which did not happen last week.
   - Check updates on #19251
   - Finalize anything else remaining before I sign off for two weeks on Friday.

ahf:
    Week of 30. September (planned):
    - Finish 0.4.2 tickets
    - Get back to S29 tickets
    - Work on migration scripts for Gitlab transition.
    - Take the good parts of our PR policy discussion and turn into a
      policy.
    - Network team retrospective.

    Week of 30. September (actually):
    - Quite a few meetings.
    - Did network team retrospective.
    - Continued work on Gitlab transition with anarcat's ticket migration idea.
    - Hacked on #31810 and #31091 (042-must)
    - Looked into 2 GB log issue on Windows (#31036)
    - Community Council meeting.

    Week of 7. October (planned):
    - S30 meeting.
    - Plan Zurich trip.
    - Get #31810 and #31091 merged.
    - Finish #31036
    - Do full migration of Trac tickets to Gitlab as an experiment.
    - S31 meeting.
    - PR policy.

dgoulet:
  Week of 02/10 (planned):
    - Go through my 042 tickets.
    - Assess s27 situation and timeline and prioritize work that need to
      happen soon.
    - Attend s27 meeting about the SOCKS error situation.
    - Bad relay world.
  Week of 02/10 (actual):
    - Network Team retrospective.
    - Went through some 042 tickets. Most were in needs_revision.
    - s27 work was bit on hold due to 042 ticket work and other work.
    - Spent time working the details and logistics for the removal of all EOL
      relays in the network (including blog post, and a whole LOT of emails).
  Week of 07/10 (planned):
    - Finish this EOL removal scheduled on Tuesday.
    - Revise my 4 remaining tickets in 042.
    - Merges/Reviews.
    - s27 meeting on October 8th about prop304 mostly.


swati (offline):
     Week of 02/10:
         - Registered and created an account for myself on trac.
         - Created a ticket https://trac.torproject.org/projects/tor/ticket/31943 for reviewing changes in the tor Manual.
         - Forked the tor repository and cloned the copy of the repository to my local filesystem
         - Pushed changes to the local repository and created a pull request.
         - The pull request is https://github.com/torproject/tor/pull/1391. 
         - Can someone assign reviewers for this pull request? I don't seem to have write access for this repository.
             [dgoulet: for #31943, we did this morning :)]

All the best,
Alex.

-- 
Alexander Færøy


More information about the tor-project mailing list