- tor-project - lists.torproject.org

Community Team report for September 2019
by gus 08 Oct '19

08 Oct '19

Hi, Here's Community Team report for September 2019. Documentation ============= In the first week of September, Community Team hosted DoscHackathon, our first documentation hackathon <https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…> During the week, we had 70 registrations, 8 contributors, and over 70 pull requests to Support Portal, Tor Browser Manual, Tor Project main website and other web repositories. It was a lot of work, and we still have some open issues tagged as DocsHackathon. The participants received different Tor prizes according to their contribution. Many thanks to all who collaborated in some way: reviewing the pull requests, opening new issues, writing new content, fixing css, doing screenshots and many other things! <3 We also worked in the content migration from old FAQ to Support Portal - <https://dip.torproject.org/torproject/web/support/issues/43> These are the new sections on Support Portal: - About Tor: <https://support.torproject.org/about/> - Get in touch: <https://support.torproject.org/get-in-touch/> - Debian repository instructions: <https://support.torproject.org/apt/> And more content migrated to: - Relay operators: <https://support.torproject.org/operators/> - Tor Browser: <https://support.torproject.org/tbb/> Sponsor9 work ============= Since July, Community Team has been working on Sponsor9 phase 3, which consist of our partners from the Global South to organize Tor trainings with the mentorship and online help from Community and UX teams. In September, we reached out more than 15 partners from different countries inviting them to join us this new phase. As this partnership process is new to the Community team, we're slowly bringing the partners on board. User support ============ Frontdesk: since BridgeDB fixed ticket #28533 <https://bugs.torproject.org/28533>, Frontdesk queue slowed down and we don't receive more blank bogus email. Outreachy: We submmitted a proposal "Help Tor Project support our users" to Outreachy <https://trac.torproject.org/projects/tor/wiki/Outreachy#HelpTorProjectsuppo…>. Applicants will make contributions from October 1 to November 5. And the intern will work with us from December 2019 to March 2020. Outreach ======== - At the beginning of this month, we reached out some non-profits to spread and share bridges campaign: <https://blog.torproject.org/run-tor-bridges-defend-open-internet> - Pili did a talk during APIdays.io (Barcelona): <https://blog.torproject.org/events/apidaysio-barcelona> - Kushal gave a workshop on digital security + Tor workshop in Goa <https://www.debutsav.in/> - nvjacobo and marco19_ did a presentation about Tor in Cumbre de Contribuidores de Open Source Software, Guadalajara, MX <https://ccoss.org/> - Cybelle had a talk during ABCDev, in Sao Paulo, Brazil. - In September, Narrira and other volunteers organized a Tor training with human rights defenders in Rio de Janeiro. - Pili, Brabo and others have started to organize FOSDEM activities: <https://trac.torproject.org/projects/tor/wiki/org/meetings/2020Brussels> - Global South IRC meeting happened last September 27th - <https://lists.torproject.org/pipermail/global-south/2019-September/000260.h…> Next Global South meeting scheduled for Wednesday, Oct 30, 1600 UTC, #tor-south - We published a blog post about the digital security training and UX feedback cycle that the Community and UX teams have been working over the last two years. <https://blog.torproject.org/reaching-people-where-they-are> - Many members of our community joined the Global Climate Strike. And as part of this, we also added Global Climate strike bannerto the main website: <https://blog.torproject.org/join-global-climate-strike-20-27-september> Meta ==== Meeting notes * Community Team meeting notes 02 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 09 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team Meeting notes 16 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 23 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00… * Community Team meeting notes 30 Sep 2019 - https://lists.torproject.org/pipermail/tor-community-team/2019-September/00…

1 0

Tails report for September 2019
by sajolida 08 Oct '19

08 Oct '19

Releases ======== * Tails 3.16 was released on September 4 (major release). https://tails.boum.org/news/version_3.16/ * Tails 4.0 is scheduled for October 22. These are some of the changes that were introduced in Tails 3.16: * Removed pre-generated Pidgin accounts * Removed LibreOffice Math * Upgraded Tor Browser to 8.5.5 Code ==== * We started to integrate _Tor Browser_ 9.0 (#16356). * We started working on the upgrade to _Thunderbird_ 68 (#16771). * We did lots of work to improve the reliability of our test suite. * We did some initial research and tests on using _Portals_ to improve the UX of saving downloaded files from _Tor Browser_ (#10422 #15678). * We did some initial research on redesigning, in a Wayland-compatible way, our current sudo-based privilege separation model (#12213 and subtasks). * We improved the UX of the _Greeter_ and fixed a few of its most annoying bugs (#16095 and the tickets it blocks). This work will hopefully land in time for Tails 4.0 :) Documentation and website ========================= - We rewrote completely the instructions to backup the persistent volume: https://tails.boum.org/doc/first_steps/persistence/copy/ - We documented how to do right-click on Mac. (#15718) - We proposed to use Trimage to compress better the images on our website. (#17099) - We agreed on having a "People" page. (#17046) User experience =============== - We published a job offer on illustrations on what is Tails and how it works: https://tails.boum.org/jobs/illustrations_how_tails_work/ - We did some stats on how good people upgrade their Tails, with data from April 2019. (#17069#note-4) - 16.6% of boots (3800/day) had no direct automatic upgrade path to the latest version because they were more than 3 months old. - 3.8% of boots (860/day) were stuck before 3.6, which had broken all automatic upgrades. The impact of breaking all automatic upgrades in 3.6 was still huge even 1 year later. Hot topics on our help desk =========================== * Unfortunately we had some problems with our WhisperBack system, and because of that, some users were prevented from contacting us. We are looking into how to prevent so much downtime the next time. (#17110) * Tails can't establish a connection with obfs4 bridges and a hardware clock too far away from UTC is still ongoing. (#15548) * Graphics cards still give problems to some users. (#16447) Infrastructure ============== * We upgraded our very old Jenkins to the current LTS version (#10068). This in turn allowed us to implement a bunch of improvements and bugfixes that had been blocked by this postponed upgrade. * We kept working on making our web translation ready for prime-time. We're almost there! https://translate.tails.boum.org/ Funding ======= - We submitted a joint grant proposal with Tor and the Guardian Project to the DRL Internet Freedom program. - We added Monero and Zcash as cryptocurrencies in which you can donate to Tails: https://tails.boum.org/donate#cryptos - We received a $1 000 donation from TOP10VPN. - We prepared most of the content for our upcoming donation campaign: banner, blog posts, email, tweets, etc. (#16096) Outreach ======== Past events ----------- * sajolida attended the 1st Café Internet on September 19 in Mexico City: https://internetfreedomfestival.org/wiki/index.php/Ciudad_de_Mexico Upcoming events --------------- * intrigeri will facilitate a "Discover Tails and translate it into your own language" session at the Mozilla Festival on October 26-27 in London (UK): https://www.mozillafestival.org/ Translations ============ ## All the website - fr: 90% (5148) strings translated - es: 54% (3095) strings translated - de: 38% (2189) strings translated - it: 33% (1887) strings translated - fa: 30% (1721) strings translated - pt: 24% (1383) strings translated Total original words: 59107 ## Core pages of the website - fr: 94% (1669) strings translated - es: 88% (1572) strings translated - de: 66% (1178) strings translated - it: 62% (1114) strings translated - pt: 45% (801) strings translated - fa: 34% (606) strings translated Total original words: 16513 Metrics ======= * Tails has been started more than 746 622 times this month. This makes 24 887 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

September 2019 report for the Tor Browser Team
by Pili Guerra 08 Oct '19

08 Oct '19

Hi everyone! During September, the team has been busy at work on the ESR68 Transition as we work towards our first 9.0 stable release later on in October. During this period we have made three releases: Tor Browser 8.5.5[1], 9.0a6[2], and 8.5.6[3]. The first release incorporated a number of important security updates[4] to Firefox and was expected to be the last release in the 8.5 series. However, due to an issue with the aarch64 version on Android which was causing a crash on every launch[5] we had to release 8.5.6 for Android only the following week. As for the 9.0 series, we shipped our first alpha release based on Firefox 68 ESR at the start of the month. September also marked the sunsetting of Orfox[6] with a final update[7] pointing users to download Tor Browser for Android as the definite way to take advantage of the full protections Tor Browser offers, on Android. Other than that, we are finally done adapting our Linux and Windows toolchains for Firefox 68 ESR. We have also made some strides in getting our bundles to build reproducibly and hope to work on Android build reproducibility during October. Another important piece of work during September involved making Tor Browser on macOS compatible with Apple's notarization process[8] and we have started rolling out these changes with the alpha series at the beginning of October. The full list of tickets closed by the Tor Browser team in September is accessible using the `TorBrowserTeam201909`[9] keyword in our bug tracker. During October we are working hard towards our first 9.0 stable release based on Firefox 68 ESR as well as continuing work on the updater for Tor Browser nightly desktop builds. We also hope to ship a few more locales[10], Thai, Lithuanian, and Malay, in our alpha series. Finally, once the first stable 9.0 release is out, we will start picking up sponsor work again, finishing off the work that was started before the Firefox 68 ESR transition period to integrate client-side authorization to onion services v3 in Tor Browser[ 11]. All tickets on our radar for October can be seen with the `TorBrowserTeam201910` keyword in our bug tracker.[12] Thanks for reading! Pili [1] https://blog.torproject.org/new-release-tor-browser-855 [2] https://blog.torproject.org/new-release-tor-browser-90a6 [3] https://blog.torproject.org/new-release-tor-browser-856 [4] https://www.mozilla.org/en-US/security/advisories/mfsa2019-27/ [5] https://trac.torproject.org/projects/tor/ticket/31140 [6] https://blog.torproject.org/orfox-paved-way-tor-browser-android [7] https://trac.torproject.org/projects/tor/ticket/29955 [8] https://trac.torproject.org/projects/tor/ticket/30126 [9] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [10] https://trac.torproject.org/projects/tor/ticket/29935 [11] https://trac.torproject.org/projects/tor/ticket/30000 [12] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

minutes from the sysadmin meeting
by Antoine Beaupré 07 Oct '19

07 Oct '19

Hello! Here are the minutes from this month's sysadmin meeting. # Roll call: who's there and emergencies anarcat, hiro, ln5, qbi and weasel are here. # What has everyone been up to ## anarcat * announced LDAP sudo transition plan ([#6367][]) * finished first phase of the hiera transition ([#30020][]) * deployed trocla in test ([#30009][]) * coordinate textile shutdown ([#31686][]) * announced jabber service shutdown ([#31700][]) * closed snowflake -> TPA transition ticket for now, external monitoring is sufficient ([#31232][]) * improvements on grafana dashboards * gitlab, nextcloud transitions coordination and oversight * ooni.tpo to ooni.io transition coordination ([#31718][]) * bugtracking on networking issues ([#31610][], [#31805][], [#31916][]) * regular janitorial work (security upgrades, reboots, crashes, disk space management, etc) * started needrestart deployment to reduce that work ([#31957][]) * completed the "reports card" questionaire ([#30881][]) * continued work on the upstream prometheus module * tested puppetboard as a Puppet Dashboard ([#31969][]) [#6367]: https://bugs.torproject.org/6367 [#30009]: https://bugs.torproject.org/30009 [#30020]: https://bugs.torproject.org/30020 [#31232]: https://bugs.torproject.org/31232 [#31686]: https://bugs.torproject.org/31686 [#31700]: https://bugs.torproject.org/31700 [#31718]: https://bugs.torproject.org/31718 [#31610]: https://bugs.torproject.org/31610 [#31805]: https://bugs.torproject.org/31805 [#31916]: https://bugs.torproject.org/31916 [#31969]: https://bugs.torproject.org/31969 ## weasel * Started with new onionoo hosts. Currently there's just one backend on fsn, irl is doing the service part (cf. #31659) * puppet cleanup: nameserver/hoster info * new static master on fsn * staticsync and bacula puppet cleanups/major-rework/syncs with debian * new fsn web frontends. only one is currently rotated * retire togashii, started retiring saxatile * moved windows VM away from textile * random updates/reboots/fixes * upgraded polyanthum to Debian 10 ## Hiro * Setup dip so that it can be easily rebased with debian upstream * Migrated gettor from getulum to gettor-01 * Random upgrades and reboots * Moving all my services to ansible or packages (no ad - hoc configuration): - Gettor can be deployed and updated via ansible - Survey should be deployed and updated via ansible - Gitlab (dip) is already on ansible - Schleuder should be maintained via packages * Nagios checks for gettor ## ln5 Didn't do much. :( ## qbi Didn't do volunteering due to private stuff # What we're up to next ## anarcat New: * LDAP sudo transition ([#6367][]) * jabber service shutdown ([#31700][]) * considering unattended-upgrades or at least automated needrestart deployment ([#31957][]) * followup on the various ops report card things ([#30881][]) * maybe deploy puppetboard as a Puppet Dashboard ([#31969][]), possibly moving puppetdb to a separate machine * nbg1/prometheus stability issues, ipsec seems to be the problem ([#31916][]) Continuing/stalled: * director replacement ([#31786][]) * taking a break on hiera refactoring ([#30020][]) * send root@ emails to RT ([#31242][]) * followup with email services improvements ([#30608][]) * continue prometheus module merges * followup on SVN decomissionning ([#17202][]) [#17202]: https://bugs.torproject.org/17202 [#30608]: https://bugs.torproject.org/30608 [#30881]: https://bugs.torproject.org/30881 [#31242]: https://bugs.torproject.org/31242 [#31232]: https://bugs.torproject.org/31232 [#31786]: https://bugs.torproject.org/31786 ## weasel * more VMs should move to gnt-fsn * more VMs should be upgraded * maybe get some of the pg config fu from dsa-puppet since the 3rd party pg module sucks ## Hiro * Nagios checks for bridgedb * decommissioning getulum * ansible recipe to manage survey.tp.o * dev portal coding in lektor * finishing moving gettor to gettor-01 includes gettor-web via lektor * do usual updates and rebots ## ln5 Nextcloud migration. # Other discussions ## configuration management systems We discussed the question of the "double tools problem" that seems to be coming up with the configuration management system: most systems are managed with Puppet, but some services are deployed with Puppet. It was argued it might be preferable to use Puppet everywhere to ease onboarding, since it would be one less tool to learn. But that might require giving people root, or managing services ourselves, which is currently out of the question. So it was agreed it's better to have services managed with ansible than not managed at all... # Next meeting We're changing the time because 1400UTC would be too early for anarcat because of daylight savings. We're pushing to 1500UTC, which is 1600CET and 1000EST. # Metrics of the month Access and transfer rates are an average over the last 15 days. * hosts in Puppet: 79, LDAP: 82, Prometheus exporters: 106 * number of apache servers monitored: 26, hits per second: 177 * number of self-hosted nameservers: 4, mail servers: 10 * pending upgrades: 0, reboots: 0 * average load: 0.51, memory available: 318.82 GiB/871.81 GiB, running processes: 379 * bytes sent: 134.28 MB/s, received: 94.38 MB/s Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 7 days, and wait a while for results to render. Note that the retention period of the Prometheus server has been reduced from 30 to 15 days to address stability issues with the server (ticket #31916), so far without luck. -- Antoine Beaupré torproject.org system administration

1 0

Tor Browser Release Meeting this week: Wednesday 9th October @ 18UTC
by Pili Guerra 07 Oct '19

07 Oct '19

Hi everyone, We’ll be having our usual Tor Browser Release meeting this Wednesday 9th October @ 18UTC on #tor-meeting. We’ll be discussing the upcoming 9.0 stable release and this will be the very last chance to request any small additions. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

S27 Meeting: Tuesday 8th October @ 16UTC
by Pili Guerra 07 Oct '19

07 Oct '19

Hi everyone, We’ll be having an un-scheduled meeting to discuss S27 and in particular Objective 2, Activity 1: Integrating client-side authorization to onion services v3[1]. The main agenda topic will be how to resolve incompatibilities between Tor Proposal 309: Optimistic SOCKS[2] and Tor Proposal 304: Extending SOCKS5 Onion Service Error Codes[3]. This meeting will take place 1hour later than usual at 1600UTC. Please join us if you think you have some input you can give to help us figure this one out. Thanks! Pili [1] https://trac.torproject.org/projects/tor/ticket/30000 <https://trac.torproject.org/projects/tor/ticket/30000> [2] https://gitweb.torproject.org/torspec.git/tree/proposals/309-optimistic-soc… <https://gitweb.torproject.org/torspec.git/tree/proposals/309-optimistic-soc…> [3] https://gitweb.torproject.org/torspec.git/tree/proposals/304-socks5-extendi… <https://gitweb.torproject.org/torspec.git/tree/proposals/304-socks5-extendi…> — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

[meeting] Sponsor 30: Empowering Communities in the Global South to Bypass Censorship
by Gaba 04 Oct '19

04 Oct '19

Hi! On Monday October 7th at 15UTC we will meet in #tor-meeting in irc to coordinate work on the project "Empowering Communities in the Global South to Bypass Censorship" [0] cheers, gaba [0]https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Notes from Vegas Meeting OCTOBER 3 2019
by Erin Wyatt 04 Oct '19

04 Oct '19

Notes from Vegas Meeting OCTOBER 3 2019 ITEMS DISCUSSED: + Gaba • - Topics for Tor at Mozilla All Hands are being written down in a pad to be submitted ASAP. • * Discussion: We need to strategize on who we send and what we want to accomplish to make the most of the opportunity; priorities: browser and scalability people, and someone who can tie it all together. + Georg - Blog: a) Where are we with fixing our blog comment issue? b) A gentle reminder: please deal with the comments of your respective blog post. If you think comments should not get published, please remove them as this gets them out of the approval queue and it helps others dealing with comments via https://blog.torproject.org/admin/content/comment/approval. If you think you can't handle the comments yourself, please find someone in your team or somewhere else who can or close comments on the blog post otherwise. We have established a policy regarding comments on our blog a while back which can be found at: https://trac.torproject.org/projects/tor/wiki/doc/community/blog-comment-po…. * Discussion: Our blog hosting company increased our bill to ~$800/month (from ~$280) because of increased traffic, people will discuss outside this meeting on how to address the issue. + Pili - What is our policy on people printing Tor swag for themselves, their friends, etc...? i.e. not to make a profit or sell. We have different opinions from different people. * Discussion: We should agree on a policy; for now Isa will talk to Jon about when to send cease/desist letters. --------------->8 --------------->8 ———————>8 GENERAL NOTES: Steph 1) Press inquiries. 2) Community portal reviews. 3) Newsletter out this week. 4) Sent initial task to prospective Outreachy interns and getting them started. 5) Preparing for EOY campaign. 6) Signed us on to a letter to end Amazon Ring-police surveillance partnerships Philipp 1) Determined ten winners for our bridge campaign. We're counting 95 new bridges so far. 2) Snowflake made it into the most recent Tor Browser alpha for Windows 3) Progress on BridgeDB (updated requirements, prototype of language switcher, updated translations 4) Progress on obfs4 (polished flow obfuscator) Georg 1) The second Tor Browser alpha version based on Firefox 68 ESR got out (including snowflake support for Windows, the latest Tor alpha, x86_64 support for Android and other neat things) 2) 20 days left to Tor Browser 9.0 and a ton of work to do :) 3) Work on the OTF proposal for ESR migration Nick 1) 0.4.2.2-alpha comes out in the next couple of working days. This should fix all the known release-blockers; remaining issues are should-fix, not must-fix. 2) Working on team policy proposals. We adopted a meta-policy for deciding whether to adopt team policies: see https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/MetaPol… in case you want to use it too. 3) Hoping to open 0.4.3.x early, if we can make enough progress on 042-should issues. Alex: 1) Had 1:1 with everybody from the network-team by now together with gaba and will continue from now on with just me and the team member. 2) Work on 0.4.2 and S29 tasks. 3) Continuing with the Gitlab migration work together with a lot of people from different teams. Erin 1) Working on handbook clarifications 2) General HR stuff Gus 1) Getting in touch with Outreachy applicants. If you see someone asking on IRC about more information, point them to this wiki page: https://trac.torproject.org/projects/tor/wiki/Outreachy 2) Sponsor9: partners are signing the Partnership Agreement. We have some training in Global South in 2 weeks. 3) Answering Frontdesk/RT. 4) Working on Community (training resources) and Support portal content (old FAQ migration). 5) Submitted Freedom not fear travel allowance 6) Pili and brabo are organizing our activities in FOSDEM, help them. Please, update this wiki page: https://trac.torproject.org/projects/tor/wiki/org/meetings/2020Brussels 7) We should somehow formalize our process for now to submit people's about/people page to www folks. 8) CCC: are we going to organize activities there this year? Matt 1) Continuing dev work 2) Continuing roles/responsibility transition Mike 1) Firefox esr networking code review Roger 0) Steph, let's be sure not to drop the "connecting EFF to relay operator who might need legal advice" thread. Let me know how I can help there. [in motion -steph] 1) Pili, where are we on the trademark swag policy discussion? I saw a thread with Jon. 2) I heard a rumor we might be scheduling the next in-person dev meeting for February. We should start collecting date conflicts asap, and start a preliminary invite list, in order to send out save-the-dates asap. 3) Fyi, the network health team is bumping out a pile of obsolete relays real soon now. Pili 1) Helping out with OTF Browser proposal 2) Replying to Outreachy applicants 3) S27 report 4) Organising for FOSDEM 5) October roadmap reviews 6) Starting to think about the developer portal sitemap and information architecture with Antonela Arturo 1) Moving forward with OONI Probe Desktop and CLI apps 2) Deploying fastpath for near realtime publication of OONI measurements: https://github.com/ooni/pipeline/pull/213 & event detection engine: https://github.com/ooni/pipeline/pull/228 3) Working on Oonifying our probe services, see: https://github.com/ooni/sysadmin/issues/359 & cleaning up our infrastructure to ensure things are redeployable: https://github.com/ooni/sysadmin/issues/356 4) Published a post on blocking in media websites in Egypt: https://ooni.org/post/2019-egypt-blocks-bbc-and-alhurra/ 5) Hacktoberfest! https://twitter.com/OpenObservatory/status/1179033711557263361 6) Working towards releasing OONI Probe mobile 2.2 and ensuring all strings are translated Antonela 1) September end of the month duties 2) TB9 Release: UX improvements: new identity, network settings, dark theme support, onboarding update. 3) EOY: Working with Alon on the art 4) WWW: some progress on the tickets with my name isabela 1) Presented at Semcomp22 at USP São Carlos/Brazil 2) Working on YE campaign stuff that Sarah needs from me 3) Editing Major Donors folder text and selecting different metrics we could use for a visualization to go w/ the folder 4) catching up w/ email backlog 5) helping out with OTF Browser proposal Sarah 1) EOY campaign planning 2) Helping with OTF proposal 3) Updating major donors with latest vision 4) Planning Boston get together 5) Sourcing new foundation/grant funding Antoine 1) continued coordination on retirement of old services and machines 2) more puppet training, brought up the idea of using puppet for hosting services too instead of forcing people to use ansible 3) announced LDAP password change 4) started experimenting with more "standard" (as in: packaged in debian) tools different things in Puppet and debian (needrestart, trocla, etc) 5) dealt with much maintenance churn (disk space issue, security upgrades, reboots, etc), trying to automate Gaba 1) Tor/Mozilla meeting is next October 8th. Topics: https://pad.riseup.net/p/DYCTCA7mcI1bqS5B9RfR 2) Sponsor 30 preparation for next weeks's meeting 3) Catching up with trac tickets 4) A few 1:1:1s this week 5) Gitlab migration (right now the blocker is how we resolve registration for users and resolve moderation and spam) 6) Other random stuff

1 0

Network Team Meeting Notes, 2 October 2019
by Alexander Færøy 03 Oct '19

03 Oct '19

Hello, Here is a short summary of the network team meeting from yesterday: 1) We went over our Kanban board to ensure that it is up-to-date. We forgot to look at weekly review distribution. 2) We looked at 0.4.2 ticket status. It looks like most people are currently focused on 0.4.2 tickets. We should ensure in the future that we have space in our schedule for doing release tickets around the time of feature freeze. Some tickets were distributed around amongst the team members. Priority should be on the 042-must tickets for now. Once all 042-must tickets are done, Nick said he is happy to open up for the 043 merge window ahead of schedule. 3) During the network team retrospective meeting that happened Tuesday, the team agreed to move forward with a subset of the PR policy that have recently been discussed at some of the network team meetings. Alex is doing the work to turn this into a policy we can vote on. 4) Nick asked some questions about an upcoming poll about C coding style in tor.git. The poll is going to be sent out to the team soon. 5) We discussed the currently active proposal discussions that are happening on the internal network-team mailing list: The policies discussed: 1. "Opting-in to faster reviews and merges". 2. "Commit Bits For CI And Review Roles". 3. "Draft merge policy for discussion and vote". The discussion on these items will continue on the network-team mailing list and during upcoming meetings. 6) Alex asked a question on what we should do with these policies that we are now discussing in terms of announcing them to the rest of the organisation since a lot of the debate around them is happening on the internal network team mailing list. We decided that Alex puts these items onto the pad we are going to use for doing monthly network team reports to tor-project(a)lists.torproject.org. 7) Nobody had anything else to talk about so the meeting was over. Please remember that our next meeting is on Monday the 7th of October at 17:00 UTC. --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-02-22.59.html Below are the contents of our meeting pad: gaba: (updated on september 30th) Last week (actual): . s30 . s31 . 1:1:1s . get up to date with trac tickets This week (planned): . s30 coordination with all teams involved . roadmap update (bring october tickets) Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 23 September (planned): Take Time for: - gitlab signup / config - team policies: - faster reviews - commit bit and roles? - finish add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - split off bugs I found while writing the control trace code Roadmap: - Sponsor 31 outstanding bugs / tasks - Sponsor 31 possible coding tasks for me - follow up email Other: - finish off bug smash logging bugs Week of 23 September (actual): Take Time for: - gitlab signup / config - team policies: - faster reviews - commit bit and roles - kept working on add tor controller trace logging to diagnose stem hangs (#30901) - split off bugs I found while writing the control trace code - did some preparation work Roadmap: - Sponsor 27 - Add IPv6 HSv3 chutney tests to CI - Sponsor 31 reviews - Sponsor 31 modularisation: disable relay mode when compiling - Initial design and strategy to move forward - Preparation work - speed up CI Other: - Finish off bug smash logging bugs - Quick bug fixes x3 Week of 30 September (planned): Take Time for: - team policy discussions - meetings x3 Roadmap: - add tor controller trace logging to diagnose stem hangs (#30901) - try nickm's suggested a simpler implementation - Sponsor 31 modularisation: disable relay mode when compiling - First cut: disable DirCache, DirPort, ORPort, and sets --disable-module-dirauth - If I stall on coding, finish sponsor 31 documentation that's assigned to me Other: - Reviews and revisions - Check CI & backports Week of 30 September (actual): Urgent: - Take Time for: - team policy discussions - meetings x3 Roadmap: - Sponsor 31 config refactor - control trace logging #30901 - preparation work - fix conflicting bugs - started work - Sponsor 31 modularisation: disable relay mode when compiling #31851 - Initial design and strategy to move forward - Preparation work - speed up CI Other: - Revisions - Check CI & backports - Quick bug fixes x2 - tor-relays moderation Nick: Week of 23 September (planned): - Keep an eye on blog comments - Finish edding circuit-padding document - Start a C style poll for the team - Meet about sponsor 31 on tuesday - attend ED tea time later Monday - Respond if needed to expected reviews on paper with Ian and Chelsea - Work on 042-must/should items - Review and merge Week of 23 September (actual): - Response to review feedback on paper with Ian and Chelsea - Handle blog spam on Tor posts - Reviews and merges - Sponsor-31 meeting - 31372: use "make -k" on CI - 31759: Improve "annotate_ifdef_directives" - 31849: move tor-guts into tor. Week of 30 September (planned): - One more PETS review. - Work on 042-must/should items - Start on another alpha, if all the -must items are done? - Kick off a C style poll - More review and feedback on pending refactoring - Review and merge stuff - Finish circuit-padding editing Mike: Week of 9/23 (planned): - Research discussion - Work with Nick to clean up final XXX's in circpad doc and merge/cite the quickstart guide - Cloudflare bot fight? - Maybe have time to start on Firefox review? <-- gaba: please or let pili know that you can't do it this week --> Week of 9/23 (actual): - Research discussion + emails - Wrapped up circpad doc (for now) - Wrote plan for circpad simulator (https://trac.torproject.org/projects/tor/ticket/31788#comment:2) - Attempted #31653; ran into unit test issues and also libevent perf issues - Started Firefox networking review (probably 75% done) Week of 10/02 (planned): - Finish Firefox networking review - Check in with Tobias re circpad perf issues and simulator plan - Perhaps update circpad doc with perf notes Need help with/at risk of dropping this month: <-- do you still need help with this? - Not doing any code reviews this month, unless on circpad patches. Got enough for Tor Browser - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) - Relay community drive/mgmt (and related LTS herding) catalyst: week of 09/23 (2019-W39) (planned): - reviews - provide feedback about C style - more feedback to review guidelines thread as needed - more feedback re gitlab migration as needed - check in with swati on Summer of Docs project - #30984 week of 09/23 (2019-W39) (actual): - reviews - chatted with some people re PR review guidelines - reviewed some policy proposals - wrote some feedback about C style week of 09/30 (2019-W40) (planned): - reviews - #30984 - review policy proposals asn: Week of 23/09 (planned): - Figure out how to do key blinding in onionbalance. - Forward progress in #31369 now that atagar has given me feedback Week of 23/09 (actual): - Significant progress on OB key blinding (#31777). - Continue work on stem descriptor encoding (#31823). - Started thread to discuss onion service errors and how they should be handled: https://lists.torproject.org/pipermail/tor-dev/2019-September/014046.html - Wrote documentation for client auth: #28966 Week of 02/10 (planned): - Bring OB hsv3 descriptor encoding closer to completion. - Attend s27 meeting about error passing over SOCKS vs HTTP vs control port - Handle remaining 042 bugfixes. ahf: Week of 23rd of September (planned): - Do first round of 1:1:1 with Gaba and other people on the team. - Work on #31810 - Continue to work on #28930 - Friday is Gitlab day where I will continue with the migration project. Week of 23rd of September (actually): - Did first rounds of 1:1:1 with Gaba. - Productive Gitlab meeting with people from different teams. - Proposed patches for #31091 and #31810 Week of 30. September (planned): - Finish 0.4.2 tickets - Get back to S29 tickets - Work on migration scripts for Gitlab transition. - Take the good parts of our PR policy discussion and turn into a policy. - Network team retrospective. dgoulet (offline): Week of 02/10 (planned): - Go through my 042 tickets. - Assess s27 situation and timeline and prioritize work that need to happen soon. - Attend s27 meeting about the SOCKS error situation. - Bad relay world. swati (offline): Week of 02/10: - Registered and created an account for myself on trac. - Created a ticket https://trac.torproject.org/projects/tor/ticket/31943 for reviewing changes in the tor Manual. - Forked the tor repository and cloned the copy of the repository to my local filesystem - Pushed changes to the local repository and created a pull request. - The pull request is https://github.com/torproject/tor/pull/1391. - Can someone assign reviewers for this pull request? I don't seem to have write access for this repository. All the best, Alex. -- Alexander Færøy

1 0

Metrics team meeting notes, 3 Oct 2019
by Gaba 03 Oct '19

03 Oct '19

Meeting Log: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-03-15.01.html Meeting pad's content: Next meeting is on October 14th at 15UTC * Debian Buster and Java 11 (irl) karsten looks into #31953 and #31952 on Friday, and if he doesn't succeed, irl takes over next week * AWS + CloudFormation (irl) karsten tries out lightsail next time he creates an EC2 instance * Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0