[tor-project] Network team meeting notes, 8 Jan 2019

Wed Jan 9 10:23:46 UTC 2019

Nick Mathewson <nickm at torproject.org> writes:

> Hi!  You can find our meeting logs here.
>
> http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-01-08-22.58.html
>
> Below are the contents of the meeting pad
>
>
>
> = Network team meeting pad! =
>
> This week's team meeting is at Tuesday at 2300 UTC 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
> On #tor-meeting on OFTC.
>
> January schedule:
>     * No meeting on 31 Dec or 1 Jan
>     * Following meeting on 8 Jan 2019, 2300 UTC.
>     * Meeting on 14 Jan, 1800 UTC
>     * Meeting on 21 Jan, 1800 UTC
>     * No meeting 28 Jan; (some of) the team will be at a face-to-face meeting.
>
> (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 list archive for older notes.)
> 3 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002117.html
> 10 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002120.html
> 17 Dec: https://lists.torproject.org/pipermail/tor-project/2018-December/002127.html
>
> == Stuff to do every week =
>
> * Let's check and update the roadmap.  What's done, and what's coming
> up? <-- Check who is doing what on s19 and s31 on January.
>
> url to roadmap:
> https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=856122210yy
>
> * Check reviewer assignments at
> https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdrriaYfUBQ/edit#gid=95993070
>
> Here are the outstanding reviews, oldest first:
>   https://trac.torproject.org/projects/tor/query?status=needs_review&component=Core+Tor%2FTor&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=changetime&col=reviewer&col=keywords&order=changetime
>
> 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
>
> * 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/TeamRotations
>   Core Tor/sbws is now part of the bug triage, CI, and reviewer assignment roles
>
> * Let's try a different way of looking at proposed tickets:
> https://pad.riseup.net/p/network-team-triage-2018
>
> 0.3.5 (bugs only):
> https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~035-roadmap-proposed&max=200&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority
>
> 0.4.0: https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~040-roadmap-proposed&max=200&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
>
> == General todo ==
>
> Please don't edit this pad with trolly stuff; if you do, you will
> force us to use a private pad again, even though it will make us sad.
>
> == 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/ISA5L5nH0Xu88iqSCx9ZjCXYSMKOBTdbUeWarbdGmxx
>
> * Check other's people call for help in their entries.
>
> -------------------------------
> ---- 8 January 2019
> -------------------------------
>
> == Announcements ==
>
> * Teor is bringing a proposal for proposed ticket (discussion during
> hackweek?). https://pad.riseup.net/p/network-team-triage-2018
> * We are going to start weekly checkins on anti-censorship work
> starting next week. I will send a mail later about it <gaba>
>
> == Discussion ==
>
>
> * Who needs help with reviews?
>   Here are the outstanding reviews, oldest first:
>   https://trac.torproject.org/projects/tor/query?status=needs_review&component=Core+Tor%2FTor&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=changetime&col=reviewer&col=keywords&order=changetime
>
> * we need a sbws reviewer for January that is not teor. who?
>
> * Sponsor 31 in da house. Modularization proposal. We have the
> milestones [0] and need to add tickets and start them in January. It
> will be included in the roadmap creation in Brussels.  [0] -> Sheet
> milestones of this document
> https://storm.torproject.org/shared/a-NKHPmkxDOuAGNaFpOrd3AIXJ4mDgIbL5sIjf4AHVP
> - Who is going to be doing them?
>
> * Closing tickets. Let's briefly come to an agreement on this.
> (closing tickets and opening new ones if there is something remaining
> from the old one).
>
> * S8 tickets need to be move to some other place. Who can do it this week?
>
> * Drafting Hackweek agenda. Let's find a day to meet and create the agenda.
>
> * draft agenda https://pad.riseup.net/p/tor-netteam-agenda-hackweek-2019.1-keep
>
> * poll to decide on a date
> https://www.systemli.org/poll/#/poll/qm6aFNWRZP/participation?encryptionKey=HncqIS9zYHxHpWrofGoUa6ihSfVvDrOBg0btTDix
>
>
> * Retrospective for S8 work https://pad.riseup.net/p/14rdcvvjS5ue
>
> * Network team needs and Priorities pad for DRL funding opportunity
> https://storm.torproject.org/shared/cDDK_EyXoIZoiOzt3YSRo3cCme0C-JAZe5nCdvbytyw
>
>
> == Recommended links ==
>
> 35c3 talk on internet history with an economics perspective
> https://media.ccc.de/v/35c3-10019-internet_the_business_side#t=3729
>
> == 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!
>
>
> gaba:
>     Week of 01/01 (actual):
>
>  - read mails and organize work to be done by me
>
> Week of 01/07 (planned):
>
>   - back into 1:1s
>
>   - anti-censorship position follow up
>
> - S8 Q4 report
>
> - modularization proposal
>
> - s19
>
> - hackweek agenda
>
> Needs help with:
>
> - getting all the tickets mark as sponsor8 out of it (close them or
> have them somewhere else). Some of them may go into s19.
> https://trac.torproject.org/projects/tor/query?status=!closed&sponsor=Sponsor8
>
> - please add points to the tickets you already have done (thanks
> dgoulet for doing it here
> https://trac.torproject.org/projects/tor/ticket/28020 and thanks
> people that added them to the spreadsheet)
>
>

Hmm, seems like I put my status report on the old pad yesterday so it
never made it here. Here is my status report anyhow: 

asn:
    Week of 12/17 (planned):
    - Do the final steps to move #28142 to merge_ready.
    - Finish up with anti-censorship hiring.
    - Do reviews.
    - Maybe look at some hsv3 tasks I've been neglecting due to #28142.
    - Will be focusing on uni stuff on Thursday/Friday.
    Weeks since 12/17 (actual):
    - I got accepted for PhD! As discussed, I plan to spend approximately 2
      days a week in the university, but I will be flexible. My uni projects
      are gonna be about Tor so I will be doing relevant stuff: atm my
      professor likes WTF-PAD and privcount, but we will figure out next steps
      during the next two weeks as I meet with him more and the rest of the
      research group.
    - WTF-PAD branch (#28142) is finally in merge_ready! Oof. Here is some stuff I did to get there:
      - Addressed all of Nick's comments on PR#461.
      - Reviewed Mike's recent changes.
      - Rebased and squashed branch a bunch of times.
      - Added more unittests.
      - Closed various other Sponsor2 tickets on the roadmap.
      - Disabled the current padding machine and worked towards a new one
        #28634 that is still unclear if will get in before the freeze.
      - Worked toward additional features #28780.
    - More work towards anti-censorship hiring.
    - Did all reviews and caught up with open hsv3 stuff.
   Week of 01/08 (planned):
    - Get #28142 closer to merged (address review comments etc.)
    - See if we can get #28780 and #28634 closer to merge_ready by EOW.
    - More anti-censorship hiring.
    - Do some initial PhD stuff.
    - Coordinate with 2-3 people who contacted me because they want Tor talks
      to happen around Athens. First one is upcoming Monday in my home university.