Hi!

Network meetings are happening every Monday at 1700UTC on #tor-meeting in irc.oftc.net. Everyone is welcome to participate in them!

We had a short meeting on July 6th and here are the logs and notes.

Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-07-06-17.00.log.... Pad: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-...

Contents of the pad for today:

== Network meeting pad! ==

Next meeting is at Monday 29th June 1700 UTC on #tor-meeting on OFTC.

June Schedule: * Monday 6 July 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.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 tor-project mailing list archive for older notes.) 15 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002877.html 22 June: https://lists.torproject.org/pipermail/tor-project/2020-June/002890.html

== Stuff to do every week ==

Let's check and update our roadmap:

What's done, and what's coming up? Any change?

Board: https://gitlab.torproject.org/groups/tpo/core/-/boards

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:

Merge requests in Core:

https://gitlab.torproject.org/groups/tpo/core/-/merge_requests

Let's check out 0.4.4 release status and open tickets!

Tickets in 0.4.4.x with no owner. https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&...

nickm:

https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&...

dgoulet:

https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&...

ahf:

https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&...

asn:

https://gitlab.torproject.org/dashboard/issues?scope=all&utf8=%E2%9C%93&...

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

------------------------------- ---- 6 July 2020 -------------------------------

== Announcements [please date] ==

== Discussion [please date] ==

* Request for update on fallback list (6 July)

=== 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 29 June (planned): - More S55 work - 044 work - Investigate problems building/running with Openssl 3 alpha (tor#34139) - Maybe move OSS-fuzz off of openssl 3? - Write a proposal for packing multiple commands into a relay cell. - More thinking on congestion control - Work on stable releases Week of 29 June (actual): - More s55 work - Several 044 tickets - started proposal for packed relay cells - Backports with ahf - Wrote a possible migration plan for gitolite (the easy parts) Week of 6 July (planned): - Revise my working checklists, and distribute them? - Stable releases-- aim for end-of-week. - Review and merge - S55: - Export statistics - - 044 work: - All "must", all "should". - Some "can"? - Release packed cell proposal (fitting multiple relay commands in a cell)

ahf: Week of 29/6 planned: - Delete unused labels from Gitlab. - Try to solve Gitlab#41 with Hiro since it makes working with GL a bit more frustrating with our git.tpo/gitlab.tpo hybrid setup. - Do merging/backporting of Tor things. Week of 29/6 (actually): - Got rid of all the GL labels. - Did not solve Gitlab#41 - Learned how to do merging thanks to David. - Worked on backports. - Tried to figure out the issue in the 3 \r\n Windows issues. - Back on Android/Browser stuff. - Got iOS on-device testing to work for the Tor.framework network extension. Week of 7/6 (planned): - Windows \r\n issues (#33781, #26316) - Get profiles done on iOS for memory consumption. - Work on Android stuff with the Browser Team. - Help if I can with Gitlab#41.

asn: Week of 29/06 (planned): - More PoW work - A look at v3 metrics. - More OBv3 hackathon. Someone is hacking on distinct descriptor support. - Need to adapt the gitlab process to using MRs as discussed on Thurdsay. - A bunch more reviews & merges. Week of 29/06 (actual): - Lots of network team reviews/merges/bugfixes work. - Some v3 metrics work. - More OBv3 reviews. - Triaging gitlab tickets. Week of 06/07 (planned); - Going AFK on Friday so biggest priority is to finish all reviews/merges/044 tickets by then.

jnewsome: Week of June 22 (planned): - More profiling of shadow/phantom and start work on optimizations Week of June 22 (actual): - Ported "interposable libc" patch to centos 7 (our benchmarking platform). This version of glibc took a bit more work. - Switched ptrace-based shadow/phantom to use PTRACE_SYSEMU, substantially improving performance. Week of June 29 (planned): - Fix https://github.com/shadow/shadow/issues/853 - Help with shadow/phantom benchmarking and optimization as needed - Work on shadow test code-coverage measurement strategy Week of June 29 (actual): - Fixed https://github.com/shadow/shadow/issues/853 - Got Rust + C code-coverage working and in our CI. Still cleaning up. - Proof-of-concept implementation of shadow/phantom optimization for greatly reducing memory marshalling overhead Week of July 6 (planned): - Get code-coverage PR cleaned up and merged - Implement phantom memory-marshalling optimization "for real" and merge

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 Week of June 15 (actual): - started work on more chutney documention - opened discussions on gitlab about chutney components Week of June 22 (planned): - continue chutney discussion/work - #32888 / work on Address config to support IPv6

dgoulet: Week of 29/06 (actual): - s55: See #33049 for progress. Most of my week was on IPv6 tickets both on code or review. - Merges and reviews. - Wrote hs-v2 deprecation blog post. Published now. - We got the HS-v2 deprecation warning #40003 in. Week of 06/07 (planned); - Simply continue s55 work... - If time allows it, really need to address the fallbackdir situation.