Hello!

You can read the logs from yesterday's meeting at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-06-24-17.00.html

Below are the contents of our meeting pad.

= Network team meeting pad! =

This week's team meeting is at Monday 24 June at 1700 UTC on #tor-meeting on OFTC.

June schedule: * Monday 24 June at 1700 UTC

July schedule: * Wednesday 3 July 2300 UTC * 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 https://lists.torproject.org/pipermail/tor-project/2017-September/001459.htm... 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.) 28 May: https://lists.torproject.org/pipermail/tor-project/2019-May/002338.html 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

== Stuff to do every week =

* How are we managing CI failures from last week? See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CIFailur...

* Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... (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: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1vN... 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 https://trac.torproject.org/projects/tor/query?status=needs_review&compo...

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.

------------------------------- ---- 24 June 2019 -------------------------------

== Announcements ==

[REMINDER] WIP Schedule for Tor meeting https://nc.riseup.net/s/FFkikRBmKDZyLw9

The master branch is now 0.4.2.x. 0.4.1.x development continues on maint-0.4.1 and release-0.4.1.

0.3.4.x is now end-of-life.

Summary the mail thread on proposal from Dgoulet https://nc.riseup.net/s/gQGT8kjNgt3C6cd

== Discussion ==

Retrospective on Thursday. How people want to do the retrospective? (please vote)

jitsi +1 +1

irc

other?

#29697 Anybody up to team with boklm to coordinate archive.tpo

Please update https://pad.riseup.net/p/network-team-draft-CI-role and vote yes/no on the change into a permanent role for CI. Can we start soon?

Rotation updates:

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

CI/coverity

ahf -> catalyst

coverity

(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

jenkins

Travis

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

Appveyor

Bug triage

teor -> ahf

Everything seems ok, I might have missed some patches and things earlier in the week.

== Recommended links ==

== 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! Leave the parts for last week and this week!

gaba:

Last week (actual):

. gitlab

This week (planned):

. sponsor 31 adjustment with new tickets

. more gitlab

Help with:

teor: (offline at the usual meeting time)

Week of 17 June (planned): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fix existing open tickets where I have added the sponsor - Fallback directory mirror list rebuild (#28793) - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - merge chutney pull requests - disown or quick fix tickets: I should only be owner on tickets I will work on in the next month - bug triage rotation Important: - 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 Low-Priority: - backlog: router_have_consensus_path() logs an incorrect "no exits in consensus" (#27448) - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month?

Week of 17 June (actual): Urgent: - triage 0.4.0 backport backlog by Wednesday, so we can decide whether to do an 0.4.0.6 - after 0.4.0.6, I will be maintaining 0.4.0. - More HR stuff - use sponsor-NN-maybe and cc Gaba rather than setting the sponsor on tickets - fixed some existing open tickets where I have added the sponsor - some code reviews - merged some chutney pull requests - Fallback directory mirror list rebuild (#28793) - draft list - need to work out why the list is so short this time (#30952) - some bug triage - sbws triage and fixes - Fixed PT extra-info bugs introduced in 0.4.1.1-alpha and 0.2.7.2-alpha (#30956, #30958) - disowned some tickets, more next week Important: - reviews of new onion service DoS code - designed API for pool abstraction - work on proposal/questions for possible trac migration - travel prep - process changes

Week of 24 June (planned): Urgent: - fix existing open tickets where I have added the sponsor - Continue fallback directory mirror list rebuild (#28793) - need to work out why the list is so short this time (#30952) - 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 - Update wiki and send email about first meeting of month changing to Wednesday 2300 UTC - maybe do this on Tuesday in the last week of the month? Important: - 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 24 June (actual): Urgent: - Important: - Low Priority: -

Help needed: - catalyst, do you have advice on: - add tor controller trace logging to diagnose stem hangs (#30901) [catalyst: i'll try to look at it this week]

Nick: Week of 17 June (planned): - Summarize employee feedback - PETS review - 0.4.0.6 release, maybe. - Reply to proposals 303 through 305, maybe. - Reviews and merges - 29211 -- refactor configuration code. - 29280 -- needs_revision, chutney in ci code - 27801 -- review proposed API for launching sockets with embedded tor - 29817 -- try to re-load seccomp into my brain and resuscitate this ticket. Week of 17 June (actual): - Code reviews - PETS review - Work on various 29211 subtickets. (configuration refactoring) - Start summarizing employee feedback. (4/6 done) - Defer 0406 release; start 0413 release - try to catch up with backlog Week of 24 June (planned): - Retrospective on Thursday - More 29211 work - 0413 release - attempt: Reply to proposals 303 through 305, maybe. - attempt: review 27801 api - attempt: 29817 -- try to re-load seccomp into my brain and resuscitate this ticket.

Mike: Week of 6/17 (planned): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/17 (actual): - Mozilla all hands performance and scalability meetings + discussion - Performance metrics finalization Week of 6/24 (planned): - Bitcoin conference - code reviews - Catch up on mail

catalyst:

week of 06/17 (2019-W25) (planned): - reviews - control.c refactoring week of 06/17 (2019-W25) (actual): - chatted with ahf re #28930 (msybe reorder some PT/proxy bootstrap phases) - bureaucracy - wrote up #30911 to document some inbound email problems - cleaned up my owned tickets a little week of 06/24 (2019-W26) (planned): - CI+Coverity rotation - reviews - take a closer look at dgoulet's "radical changes" email thread - help teor with #30901 (control port trace logging for debugging test-stem hangs) - more bureaucracy - starting Stockholm trip prep - hopefully have time to work on control.c refactor

asn: Week of 06/03 (planned): - Finalize s27 o2a1. - Help organize our AllHands experience. - Fix #30578 circpadding bug (041-must). - Do more work on HS DoS. - Some more travel prep for allhands. Week of 06/03 (actual): - Finally managed to get #30381 in needs_review. - Wrote some scaling emails. - Worked on #30578 (041-must). - Did some work on HS DoS: https://lists.torproject.org/pipermail/tor-dev/2019-June/013873.html - Cleaned most of my review backlog, but there is still more. - Merged prop304 to torpec. Week of 06/10 (planned): - #30381 is now in needs_revision. Need to do that. - More prepping for AllHands. Flying out on Sunday. - Try to do some work on s27 #26294 (intro point rotation dos) - Still got reviews hanging. In particular #30382. - I also got lots of hanging merges... Help needed: - teor, I still have troubles mapping all the pieces of #22029 in my brain. Perhaps at some point you can take over the review of that ticket, and I can take one big review from you? I don't see you having any big reviews this week, so perhaps we can wait until next week. teor says: I assigned myself as reviewer on this ticket. neel is still working on it, when he finishes, I will split off some of the small features so other people can review them.

ahf Week of 17/6 (planned): Network team: - Finish off patches for #29736 so we can discuss the big changes at the Thursday meeting. - Continue with #28930. Misc: - Figure out what needs to be doing on some of the PT spec tickets I have. Week of 17/6 (actually): Network team: - Discussed #29736 and authentication patches during anti-censorship team meeting. - Rebased and discussed current changes for #28930 with catalyst and decided next step. - Wrote patches for CI build failures for Stem and Chutney in #30928. - Figured out next steps for #5304 Week of 24/6 (planned): Network team: - Continue iteration of #28930 and discuss progress with catalyst. - Write Tor patch for #5304 (spec is OK) - Bug Triage duty. - Work a little bit on 'untrac' (a small tool to import Trac tickets into Gitlab that Gaba and I talked about during my 1:1 last Friday).

juga(offline): Week of 05/20 (planned) - Add Tor version to the bandwidth file (#30196) Week of 05/20 (actual) Week of 06/03 (plan) - Continue with #30406: Refactor header constants in sbws to use Stem's one

dgoulet: (might be offline, getting sleep has been very rough in the last days...) Week of 06/10 (actual): - Tested and experimented with #15516. Had to wait a bit to get new machines from a friend at a hosting provider in order to start limited bw relays. Thanks to ahf for providing assistance with his fast relays. - Wrote prop305 (on tor-dev@) about ESTABLISH_INTRO parameters. See #30790. Thanks from teor/asn for early feedbacks! - Merges and reviews as always. Week of 06/17 (planned): - Finalize #30382 from asn's review. - Continue work on #15516. I'm hoping to drop the experimental results on the ticket, finzlie the branch for upstream merge. And then move on to prop305.