Hi!

Logs here:

http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-11-12-17.59.html

Pad contents below:

= 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.) 15 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002027.html 22 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002032.html 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

== 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.

* Remember that you can already book the flight to Brussels for hackweek. (Ask jon & gaba if you have any question)

------------------------------- ---- 12 November 2018 -------------------------------

== Announcements ==

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.

Nick's upcoming release plans:

Starting now: Stay up to date on backports. [See spreadsheet about backport status.]

Late next week, around Nov 23: TB releases with 0.3.5.4-alpha.

~Dec 3: 0.3.5.5-(rc or alpha) [Note short window from TB release!]

Dec 11: TB releases again.

~Jan 2: Release 0.3.5.6-(rc or stable). Release 0.3.4.10. Release 0.3.3.11.

Jan 15: Feature freeze for 0.4.0.

Later in Jan: Release 0.4.0.1-alpha.

Snowflake kickoff meeting on November 27th: overview and what needs to be done.

== Discussion ==

* 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...

* Is our process for "proposed" working?

== Recommended links ==

Cool talk on communication in teams http://lenareinhard.com/do-you-read-me-better-communication-for-stronger-tea...

== 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/5 (planned): - Comment on new version of crypto thing /prop295 - Review wtf-pad design and code (waiting on status update for proposal revisions) - Meet with B Bhumiratana to chat about net privacy - Plan and possibly start working on #2149 ("extra dormant") with dgoulet - Revise or merge #28226 (messaging system) - Release 0.3.5.4-alpha? - Possibly, design for testing sustems that use pub/sub. Week of 11/5 (actual) - Implemented a python version of prop295, circulated in network team. Got comments on new version's readability. - Reviewed wtf-pad design; initial architectural review of code. - Met with B Bhumiratana (Eisenhower fellow). He said he knows Haxxpop :) - Designed #28335 ("extra dormant nouveau") with dgoulet and started coding. - Released 0.3.5.4-alpha - Wrote enhancement for checkIncludes.py (#28362) to detect circular include structures among directories. Resolved the ones we have in lib. - Merge, Reveiew, etc. - Figured out OpenSSL 1.1.1/TLS 1.3 client problem (#28245) - Rearranged 035-can / 035-must tags a bit Week of 11/12 (planned): - Send comments about prop295 draft back to Tomer et al - Triage 0.3.5 must-do vs may-do stuff. - Continue revising publish/subscribe code pending comments from Taylor #28226. - Continue work on "dormant mode" logic for #28335. Hope to finish first draft, but might pend #28226 work. - Time permitting, add more tests for myfamily memory improvements (#27359) - Plan when to do next alpha/stable releases. - Write a schedule for upcoming releases - Backports to 0.3.4 etc

Want help with:

Mike: week of 11/5 (planned) - New GPG subkey. Kill me. - More WTF-pad proposal updates - Vanguards release? - WTF-PAD updates, fixups, tests - Datagram paper diff for nick week of 11/5 (actual) - WTF-pad proposal disussion - WTF-PAD updates, fixups (maybe 80% of the way through code review change requests) - Highlights: Supports 65532 states now with not much addtl overhead week of 11/12 (planned) - GPG? Does anyone use it? can we agree to stop? Kidding. ;) - More WTF-PAD fixups, tests - Vanguards release? - Datagram paper diff for nick help with:

ahf: Week of 11/05 (planned): Sponsor 8: - Finish #28179 and get it reviewed+landed. - Talked with HC from TGP about #28409. Sponsor 19: - Continue wrapping my head around PT tasks for s19 (mostly focusing on Snowflake). - Help UX with #27385. - Anti censorship team hire. Misc: - Review #28298. - Do reimbursements from Mexico. Week of 11/05 (actually): Sponsor 8: - Got first patches for #28179 pushed to bugs/28179. Sponsor 19: - Looked at HTTPS Proxy (for the alt. PT part of S19) - Discussed #28298 with Antonela. - Interview with two candidates. Some pre-interview meetings with technical questions, etc. - Send out email to network team about S19 kick off meeting. Misc: - Reviewed #28298. - Didn't do Mexico reimbursement... Week of 11/12 (planned): Sponsor 8: - Hook up transports.c with the code from #28179 and test that it all still works on all our platforms -- begin on #28180 with David. - Begin on #27100. Sponsor 19 - One interview this week with a candidate. - Continue looking into Snowflake. Misc: - Do the Mexico reimbursement that I keep postponing. - Book flight tickets for Brussels.

asn: Week of 10/29 (planned): - Continue reviewing, refactoring and testing the WTF-PAD code. - Try to come up with a useful WTF-PAD state machine that we actually want to merge. - Do reviews. Week of 10/29 (actual): - Continue reviewing, refactoring and testing the WTF-PAD branch. Passed knowledge to Nick so that he can also do some reviewing. Found some bugs and wrote some commits to improve code. - Did reviews (#28308, #28906, #28184, #28245). - Help out with the anti-censorship team hires. Week of 11/05 (planned): - Sufficient review has happenened on the WTF-PAD branch. It's now time to start working on the TODO items and wrapping this up so that we move towards merge. Coordinate this with Mike. - Do reviews. - Continue helping with the anti-censorship team hires. Help with: - Mike we should figure out next steps to move thjis to merge.

dgoulet: (offline for meeting) Week of 11/5 (planned): - Planned, review and/or work on #28335 with nickm. - Available for ahf to review #28179 and then start working on the code for #28180 (s8). - Finalize whatever s8 other tasks come up this week. Week of 11/5 (actual): - Review #28330 subsystem branch from nickm. - Ticket work on HSv3 bugs: #27841, #28184. Week of 11/12 (planned): - Holiday on November 12th. - Review #28179 important s8 ticket then move on to #28180. - Help nickm with #28335 and childs.

gaba: Week of 11/5 (actual): - gettor follow up - hackweek cancel KU reservation - get into ooni work/roadmap - start looking at CVs that come up for data architect position for metrics team - several weekly meetings (ooni, metrics, fundraising, las vegas) and 1:1s - work on DRL proposal that was submitted on Friday Week of 11/12 (planned): - weekly meetings (ooni, metrics, fundraising, las vegas) and 1:1s - metrics data architect position - participate in interviews for anti-censorship team developer - ooni roadmap - gettor help with: - communicating anything about sponsor8-bootstrap help/needs and progress

catalyst: week of 11/05 (2018-W45) (planned): - reviews - bug triage rotation - 0.3.5 bugfixes as needed week of 11/05 (2018-W45) (actual): - bug triage - reviewed #28229 - continued reviewing #28226 -- sent comments on msg stuff - preliminary planning for Athens meeting week of 11/12 (2018-W46) (planned): - reviews - #27167 - 0.3.5 bugfixes as needed help with:

haxxpop:

Week of 11/5 (planned):

- Probably discuss about #28275. A lot of ideas are going through. So fun :). And I will fix it if there is something to be changed.

- Write the tor-keygen man page, if I have time left.

help with:

teor (online!):

Week of 5 Nov (planned): - Pick up a s8 bootstrap ticket, and do it - Try and make progress on the s8 chutney consensus failure bugfix tickets - Defer: Make the fallback script ignore addresses in the whitelist, so we can rebuild the fallback list - Defer: Work on PrivCount in Tor prototype - merge the crypto_rand_double() C code in #23061, and write a Rust equivalent - minor fixes to privcount_shamir - finish off the travis CI config for chutney / turn it into a config to test PrivCount in Tor

Week of 5 Nov (actual): - Started "pick guards from a reasonably live consensus" (#24661), found #28319 - More admin, hackfest planning - Cleared my ticket backlog, lots of little ticket updates, code reviews - Planning for s8-bootstrap - Reviewed metrics' total consensus weight and consensus weight by flag graphs - Extensive reviews on various sbws tickets - Looked at some CVs for the metrics position - Internet Freedom Hack presentation and mentoring

Week of 12 Nov (planned): - Continue to work on s8 bootstrap tickets - "pick guards from a reasonably live consensus" (#24661) - do path selection from a reasonably live consensus (#28319) - Fix the s8 chutney consensus failure bugs - Do a review of the sbws specs once a week - Defer: Make the fallback script ignore addresses in the whitelist, so we can rebuild the fallback list - Defer: Work on PrivCount in Tor prototype

Week of 12 Nov (actual): - sbws spec ticket review - more admin

Help with: - nickm, I would like help on how to access --RUNNING-FORKED in #28096. It seems to require an abstraction layer violation: argv is in tinytest.c, but tor code is in test_common.c. Is there some simple trick I'm missing? (So, IMO it would be okay to look at the "v" argument in main in testing_common.c: it is argv. Yes, that's a layer violation, but tinytest is under our control anyway. Alternatively, we could extend tinytest, I guess? I'll be around at the patch party time to talk more if it's helpful -nickm)

juga:

Week of 11/05 (planned): - tor code - continue with #21377: DirAuths should expose bwauth bandwidth files - continue with #22453: Relays should regularly do a larger bandwidth self-test - start with #26698: Authorities should put a hash of the bandwidth file in their votes - undecided on trying to start some tasks that are not priority but on which the rest of the work on bandwidth stuff might depend - Week 11/05 (actual): - Tor code - serve bandwidth files used in the votes (#21377) - include the digest of the bandwidth file in the vote (#26698) - Bandwidth File specification - correct scaling methods examples (#27690) - correct key/values (#28085) - Tor Directory Protocol specification - remove bandwidth file headers key/values (#28382) - include a "bandwidth-file" item the vote documents (#28359) - updated sbws Debian package to 1.0 - started to write about the bandwidth distribution goal problem - Week 11/19 (plan): - Tor code - Relays should regularly do a larger bandwidth self-test (#22453) - bandwidth testing circuits should be allowed to use our guards (#19009) - In a private network some relays advertise zero bandwidth-observed (#24250) - sbws - Change integration tests from bash to POSIX shell (#28106) - revisions - Help with: - anyone: review my tickets in "needs_review" :)