[tor-project] Network team meeting notes: 26 Feb 2018
nickm at torproject.org
Mon Feb 26 22:04:45 UTC 2018
Meeting logs at:
Meeting pad contents below.
Network team meeting pad, 26 Feb 2018
Welcome to our meeting! Mondays at 1800 UTC on #tor-meeting on OFTC.
(This channel is logged while meetings are in progress.)
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!
Note the meeting location: #tor-meeting on OFTC!
Meeting notes from previous weeks:
, search "network team"
* 0.3.3.x is in feature-freeze. No new features (except for
#24902, which has permission.).
* Please, work on bugfixes! It would be great to have this release
release on time. (Planned date is 15 April)
* There are tons of tiny 0.3.3.x tickets. Maybe if you can do one
of them in <X minutes for some small X, you should just do it?
* The 0.3.4.x merge window opened on Feb 15.
* Please fill in the code subsystems spreadsheet at
If you review tickets, feel free to add a column with your name.
* Please fill in Isabela's heat-mapping exercise with areas of tor
work: what are our priorities? https://pad.riseup.net/p/38VbTZUIzG4X
* No GSoC for Tor :'( [this time]
* isis cannot attend Rome :(
* Tor Meeting starts in 2 weeks: Sunday 10 March (Hackfest) to
Thursday 15 March (Unstructured Day)
* Jon will book accommodation for the May hackfest (Wednesday 30th
- Sunday 3rd) by the middle of this week. Then people can book
flights. [catalyst: is location for hackfest still undetermined?]
[dgoulet: It is Seattle, see hackfest pad for details.] [catalyst:
there was talk about moving to Portland due to hotel cost] [Afaict,
still Seattle. Hotel booking is ongoing so we'll notify the list once
we have that settled for flight arrangements].
* Review-group-32 is open! There are 5 tickets in needs_review.
* Review-group-33 is open! There are 5 tickets in needs_review.
* teor moved some needs_review tickets from "Tor: unspecified" to
"Tor 0.3.4", so the next review group will be a big one. Let's try not
to lose needs_review tickets in other milestones!
* Team rotation roles are open for March.
teor also added "Frontline Support", which they can do most of the time.
* teor is happy to do Coverity rotations, but thinks they might
need a login or a mailing list subscription. [Ask nickm if you need a
coverity login; he'll make one for teor.]
* #25324 (about tor-releases.git), IRC discussion last week didn't
end up in favor of it. Lets not
bikeshed too much but now is a good time to put in your opinion.
(On the ticket, perhaps?) <-- Yes, right place to do so.
* Subsystem maintainer (see spreadsheet). We should maybe assign
them to developers and start
using that for tickets. [
* heatmap (review and what's next) isa can lead [
* Last week:
- Finished Experimental PrivCount (it's feature-complete)
- More May hackfest planning
- More Proposal meetings
- Designed some demo code for typical floating point issues.
Rust is nice for demos in docs
- Reviewed a few tickets
* This week:
- Test Experimental PrivCount on a live relay
- Update the Network Team Useful Queries page to be more useful (WIP)
- Make trac user page that lists the tickets I'm working on in
- Review and revise tickets
- Write some Rust. Write some floating point code. Watch
rustc's output carefully
* Last week:
- More work on upcoming releases
- More rome planning/prep with isa
- bugfixes, 033-must bug triage, review, merging, etc
- worked on a better protover voting algorithm.
- Dove into most frequent* wakeup events and what we can do to
reduce or eliminate them.
[* That is, the ones scheduled with highest frequency.]
- Many meetings
- Skimmed my old algorithms text
- Finished/published prop290 (rolling expiration of consensus methods)
- Made a tor-rust-dependencies repo
- Discussed releases repo (#25324)
* This week:
- Many meetings
- Try to do security releases (0.2.9 and up).
- TROVE-2018-001 review status? [catalyst: changes look
ok, doing manual builds. done!]
- Anything I should merge or backport before releases?
[dgoulet: If you feel like it, #25316 but not that critical]
- More rome prep
- On call for jury duty on Tuesday. Might not be needed, but
if I am, this will consume all of Tuesday, and possibly more :/
- Work on 0.3.4 issues, 0.3.3 issues
- Open tickets for making events less frequent
- Decide on power-saving api approach with ahf
* Last week:
- Found #25312 while working on circuitmux performance for which I opened
#25328 and worked on it but nothing final (Development in
- Some DoS ticket triage to better organize SponsorV.
- Finalized #24767 from asn's review. Now in merge_ready for nickm.
- Ticket #25226 is awaiting some feedback from Roger and interesting
comment to take into account from cypherpunks.
- See timeline for the rest:
* This week:
- Continue working on my 033 and 034 tickets.
- New stable series will have the DoS mitigation so I'll keep an eye out
for any issues arising from these releases.
* Last week
- Working on vanguard controller structure and feature brainstorming
- Reviewed side channel attacks to see if they detected by a controller
- Looks like yes, though there may be CIRC_BW/STREAM_BW mis-counting bugs
- Did a bit of roadmapping for sponsor2+v. Also filled out heatmap,
component owner sheets.
- Coordination for upcoming OTF grant
* This week:
- More OTF coordination
- Continued vanguards work
- Reviewed #17945 and #24767 and #25306!
- Investigated newest SRV bug #24815 courtesy of teor.
- Did some digging in #25347: our latest important guard bug.
- Helped new volunteer with #6236. 6 years old easy refactoring
ticket now finalized.
- Some more work on guardfraction remnants #24456.
- Filled out isa's roadmapping/voting exercise. Talked some more
Did some more spreadsheet tricks on the subsystem maintainer spreadsheet.
Please fill it out if you haven't:
- More reviews and bugfixes. Particularly #25306, #25347, #24815, etc.
- Organizing SponsorV work and seeing what's needed.
- Wednesday: Doing Tor talk at ENS Paris with Lunar.
- Wrote a script to extract main loop event stats.
- Baselined idle client event loop numbers in
- Tiny patch for Shadow https://github.com/shadow/shadow/pull/403
- Trying to wrap my head around Shadow's way of not using the
main.c event loop functions and how to measure things sensibly.
- More event loop and Windows experimenting. Reading MSDN.
- Added Rust support and open sourced the Tor vim plug-in:
- Added a SyslogFacility config entry in #25355 for setting syslog
- Answered team surveys.
- Work with Nick on more event loop and power management features.
- Prepare some info for the mobile session in Rome about core Tor
progress since Montreal.
- Look at Isa's Roadmap email questions.
- Look into #24368 (zstd tuning) (moved forward from last week).
start working with folks on planning sponsors (only) work for
the 6 months roadmap [ahf + catalyst -> i pinged you on this]
hope to start converting the info on pad for sponsor tasks
into trac tickets this week
share orientation for planning in rome (specially for
last week (2018-W08):
- TROVE patch review
- roadmappy stuff
this week (2018-W09):
- review tickets
- travel prep
- CoC and SoV feedback
- are we doing Rust stuff at Rome and if so what prep should
we do for it?
- Catch up on email backlog
- Prototype for Rust wrappers for SHA2 code #24659, can't get
it to link to both libtor and libor-crypto for the life of me
- Call/pair programming/review with komlo about the Rust
logging module, I promised to take over the patch and do whatever
fixups nick requested since she's quite swamped right now
- Documented the setup of the moat reflector for Isa
- Documented the status of the moat project (done!) :)
- More large create cell work #24986 to clean up my branch and
show it for preliminary review
- Getting the frickin linker to link the stuff
- I forgot to review #25268 last week! sorry! will do this afternoon
More information about the tor-project