Hi!
You can find our meeting logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-11-26-17.59.html
Below is a copy of the contents of our pad.
= Network team meeting pad! =
This week's team meeting is on Monday at 1800 UTC (1 hour later for daylight saving time) on #tor-meeting on OFTC.
Welcome to our meeting! First meeting each month: Tuesday at 2300 UTC Other meetings each month: Mondays at 1800 UTC (1 hour later for daylight saving time) 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.) 29 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002036.html 6 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002047.html 12 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002054.html 19 Nov: https://lists.torproject.org/pipermail/tor-project/2018-November/002074.html
== Stuff to do every week =
* Let's check and update the roadmap. What's done, and what's coming up?
url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrr...
* Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrr...
* 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...
* Let's look at proposed tickets!
0.3.5 (bugs only): https://trac.torproject.org/projects/tor/query?status=accepted&status=as...
0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=as...
== 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 actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbdG...
<< Remember that priority is Sponsor 8 - roadmap is sort out by priority >> Activity O2.5 is the one we are missing and need to be done in 2 months.
------------------------------- ---- 26 November 2018 -------------------------------
== Announcements ==
Next week's meeting is the first meeting in December, it's on Tuesday at 2300 UTC.
Please don't bulk-delete all the old entries from this pad any more. Instead, delete the "planned" and "actual" for the previous week, but leave the "planned" for this week in place. Please check the dates before deleting.
Check other's people call for help in their entries.
Snowflake kickoff meeting on November 27th: overview and what needs to be done. TUESDAY november 27th at 23 UTC in #tor-meeting <<-- Come to the party!
== Discussion ==
What is our testing plan for the sponsor 8 bootstrap changes? - How many different failure conditions are things we can simulate easily?
How do we test clock skew to avoid regressions? - Is "chutney + libfaketime" an option? -nickm
Should we add more testing time to all our funding applications? - I feel we usually start with a lot of testing time, but we wind up starting very late. See sponsor8 for one example, sponsor19 for another. -nickm
Can anyone review sbws #28588 (python code)? I was very involved in the ticket, so I would like another perspective. (I can also do a review.) - nickm will have a look, but it will be nice if others can too.
* Is our process for "proposed" working? <-- we still didn't go through it yet teor says: things seem to get stuck in proposed.
* sponsor 8 work
O2.5 (bootstrap reporting) is most important
- right now working on this: catalyst, ahf, dgoulet, teor. any of you need help with it?
* Please see tickets with tag "035-rc-blocker?" -- are any of them really rc blockers? Are there any other true rc blockers? https://trac.torproject.org/projects/tor/query?status=accepted&status=as...
Reviewer role responsibilities: https://pad.riseup.net/p/q0s3rQxVzSeZ - PLEASE look at the pad for options. Discuss and vote for one.
Release schedule: any changes?
== 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!
Nick: Week of 11/19 (planned): - Send comments about prop295 draft back to Tomer et al - Write tests for family compression branch #27359 - write tests for dormant branch #28335 - Inbox zero - interviews - book travel for brussels - Vacation Wed through Fri. Week of 11/19 (actual): - Sent comments back to tomer et al wrt prop 295 (relay crypto) - Wrote tests as plan - Review, merge, etc - Implemented prop 293 (know when to publish) - Implemented prop 297 (safer protover shutdowns) - implemented prop 298 (canonical families) - Vacation Week of 11/26 (planned): - book travel for brussels - meeting wrt privcount, tuesday, I think - review & merge aggressively - help everybody with deliverables - Release 0.3.5.6-? so that it can make the mid-december TB release? - Triage rotation - Identify 035-rc-blocker issues? Notes: - I won't be here next week; I'll be en route to the mozilla meeting
Want help with:
Mike: Week of 11/19 (planned) - Short week. - Vacation next monday and tuesday (will miss meeting). help with: Nick/asn: Can we decide on something I must-do this week? Like update the paper and do maybe one WTF-PAD crucial item that is a blocker? That way I don't get distracted and drop something until next weds.
ahf: Week of 11/19 (planned): Sponsor 8: - Work on #27100 while we move forward with reviews of #28179. - Add missing tests to #28179. - Figure out what we do with benchmarks for #28409. Sponsor 19: - A few more interviews left. - Prepare for Snowflake kick off meeting next week (the 27th!) Misc: - Test #28518 on FreeBSD. Week of 11/19 (actually): Sponsor 8: - Got #28179's test coverage up to 100% on Unix for functions. - Review process with David for #28179, first set of changes made. - Talked with Catalyst about #27100, looked at their orconn-tracker branch for #27167, trying to figure out what a good solution and emit bootstrap events somehow for the PT case. Sponsor 19: - Did two interviews last week and today. - Went over all the Snowflake tickets on trac to see what the Snowflake people have in mind. Misc: - Tested and reviewed #28518. - Talked with Juga about #21377 Week of 11/26 (hopefully) Sponsor 8: - Work with David with review on #28179, once he is happy I'd very much like Nick to also have a look at especially the Windows code. - Continue with s8-bootstrap and #27100 - Run simpleperf tests for #28409 and compare results. Sponsor 19: - Figure out next steps for candidates. - Snowflake meeting tomorrow at patch party time! Please have a look at https://trac.torproject.org/projects/tor/wiki/doc/Snowflake before our meeting :-) Misc: - CI and coverity duty.
asn: Week of 11/19 (planned): - Continue review and striking out items from the WTF-PAD TODO list. Hopefully we can have the branch in merge_ready soon. - Continue with the anti-censorship team interviews. - Do reviews. Week of 11/19 (actual): - Continue crunching through WTF-PAD (#28142): - Worked on probability distribution code and tests provided by Riastradh. This took a while to understand and go through (it's thick statistics code) but the current code seems to work and is really well tested. I fixed the code and unittests up to fit with the Tor codebase and I pushed it in a new PR. After Riastradh ACKs it, I plan to squash it for Mike and Nick: https://github.com/torproject/tor/pull/543 This code can be used both for WTF-PAD and for privcount tests. - Continued doing histogram tests. - Continue doing anti-censorship interviews. - Help teor with some s8-bootstrap guard stuff (#24661) - Do reviews. Week of 11/26 (planned): - Continue going through the WTF-PAD TODO list. - Open tickets for future work on Riastradh's probability distribution code that don't need to happen right now. Help with: - All good.
dgoulet: Week of 11/19 (planned): - Released torsocks 2.3.0 this morning (\o/) - Big s8 ahf's branch has arrived in my courtyard for review: #28179 - Continue work on #28335 with nickm. Week of 11/19 (actual): - One pass on #28179 and did a 0.5 pass on the fixes made by ahf. - Second round of review on #28335 and merge_ready this morning! - Review and triage tickets. Week of 11/26 (planned): - Finalizing #28179 with ahf for upstream merge. I expects the branch to be ready for nickm's considerations today or tomorrow at worst. - Work on the remaining part of #25502, a s8 master ticket. Finalizing specs within #28180 to match implementation. - Whatever comes my way for s8 at that point.
gaba (offline) : Week of 11/19 (actual): - anti-censorship interviews - ooni roadmap - OOO thursday & friday off monday & tuesday (will be on tuesday for the snowflake meeting) - grant/pm coordination Week of 11/25 (planned): - anti-censorship interview - gettor meeting to check on work and move it forward between teams - snowflake meeting and start planning help with: - communicating anything about sponsor8-bootstrap help/needs and progress
catalyst: week of 11/19 (2018-W47) (planned): - following up with Nick about #28226 if needed - finishing up review of #28226 (pubsub) - #27167 - reviews - travel request for Brussels week of 11/19 (2018-W47) (actual): - talked some with riastradh about bootstrap reporting as used by Brave - fix for #27405 on my WIP branch orconn-tracker (during bootstrap stop distinguishing a consensus lacking exits; it often guesses wrong anyway) - made some progress on orconn-tracker for #27167 (track first orconn during bootstrap) - #27167 work will use a simpler, more minimal version of the pubsub concept that is synchronous for now. nothing it replaces is currently async anyway - found a minor bug while working on #27167 -- submitted patch in #28524 - talked with ahf re bootstrap progress reporting and PTs - talked with nickm re some about torguts stuff about channels, circuits, connections - talked with teor re some sponsor8 bootstrap reporting stuff - 11/22 and 11/23 off as TPI holidays week of 11/26 (2018-W48) (planned): - proof of concept for orconn-tracker (#27167) - travel request for Brussels - reviews (priority on the sponsor8 ones) help with:
haxxpop: help with:
teor (offline): Week of 19 Nov (planned): - I am on CI rotation - Continue to work on s8 bootstrap tickets - pick guards from a reasonably live consensus (#24661) - do path selection from a reasonably l34ive consensus (#28319) - Maybe: Fix the s8 chutney consensus failure bugs - Maybe: Make the fallback script ignore addresses in the whitelist, so we can rebuild the fallback list - Defer: Any more reviews on sbws - Defer: Most other tasks
Week of 19 Nov (actual): High-Priority: - Opened tickets for CI/Coverity failures: - stem Travis (2 fixed) - Appveyor OpenSSL (#28574, not fixed yet) - Coverity spurious memory leak in memoize_protover_summary() (#28592) - Coded and tested "pick guards from a reasonably live consensus" (#24661) - Worked on other s8 bootstrap bugs (#23605 and children) Medium-Priority: - sbws 1.0 code freeze triage - tickets and spec for analysing missing relays in sbws - worked with metrics to improve bandwidth authority analysis (#28137) - code reviews Time-Sensitive: - Metrics job applications - Meeting about Mozilla's privacy-preserving user stats system "Prio" - Helped with sponsor 19 analysis of Orbot Onionoo load
Week of 26 Nov (planned): High-Priority: - Send tor-dev email about next week's meeting time (on Thursday, to avoid confusion) - Continue to work on s8 bootstrap tickets - accept clock skew for 24 hours in the future, as well as in the past - integration testing for clock skew? Medium-Priority: - up to 1 day of sbws reviews - Metrics job applications - Code reviews
Week of 26 Nov (actual): High-Priority: - Medium-Priority: -
Help with: - How do we test our sponsor 8 reasonably live consensus code? (see discussion) - Do I have enough time to write PrivCount blog post for the EoY campaign? <-- it depends on how the other work on s8 that you have on your plate is going. It seems like sponsor 8 is higher priority? <--- yes (gaba: send me a message to chat about it)
juga (offline): - Week 11/19 (plan): - review more tickets about rounding - check that there are not TODOs related to the moment when we changed sbws to work as torflow - continue with "Serve bandwidth file used in the next vote" - continue with "In a private network some relays advertise zero bandwidth-observed" - Week 11/19 (actual) - review more tickets about rounding - check that there are not TODOs related to the moment when we changed sbws to scale as torflow - monitor relays that are not measured by sbws - include the consensus measured bandwidth when calculating the minimum of the descriptors' bandwith - my roadmap on tickets has changed (thanks teor for reorganizing tickets) - Week 11/26 (plan) - continue with the work to monitor relays that are not measured - continue with the work to include the consensus measured bandwidth when calculating the minimum of the descriptors' bandwith - maybe some sbws refactoring