Hi!
A reminder: The next network team meeting is at 2300 UTC on Tuesday 2 April.
Daylight saving changed recently, so these meetings might be at a different local time for you.
Here is our full April schedule: * Tuesday 2 April at 2300 UTC * Monday 8 April at 1700 UTC * Monday 15 April at 1700 UTC * Tuesday 23 April at 1700 UTC (Monday 22 April is the Easter Monday public holiday) * Monday 29 April at 1700 UTC
Our logs are at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-03-25-17.00.html
Our meeting notes are below: =======
This week's team meeting is at Monday 25 March at 1700 UTC on #tor-meeting on OFTC.
Welcome to our meeting! First meeting each month: Tuesday 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.
March schedule: * Tuesday 5 March at 2300 UTC * Monday 11 March at 1700 UTC * Monday 18 March at 1700 UTC * Monday 25 March at 1700 UTC
April schedule: * Tuesday 2 April at 2300 UTC * Monday 8 April at 1700 UTC * Monday 15 April at 1700 UTC * Tuesday 23 April at 1700 UTC (Monday 22 April is the Easter Monday public holiday) * Monday 29 April at 1700 UTC * teor will be on leave at the end of April
(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.) 25 Feb: https://lists.torproject.org/pipermail/tor-project/2019-March/002236.html 5 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002244.html 11 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002252.html 18 Mar: https://lists.torproject.org/pipermail/tor-project/2019-March/002263.html
== Stuff to do every week =
* Let's check the 0.4.0 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... <-- filter by your name and check the 'in progress' column is correct.
* Check reviewer assignments!
Here are the needs-review tickets, by reviewer: https://trac.torproject.org/projects/tor/query?status=needs_review&revie...
Here are the outstanding reviews, oldest first: https://trac.torproject.org/projects/tor/query?status=needs_review&compo...
Including sbws: https://trac.torproject.org/projects/tor/query?status=needs_review&compo...
* 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/TeamRota... Core Tor/sbws is now part of the bug triage, CI, and reviewer assignment roles
== 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.
* Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbdG...
* Check other's people call for help in their entries.
------------------------------- ---- 25 March 2019 -------------------------------
== Announcements ==
- The master branch is now 0.4.1.x; 0.4.0 development will continue in maint-0.4.0.
- US DST began a few weeks ago; let's be careful with schedules
We need to prioritize sbws's reviews this month as Juga is wrapping up their work in March. Then we need to prioritize 0.4.0 fixes and reviews in March and April, because stable is due on 15 April.
- Note different meeting time (Tues 2300 UTC) next week
== Discussion ==
dgoulet is away, who can do the CI rotation this week? (nickm will pick it up) Should we remove dgoulet from the next set of rotations?
There are now 7 bugs tagged 040-must, some of them are in progress. Last week, there were 13. (We started the week with 10, and discovered 3 more.) Who needs help with their 0.4.0 bug fixes?
== Recommended links ==
On gitlab time-based releases, and why developers and users like them: https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release-...
== 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: • Week of 03/04 (actual): • - processes https://gitlab.com/gabelula/tor-documentation-processes • Week of 03/11 (planned): • - tor scaling meeting • - roadmap checking before leaving • - traveling on the 14th
teor: (offline except for the first meeting each month)
• Week of 18 Mar (planned): • Roadmap Coding (3 days per week): • - CI with Chutney/Tor: #29729, #29761 • - Backport fixes needed for CI with Chutney/Tor to Tor 0.2.9 • - Bandwidth stats for PrivCount: #29019, #17036, #29005 • - Rearrange the commits in a nice order on a bunch of new branches • Roadmap Reviews: • - Review nickm's parts of the CI with Chutney/Tor tickets • - sbws reviews • Other: • - Other assigned reviews • - Do mainline merges, and the remaining backport merges from last week • - Do remaining reviews from last week • - Leave admin • - Add a travis test for stem (it's a copy of the chutney test, but using the stem command)
• Week of 18 Mar (actual): • Roadmap Coding (3 days per week): • - CI with Chutney/Tor: #22132, #28203, #29703, #29729 and children if needed • Roadmap Reviews: • - test proposed sbws design, suggest a new design, do sbws reviews, found some sbws bugs • Other: • - review and design work on prop#199 and sbws • - tried to make CI fail on undefined behaviour: #29528 and children • - review #29036, #29434, #29073, #29537, and more! • - tried to explain #29500 better • - Leave admin • - Work out how Tor's new feedback process works • - Work out the new travel rules • - review and merge mainline, torspec, and chutney; triage and merge backports • - assigned 040-must tickets to people, and created an 040 status page: • https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... • - did 040 bugfixes
• Week of 25 Mar (planned): • Roadmap Coding: • - CI with Chutney/Tor: #29729, #20473 • - Backport merge fixes needed for CI with Chutney/Tor to Tor 0.2.9 • - Bandwidth stats for PrivCount: #29019, #17036, #29005 • - Rearrange the commits in a nice order on a bunch of new branches • Roadmap Reviews: • - Review nickm's parts of the CI with Chutney/Tor tickets: #29280 • - sbws reviews • Other: • - Hack out quick fixes to #29500 and #29437 • - Assigned reviews • - Do mainline merges and backport merges • - Do remaining reviews from last week • - Add a travis test for stem (it's a copy of the chutney test, but using the stem command)
• Week of 25 Mar (actual): • Roadmap Coding: • - CI with Chutney/Tor: #29729 • Roadmap Reviews: • - sbws reviews, revisions, design work, and backports • Other: • - Assigned reviews • - Do lots of mainline merges and backport merges • - Do remaining reviews from last week • - Tried to get clang to actually fail on UBSan errors • - HR admin / peer feedback requests
• Help with: • - I think #29528 should fail on 0.4.0 with the divide-by-zero undefined behaviour warnings. • But it passes. Does anyone know why? • teor says: we pass the right options to the compiler, but then it disables the UBSan warnings????
• Blocked: • I can't work out how to use practracker, so I can't do some merges • - #29884 Document how to edit practracker exception files
• Dev work and merges are slow due to frequent CI failures: • - #29500 (circuit padding time) • #29437 (test-stem) • So I'm going to hack out quick fixes to these issues this week.
• I haven't been doing 3 days of roadmap coding per week. • I will have more time after sbws and 0.4.0 bugs are over.
Nick: • Week of 25 March (planned): • - 040-must items • - Time permitting, adl/rup revisions • - CI/pubsub hacking as needed • - split control.c into smaller pieces • - extra meetings • - 29223 standardized abbrevs • - Lots of review and merge.
• Week of 25 March (actual): • - 040-must items: • - NSS issue #29241 -- tricky debugging, not-so-tricky fix. (It was only affected TLS1.2 + SHA384.) • - Libseccomp issue #29819 -- helped debug; it seems to be an upstream bug. • - Got pubsub branch merged • - split control.c into smaller pieces (#29894) • - Lots of extra meetings • - Lots of review and merge. • - PETS review. • - Helped review a proposal for a funder. • - Prepared for presentation on this saturday. • - Onion services kickoff meeting • - 29884, practracker enhancements • - misc coverity fixes
• Week of 1 April (planned): • - Try to fix remaining 040-must issue: • - Reopened Can't parse networkstatus consensus time (#28614) • - 040 release? • - Lots of review and merge • - Control.c refactoring: try to better unify command-parsing logic • - Prepare for presentation at Tufts on Saturday • - Write a couple of users for publish/subscribe logic
dgoulet (missing meeting): - AFK.
Mike: Week of 3/18 (planned) - Scalability planning & discussion - Catch up with asn's wtf-pad work, finalize plan for keeping circuits open (#28780) - Taking friday off Week of 3/18 (actual): - Lots of Tor scalability discussion & thought - Continued testing vanguard fixes Week of 3/25 (planned): - Scalability planning & discussion - Client side vanguards issues - Plan lots of travel - Finalize plan for keeping circuits open (#28780) - #29034 patch - Catch up on code reviews
catalyst:
week of 03/18 (2019-W12) (planned): - try prototyping #28925 solution using pubsub but in a way not too difficult to back port to 0.4.0 - CI+Coverity rotation - reviews - checking for any remaining loose ends in pubsub review week of 03/18 (2019-W12) (actual): - reviews - chatted with asn and Riastradh about the prob_distr.c Coverity defects (#29805) and possible ways to resolve them - #28925 patch for 0.4.0 that wasn't too invasive (not using pubsub) - #29789 patch for practracker.py UTF-8 issues - CI+Coverity rotation -- opened tickets for a few new Coverity defects; no significant CI issues - chatted with nickm about ideas for splitting up control.c - resolved some comments on pubsub after reviewing new changes week of 03/25 (2019-W13) (planned): - reviews - work with nickm some on splitting up control.c
juga:
Week 18 March (planned) - Continue with Work out how sbws can report excluded relays in the bandwidth file (#28563) - Work on Ignore bandwidth file lines with "vote=0" (#29806) - Create a blog post about work done and future work (#29724) - Continue with DirAuths should expose bwauth bandwidth files (#21377)
Week 18 March (actual) - Missing diagnostic keys in relay lines (#29854) - sbws should show relays for diagnostics (#29853) - Minor fixes from observed behaviour in the public network (#29891) - Include new monitoring KeyValues in the bandwidth-file-spec (#29754) - Revisions
Week 24 March (plan) - Document next steps (#29723) - Create a blog post about work done and future work (#29724) - Continue with DirAuths should expose bwauth bandwidth files (#21377) - Create 1.1.0 release (and create maint branch) (#29750) - Deploy 1.1.0 in one dirauth (part of #29290) - Revisions - Possible new bugs
Needs help with: - When i'll have a blog post draft, i'd like omeone in net-team to review it (probably teor, mikeperry, nickm and/or arma) - Question left in #21377
asn: Week of 03/18 (planned): - Continue work on #28634. - Do merges/reviews. - Get #28636 finalized. - Fix prob_distr coverity issues. Week of 03/18 (actual): - Worked more on #28634 (design a WTF-PAD machine) but got intercepted by various 040-related and prob-distr tickets and didn't manage to spend as much time as I wanted here. - #28636 finalized and merged! - In #29693 did analysis on the current prob distr stochastic tests and reduced their false positive rate. We have #29847 for future work here. - Fixed coverity issues on prob_distr with the help of catalyst and riastradh: #29805 - Reviewed #28652, #22029, #28983. Week of 03/25 (planned): - Started the week sick. - Hoping to have time to concentrate on #28634. My goal here is something simple, with low bandwidth overhead, that will fool the basic classifiers from the USENIX paper, as well as a basic analysis on future steps. - Do reviews/merges etc.
ahf: Week of 3/18 (planned): Sponsor 19: - Second review of #29734. - Continue with #29207. Misc: - Network team bug triage. - Get Gitlab to run :-S - Talk with Erin, Cohosh, and Gaba about what we do with performance review for anti-censorship team. Week of 3/18 (actually) Sponsor 19: - Review of #29734. - Began review of #29297. - Small progress on #29207. Misc: - Got Gitlab to run on https://dip.torproject.org - next step is to get LDAP login integrated. - Think we found a solution for doing useful feedback for the anti-censorship team too! - Patches for 040-must tickets: #29691, #29136, #29874. - Try to solve the Coveralls/Cache issue on Travis in #29036. Week of 3/25 (planned) Anti-censorship team: - Catch up on S19 tickets this week and less network-team things. - Spend a day on making progress with Gitlab. - PHW starts next week(!) Network team: - Follow up on 040-must tickets that are in review. - Weekly reviews.
=======
T
-- teor ----------------------------------------------------------------------