[tor-project] Network meeting notes, 15th June 2020
Gaba
gaba at torproject.org
Mon Jun 15 17:39:02 UTC 2020
Hi!
Network meetings are happening every Monday at 1700UTC on
#tor-meeting in irc.oftc.net
We had a meeting on June 15th and here are the logs and notes.
Log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-15-17.00.log.html
Pad:
http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-netteam-2020.1-keep
Contents of the pad for today:
== Network meeting pad! ==
Next meeting is at Monday 22 June 1700 UTC on #tor-meeting on OFTC.
June Schedule:
* Monday 22 June 17:00 UTC
Welcome to our meeting!
We meet each month at: Mondays at 1700 UTC
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.html
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 tor-project mailing list archive for older notes.)
1 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002857.html
8 June:
https://lists.torproject.org/pipermail/tor-project/2020-June/002865.html
== Stuff to do every week ==
Let's check and update our roadmap:
What's done, and what's coming up? Any change?
All the trac tickets for the roadmap are in the team's page:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam
S28 & S30 - Continue after October - Ahf
S55 - Nickm & dgoulet
Non sponsor stuff
DoS defenses = Dgoulet + Asn
Library Size reduction = Ahf + Dgoulet
sbws = Ahf + Juga
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&component=Core+Tor%2FTor&or&status=needs_review&component=Core+Tor%2Fsbws&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=changetime&col=reviewer&col=keywords&order=changetime
Go over our 0.4.4 status page at
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases/044Status
. (If maint-0.4.4 were released as stable tomorrow, what would we
regret?) - scheduled to enter feature freeze on Monday June 15th
== 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.
* Check other's people call for help in their entries.
Volunteers need help. Please help them when you are around. Maybe we
should have times of day when different people are responders, and
expectations of who helps.
-------------------------------
---- 15 June 2020
-------------------------------
== Announcements [please date] ==
Assigned reviews (Will put on gitlab when gitlab becomes RW again):
dgoulet -> #33816 Fill in missing IPv6 addresses in extend
cells
nickm -> #34065 Make routerset_contains_router() support
IPv6
asn -> #34433 Replace clang-format.sh with a faster, better
version
== Discussion [please date] ==
* [June 15] We need somebody to take over the fallback list. - dgoulet
will ask geko
* [Jun 15] Who (besides nickm) will look at Chutney?
* [June 15] Gitlab's questions (not ready yet but will be tomorrow)
044 milestone https://gitlab.torproject.org/tpo/core/tor/-/milestones/50
wiki page not transfered yet (all trac wiki is in
https://gitlab.torproject.org/legacy/trac/-/wikis/home)
roadmap: it will be eventually in
https://gitlab.torproject.org/groups/tpo/core/-/boards
do all of you have accounts?
* [Jun 15] Any needs_revision sutff that c should pick up?
=== Active Proposed Policies ===
* Pull Request Guidelines (stalled)
=== Design proposals under discussion ===
315: require more fields in directory documents (still waiting [6/1])
316: flashflow (asn and nickm are reviewing, should schedule discussion
with pastly. [5/18])
317: dns (under discussion on ML [5/18])
318: limit protovers (waiting for more commment; needs discussion [6/1])
319: wide everything (nick replied on ml; waiting for more discussion [6/1])
320: tap out again
- Do we have a consensus to replace this with a "deprecate v2 onion
services" proposal? If so, who writes it? [6/1]
protover rethinking (teor's email to tor-dev) (nick needs to reply [5/18])
321: happy families (need feedback [6/1])
322: dirport linkspec (need feedback [6/1])
== Recommended links ==
== Updates ==
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 8 Jun (planned):
- Prepare for 0.4.4 freeze
- Merge pending S55 code, and increase my command of the
remaining work on O1.1
- Talk with Metrics about S55 stuff?
- S69 wrap-up email
- Tor-unspecified triage: wow do we need it
- Code-formatting hacking.
Week of 8 Jun (actual):
- Merged teor's S55 work.
- S69 wrap-up email
- lots of triage discussion
- Code-formatting hacking
- S55 ipv6 reachability experiments
Week of 15 Jun (planned):
- Get chutney actually working with assumereachable disabled
(34445 through 34449)
- Work on aftermath of gitlab migration.
- Work with dgoulet to advance S55 planning.
- Get S55 reachability test more advanced.
- Release 0.4.4.1-alpha.
ahf (afk today due to public holiday):
Week of 8/6 planned:
- Work with the Admin team on Gitlab migration.
- As much other things as I can squeze in while waiting for
different batch tasks to complete. Focus on Fenix still.
Week of 8/6 actually:
- Worked with a lot of people on the Gitlab migration.
Week of 15/6 planned:
- Back to Fenix stuff with Browser Team
- Support Gitlab people if we go with that.
asn:
Week of 08/06 (planned):
- Reply on all the recent responses on PoW thread -- lots of work done
there.
- Publish fix for #32040.
- Merge prop#310 patch.
Week of 08/06 (actual):
- Did a proposal revision on the PoW thread. More work needed here.
- Merged #310.
- Reviewed and tested padding bugfixes: #30992 and #32040.
#30992 got merged, but #32040 needs a bit more tweaking.
Week of 15/06 (planned):
- More work on PoW proposal. Fold in David's work on the scheduler and
derive
results from that.
- Hopefully merge #32040.
- More reviews & merges
jnewsome:
Week of June 1 (actual):
- Added GH milestones and issues in shadow/shadow
- Sent out Tor Project update
- Added more thread/interposition APIs in shadow/phantom to support
more syscalls.
- Did some straceing to identify more syscalls we need for tor
Week of June 8 (planned):
- Hand off OnionPerf work for now (#33974: update to tgen 1.0)
- Identify more syscalls needed to simulate Tor.
(use nm/objdump; chutney; src/lib/sandbox)
- Figure out (how to avoid implementing) netlink
- Check whether we already can interpose Tor's name lookups (via
libevent)
Week of June 8 (actual):
- shadow/phantom: Identified and documented syscalls needed for Tor,
based on strace + sandbox config.
https://github.com/shadow/shadow/issues/849
- Reviewed PR to add file IO support for shadow/phantom
- More review for adding yaml config for shadow/shadow
Week of June 15 (planned):
- Work out logging from the shim with the new file IO design
- Help flesh out support for syscalls and libraries needed to
run Tor
- Start looking into code-coverage tools (gcov)
pastly:
Week of 18 May (planned):
- Finish bones of external FlashFlow repo (python?) to control
tor clients
that perform FF measurements
- Finish bones of little-t tor changes s.t. measurement can be
performed
- Discuss FlashFlow with network team devs as they have questions
c:
Week of May 25 (planned):
- close up work on #33609
- get started on other s55 tickets, potentially knock out 'easy'
ones first and take it from there
- update https://trac.torproject.org/projects/tor/wiki/doc/gsoc
with my information
Week of May 25 (actual):
- #33609 ready for review
- started hunting down and working on other Sponsor55-can and
-must issues
- talking in #tor-project about wiki
Week of June 1 (actual):
- opened and made #34381 ready for review
- IPv4 part of #32888
Week of June 8 (planned):
- #33598
- IPv6 part of #32888 <-- do you have a ticket for it?
Week of June 8 (actual):
- #32888 IPv6 PR: https://github.com/torproject/tor/pull/1932
- requested reproducibility info for
https://bugs.torproject.org/33598 -- maybe I'll start thread on tor-dev@
since trac is read-only
- wrote Outreachy blog post explaining Tor's IPv6 goals
Week of June 15 (planned):
- during meeting, poke someone about
https://github.com/torproject/chutney/pull/66
- chutney work with nickm (#34445 - #34448)
- force myself to remain regularly active on tor-dev@ so we can
get things done more efficiently :)
- in general just check behind myself and others to clean up
open issues in need of commentary or review
--
she/her are my pronouns
GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20200615/5484c66f/attachment.sig>
More information about the tor-project
mailing list