- tor-project - lists.torproject.org

Network health meeting notes, 23 Mar 2020
by Georg Koppen 24 Mar '20

24 Mar '20

Hello! We had another round of our weekly network-health meeting yesterday in #tor-meeting. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-23-18.59.log… The items from our pad (both discussion and status related) can be found below: Discussion: -meeting moves to 1800UTC next week (so everyone should have it at their usual local time)? [GeKo: yes. announcement got sent to networ-health list] - docshackathon this week. Do we need to update documentation about relays? Improvements? - DoS Prevention / PrivacyPass and Co / Onion Services (dj) [GeKo: yes, we think about participating] Statuses: GeKo: Last week: -more sbws work (I did not finish my work on #33009, but started to review closely #30905) -fixed #32864 -usual bad relay work -looked at our checktest doctor test (#33683) -started to look at another round of seemingly random resource load failures caused by Cloudflare (as part of #33466) -ggus: do we have some list of relay operators who run more than X% of the network and what kind of contacts we have to them? [GeKo: ggus asks sarah what the fundraising folks use and could find useful and we take it from there] This week -sbws work (mainly reviewing #30905 and hopefully fixing #33009) -more work on issues encountered with our bad relay scanners -more work on exit relay blocking problem (#33500 etc.) juga (offline): Last week: - Continued with child of #30719: #30905 (change state values when sbws is restarted) - Had irc meeting with GeKo and ahf together, we decided: - my minor (not bugfixes) changes for #30905 are ok, in the sense they are not just bugfixes, but with the current code it's all can be done (yet a lot of work). Still pending review. - we'll start to do reviews in gitlab.tpo, as soon as gaba creates the gitlab "canonical" sbws project. Next week: - Revisions on #30719 - Continue with #30735 Gus: This week: - Doing docshackathon this week. Do we need to update documentation about relays? Improvements? Gaba: This week: not doing anything related to the network health team. Georg

1 0

Notes from Vegas Meeting MARCH 19 2020
by Erin Wyatt 23 Mar '20

23 Mar '20

Vegas Team Meeting Notes March 19 2020: NEW BUSINESS + Sarah - We are looking at platforms and are leaning toward using Zoom for the upcoming webinars. We need something that is cheap (or free!), can handle 50 people, allows for screen sharing and recording, has a way for participants to ask questions. Suggestion: Jitsi? Maybe not because there is a thread in infrared from mayfirst and others; seems not to scale to more than 20 ppl --gaba] + isabela -> what are the pain points on vegas leads meetings so we can start thinking on how to address them and improve this meeting? - Long discussions about topics that only concern a few people - Discussion items need to be in the pad *at least 24 hours ahead of time*, ideally sooner; general notes can be last-minute - Maybe we can move to voice, or have a mix of voice- and text-based meetings; voice would require more attention to keeping minutes; Isa and Charly will be building a plan for meetings going forward. GENERAL NOTES GeKo: 1. network health work 2. Steph: Did you get my mail regarding the onion service education coordination? [yes, I did. Thanks for the reminder. things have been hectic -steph] 3. Working on licensing/copyright situation for TPI employees Sarah: 1. Working on webinar for next Thursday. We are looking at platforms and are leaning toward using Zoom. We need something that is cheap (or free!), can handle 50 people, allows for screen sharing and recording, has a way for participants to ask questions. 2. Had productive meetings this week with Internet Society Foundation and Omidyar. We will be submitting proposals to both. 3. Received notice that the browser OTF proposal has been accepted. We are now moving onto the contract phase. NICE! 4. Decided to hold off on a spring appeal to individuals. Nick: 1. new releases came out, including security fix. Seriously, everybody should upgrade. No sign of anybody using the attack yet (as of 0000 UTC on 19 Mar) 2. A few of us had our first mayfirst-hosted online meeting on Tuesday : it went 4 hours, with 10-15 minute breaks every hour. asn and dgoulet facilitated. Ask us what worked! Anarcat: 1. published two technical articles on my personal blog https://anarc.at/blog/2020-03-17-git-gpg-verification/ https://anarc.at/blog/2020-03-15-remote-tools/ 2. finished migrating 3 more VMs: cupani, polyanthum, omeiense, automation is starting to pay off 3. that allowed retiring second old libvirt/KVM server (unifolium), 2/5 done! 4. ordered a new ganeti server which i'll setup soon, fsn-node-05, to continue the Great Migration 5. routine stuff isabela: 1. Working on webinar deck for next week and other details related to March 26 event 2. Meetings w/ foundations Internet Society, Omydiar 3. Prepaing as much as possible to all the changes and implications regarding covid-19 and trying to give support to Tor folks and our community 4. onboarding Charly! 5. what are the pain points on vegas leads meetings? so we can start thinking on how to address them and improve this meeting gus: 1. Next week we will have Documentation Hackathon. People will join us on IRC and ask questions, please send them to #tor-www or to this blog post - https://blog.torproject.org/docshackathon-2020 2. Engaging with Outreachies applicants - Project 1 - 'Help Tor support our users'. 3. CryptoRave is postponed due Covid-19 Steph: 1. Working on a blog post about remote work habits and quarantine privacy situations. Helped with onionbalance & docshackathon posts 2. Will still be submitting to def con for a booth 3. Working with OTF learning lab on onion services 4. Preparing for webinar next week 5. Responding to press inquiries 6. Social media Gaba 1. s55 tracking 2. reading on walking onion project updates from nick 3. DoS defenses meeting. 4. sent mail to some of the sponsors on c19 5. a bunch of ther small stuff Antonela 1. Regular sponsor work, S27, S30 2. Working on a git proposal for design iterations in gitlab.torproject.org/torproject/ux/design 3. S9 planning remote user research for onion services and bridges, working with nah on it 4. Planning Monthly Hall Demos Pili 1. S9 regular sync 2. Tor Browser Release meeting 3. Helping Outreachy and GSoC applicants 4. Starting to wrap up S27 and figuring out what we're going to release when 5. Looking at gitlab projects again and organising them 6. S58 set up: creating trac page, tagging tickets, etc... - https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 Matt: 1. New Tor Browser releases at the end of this week/early next week 2. Lots of distractions, but concentrating as best I can Alex: 1. Team seems to be doing OK. 2. Low on concentration. 3. Some infrastructure issues this week that David helped me solve. 4. Technical work this week is in security stuff, windows problems Erin: 1. Onboarding Charly (yay!) 2. Personnel/HR stuff 3. Still a little behind on some things 4. Trying to stay focused and optimistic Mike: 1. HS DoS meeting 2. Writing peer reviews Karsten: 1. Getting up to speed with Matplotlib as first step to tweaking graphs produced by OnionPerf's visualize mode. 2. Started tracking time at a granularity of 0.1 points for better reports and future estimates. Philipp: 1. Mostly caught up from vacation. S28/S30 business as usual 2. Trying to pay more attention to volunteer work that accumulated over the last weeks

1 0

Anti-censorship meeting notes, 19 Mar 2020
by Philipp Winter 20 Mar '20

20 Mar '20

Hi friends, Here is our meeting summary: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-19-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday March 19th 18:00 UTC Weekly meetings, every Thursday at 18:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: https://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * Next planning session: last week of April * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meetings' notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- March 19th 2020 -- ------------------------- == Announcements == * == Discussion == * Let's talk about the next steps to get snowflake to an "MVP" so it can be useful to users. * When is it a good time to blog about what we've been up to wrt snowflake? Before/after the TurboTunnel merge? * How about every two weeks, we pick a project or a paper and discuss it, reading group-style? * We could talk about it during our IRC meetings or over at https://github.com/net4people/bbs/issues * Ideally, we would exchange ideas about the benefits/issues of a project; how Tor could benefit from it; etc. * The goal is for us to stay up to date on recent developments and learn from each other. == Actions == * == Interesting links == * == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. phw: This week (2020-03-19): * Wrote February 2020 report * https://lists.torproject.org/pipermail/tor-project/2020-March/002774.html * Identified and contacted bridges that run soon-to-be-obsolete Tor versions * https://trac.torproject.org/projects/tor/ticket/32672#comment:42 * Added a bunch of new papers to CensorBib * Some catching up on Sponsor 28 emails * Reviewed several docker, GetTor, and BridgeDB patches * Tried to figure out if #33464 really is a problem (it isn't) * Addressed remaining feedback for #33008, merged, and deployed * Filed #33630 to get noisebridge01 removed from list of default bridges * It's been unmaintained for a looong time * Realised that BridgeDB doesn't let bridges *change* their distribution mechanism and filed #33631 to get it fixed * ...the fix is more invasive than I thought, though * More coordination on our monitoring infrastructure (#31159) * Our sysmon instance was broken, resulting in us not knowing that our UMN default bridge was down :( * Spent way too much time trying to figure out why BridgeDB's overly complicated installation procedure is now broken * ...still not clear :( Next week: * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones * Pay attention to volunteer work (help agix with BridgeDB reviews; thymbahutymba with docker; Sergey with https proxy) * Make BridgeDB report internal metrics (#31422) * Catch up on RACE; in particular wrt obfs4 improvements Help with: * Gaba: () Last week (2020-03-12): * not much related to anti-censorship This week (planned): * not much related to anti-censorship cecylia (cohosh): last updated 2020-03-19 Last week: - finished Tor browser patch to update pion (#33576) - Revise GetTor help (and links) message (#23226) - removed server-webrtc (#33636) - final edit passes for NSF grant - worked on a Snowflake package for Debian (#19409) - helping with update of obfs4proxy debian package - remove server-webrtc from snowflake repo (#33636) - reviews of #33008, #33638 - talked with alwayslivid about telegram bot for GetTor (#22011) - prepared for potential snowflake repo split (#33593) This week: - maybe continue work on throughput check (#32938) - make a Snowflake package for debian (#19409) - Resume obfs4 and snowflake tests (#31701, #32657, and #32545) - look at options for getting STUN information to snowflake clients (#25591) - make sure obfs4proxy debian package gets updated - take a look at reviving the twitter responder in GetTor (#33036) Needs help with: - Update Snowflake license (#33637) - Review of GetTor help/links message update (#23226) - Decision and review of snowflake repo split (#33593) arlolra: 2020-03-19 Last week: - some snowflake refactoring (#33638) and review - #33665 Next week: - maybe the proxy parts of #19026 - start on #31201 Help with: - dcf: 2020-03-19 Last week: - reviewed snowflake proxy throughput tests (#32938) - filed a ticket for a needed security upgrade for the snowflake bridge (#33644) - let snowflake-turbotunnel handle simultaneous SOCKS connections (#33519) Next week: - announce snowflake-turbotunnel Tor Browser packages with 9.5a8 - file ticket for snowflake-turbotunnel merge - share access to the snowflake broker CDN configuration (#30510) Help with: cjb: 2020-03-19 Last week: - gonna be afk with kids Next week: Help with: agix:2020-03-19 Last week: - Opened #33647 (Minor updates to BridgeDB's dependencies) - Worked on the GSoC proposal - Fixed broken patch for #31967 Next week: - Continue on #31967 and #31426 Help with: - catalyst: 2020-03-19 last week: - did some s28/s30 prioritization with ahf - helped cohosh with some Debian packaging related things this week: - work on some s28/30 tickets, e.g., #5304 thymbahutymba: 2020-03-12 Last week: - docker-compose for obfs4-bridge (#31834) - multiarch docker obfs4 images #33461 (even though is more then a week ago) - reported issue concerning #31834 (comment 25) Next week: Help with: Hiro: (last updated before 2020-01-09) Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation

1 0

Sponsor 38 update (Shadow simulator)
by Jim Newsome 19 Mar '20

19 Mar '20

Project management: * We’ve filled in a more granular plan in the _Sponsor 38_ <https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor38>page. We’ve made some progress on _Shadow_ <https://github.com/shadow/shadow>’s milestone _Improve development assurance and velocity_ <https://github.com/shadow/shadow/milestone/15>. Notably: * Fixed remaining compiler warnings in our continuous-integration environments, and enabled -Werror there. _[#726_ <https://github.com/shadow/shadow/issues/711>] * Added continuous integration for shadow-plugin-tor, testing each pull request of shadow-plugin-tor against stable versions of shadow and Tor [_#85_ <https://github.com/shadow/shadow-plugin-tor/pull/85>, _#86_ <https://github.com/shadow/shadow-plugin-tor/pull/86>, _#90_ <https://github.com/shadow/shadow-plugin-tor/pull/90>], and also run it for pull requests in the Shadow plugin against stable versions of shadow-plugin-tor and Tor [_#727_ <https://github.com/shadow/shadow/pull/727>] _v1.14.0_ <https://github.com/shadow/shadow/releases/tag/v1.14.0>of Shadow was released. In addition to the changes above, it modularizes the router queue management algorithm and makes CoDel the default algorithm. Our current focus is on prototyping Phantom: a new architecture for Shadow that will run applications in their own processes rather than using a custom ELF loader to load them directly into Shadow’s process. The new architecture will work with unmodified program binaries (rather than having to recompile them with -fPIC), should be stabler and easier to maintain, and may have performance benefits. Because Rob Jansen and Ryan Wails at NRL are actively involved in this development work, NRL regulations require that the active development happen in a private branch. When it’s ready to be upstreamed, they’ll go through an NRL release process and merge it into the public repo. In the meantime there is a place-holder issue [_#738_ <https://github.com/shadow/shadow/issues/738>] in the public repo. Recent progress on Shadow-Phantom: * Added ability to simultaneously support alternative “thread” strategies for controlling and communicating with plugins. * Working proof-of-concept of “Shim-Pipe” threads, which use LD_PRELOAD to interpose the libc API to call a version of the “syscall” function that communicates via Shadow using a pipe. * Nearly done with a shared-memory-based IPC mechanism for the Shim-Pipe, which will be used for syscall pointer arguments. * Working proof-of-concept of “Ptrace” threads, which use ptrace to attach to plugin threads, and intercept and service syscalls. This approach is expected to be a bit simpler (the tracing process can directly read and write the tracee’s memory, making marshalling easier) and more reliable (e.g. handle direct usage of the syscall instruction), but be less performant (likely more context switches between Shadow, the OS, and the plugin). In the coming month our main focus will continue to be on Shadow-Phantom. We intend to flesh out the functionality enough to start doing simple networking benchmarks, and if results look promising will continue to flesh it out enough to run Tor.

1 0

Metrics Meeting Notes, March 19th 2020
by Gaba 19 Mar '20

19 Mar '20

Hi! We had our weekly metrics team meeting today. The next one is going to be on March 26th at 1500 UTC. The pad for the meetings in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The agenda and notes for today (and last week) are here: ----------------------------------- Agenda Thursday, March 19th, 15 UTC ----------------------------------- Time tracking (karsten) 1.0 Update CDF-TTFB graph (#33256) 0.8 Add CSV file export of graphed data (#33258) 0.6 Improve logging for Exonerator (#24542) 0.5 Extend integration tests in metrics-test to also test Onionoo (no ticket) 0.3 Make all Descriptor implementors serializable (#33090) 0.2 Display a bridge's distribution bucket (#33008) 0.2 Fix deserialization of UTF-8 characters in details statuses and documents (#21933) 0.1 Document how we estimate users by transport by country (#29636) 0.4 Other more topics here Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-19-15.02.log… ----------------------------------- Agenda Thursday, March 12th, 15 UTC ----------------------------------- Time tracking (karsten) 0.6 Add directory authority bytes to dirbytes graph (#33065) 0.4 Cache-Control header on 404 does not permit caching (#32065) 0.8 Simplify logging configuration across code bases (#33549) 0.1 Configure embedded Jetties programmatically rather than using IoC (no ticket) 0.1 Extend descriptorCutOff in CollecTor's RelayDescriptorDownloader by 6 hours (#19828) 0.1 Find a working alternative to using MaxMind's GeoLite2 databases (#32978) 0.1 Investigate possible bug in m-web logs (no ticket) 0.1 Make all Descriptor implementors serializable (#33090) 0.1 Relay Search does not have an icon for StaleDesc (#33453) 0.1 Relay Search flags are vertical on Tor Browser 8.0.2 on macOS (#28317) 0.1 Relay Search should be able to handle non-numbers in "as:" parameter (#32683) 0.1 Send service change announcement for check/tordnsel (#33510) 0.0 Update instructions for enabling javascript when javascript is disabled (#31714) 0.0 Do not let appended descriptor files grow too large (#33502) 0.4 Other ExitScanner (add more topics) Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-12-15.00.log… -- 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 MARCH 12 2020
by Erin Wyatt 18 Mar '20

18 Mar '20

Vegas Team Meeting Notes March 12, 2020 Anarcat 1. hiro switched us over to the new gitlab server, and that fixed the bug yaaaay! 2. check.torproject.org service replaced, old chiwui will *finally* be decomissionned in april (#33536, #33362, #29399) 3. performed SVN access audit and cleanup (#33537) - what is sue's username? [delegated to gaba] 4. reviewed DoH article 5. had our monthly meeting on monday 6. started drafting a "tools" policy, to limit and document tools used in the team (e.g. "we use Debian and Python, not Arch Linux and Golang"), specifically introduced and demo' Fabric as a new tool to automate ad-hoc jobs 7. migrated git-rw/cupani to the ganeti cluster, the first major live service to migrate (#33586) 8. handled a minor security issue with Puppet certificate revocation (#33587) 9. routine work (puppet module upgrades, code reviews Steph 1. Coordinating/writing responses to press inquiries 2. Edited DoH blog post with Roger, Matt 3. Working with annalee_ on a vpn blog post 4. Participated in IWD on social media with a graphic by Anto 5. Making arrangements for alternate SF meetings 6. Working with OTF lab on onion services pages 7. Will submit to have a booth at DEFCON, starting initial swag/staff planning Gaba 1. S30 meeting and follow up 2. S55 meeting and follow up 3. Coordinating DoS defenses discussion. 4. Follow up on tor library size discussion 5. Follow up on svn access 6. Reading on outreachy to keep up with applicants 7. Soundtrack https://www.youtube.com/watch?v=EBRAhgvixTg Gus 1. Submitted Cleopatra's final feeback in Outreachy. 2. Starting to get contacted by new Outreachy contributors. 3. Moving forward with the next DocsHackathon. 4. New training material digital security for journalists ready for review. 5. Submitted all peer feedbacks and self feedback. 6. Re-organizing Community Team plans and working in a contingency plan. Georg: 1. network health work is moving forward 2. finished peer feedback 3. I spent a bunch of my weekend thinking about our organization-wide goals and how to break those down into actionable items on our roadmaps, and above all, where the current blockers are on making progress in that direction. We clearly want that flow but are not there yet. Alex: 1. Submitted peer feedback that was missing to Isa, late. 2. Virus is over DK and they have closed down some of the state, so keeping a bit track of what is going on there. Sarah's working from home now as well, which might mean that I will be working in more "normal 9-17" hours in DK and be less online in the evening. 3. Review of sbws and chutney work by juga and teor. Both projects seems to be going well. 4. Made a plan with Nick on some Windows and security items that I need to have ready for our upcoming release(s). 5. Network team folks had some feedback on the feedback process in the 1:1's. I'm keeping notes around on that and I guess we'll do some evaluation at some point? 6. My talk at University College Lillebaelt was cancelled because they dropped the conference, but I ended up doing a much long lecture just for the students in their network monitoring and security class. Was fun! 7. Behind on GSoC/Outreachy things I think. Mike: 1. Helped w/ final review of DRL 2. USENIX paper review 3. FlashFlow coordination 4. HS DoS planning + reading 5. Role discussions Antonela: 1. S30 work, OONI design tasks, user research and tor browser ft bridges. 2. Sent ux team report for february. 3. Working with diogosergio on setting up a workflow with git for design iterations. 4. emmapeel is working with fundraising on a MOSS grant to get ride of transifex with the linguine group. 5. We need a plan to ship onion names in stable. 6. Planning with nah remote user research as part of S9. 7. Reviewing the various OTF Learning Lab deliverables. 8. First meeting with Simply Secure for Metrics this friday. 9. Trying to make internal demos monthly call a thing.\o/ Sarah: 1. Converting SF EFF event into a virtual happy hour. 2. Bitcoin2020 is postponed to later in the year. 3. Plugging ahead on plans for NYC event April 13th and exploring virtual options. 4. Planning for fundraising appeal for walking onions. 5. Upcoming meetings with Omidyar and Internet Society Foundation. 6. Applied for booth at IGF in November. Pili: 1. Working on outstanding feedback 2. Done with OTF revisions 3. Answering GSoC and Outreachy queries 4. Finally sent Browser team february report 5. Need to think about how we move some projects forward given cancellations of face to face meetings. We might do an online mini hackweek for Community, UX and Websites team during the week we would have been at IFF with a number of online presentations and events. We're still figuring out the details 6. Docshackathon prep Nick: 1. I need to get stable releases out soon, but stuff is being a bit sluggish. Working on it. 2. DoS meeting has been moved from in-person to online; will happen next Tuesday as a pilot for future online team meeting-type stuff Philipp: 1. Back from vacation and trying to catch up. Please let me know if you want me to prioritise something! 2. In-person meetings at IETF 107 are cancelled, so won't be attending. May participate remotely in some sessions. 3. Tor talk in Austria is looking increasingly fragile given the current travelling situation. May do the talk remotely. 4. Submitted late peer feedback. isabela: 1. Second round of interviews 2. organizing onboarding for new ED assistant 3. finishing all proposals reviews 4. preparing to move virtual w/ donors and foundations events Matt: 1. Many Tor Browser releases 2. Helped answer questions for OTF proposal 3. Working on overdue peer reviews

1 0

Join Our Second Documentation Hackathon March 22-30
by gus 17 Mar '20

17 Mar '20

Hi, Between 22 and 30 March, the Tor Project will host the second edition of our user documentation hackathon, the DocsHackathon. The DocsHackathon is a totally remote and online event. If you've never volunteered with us before, this is an opportunity for you to become involved in the community, get closer to our work, and make meaningful contributions. During our first DocsHackathon last September, we had 70 registrations, 8 contributors, and over 70 pull requests to the support portal, Tor Browser manual, our main website, and other repositories. If you helped out last year, we hope you can join us again or help spread the word. Once the DocsHackathon is completed, we'll reward the top 3 contributors with official Tor swag. So if you're a copywriter, front-end dev, tester, or content reviewer, we'd appreciate your help improving our documentation, updating our support portal, and ensuring their relevancy. Don't feel like any of these apply to you but still want to help out? Chat with us on IRC (#tor-www - irc.oftc.net) or the community team mailing list to join us and find out where you could add value. Read more here: https://blog.torproject.org/docshackathon-2020 And here: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH… all the best, Gus -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/

1 0

Network health meeting notes, 16 Mar 2020
by Georg Koppen 17 Mar '20

17 Mar '20

Hello! Here comes the summary of our weekly network-health meeting we hold yesterday in #tor-meeting. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-16-18.59.log… The items from our pad (both discussion and status related) can be found below: Discussion ========== - strategy for moving #32672 forward (pinging relay ops on social media etc.) [GeKo: we decided to have two social media campaigns/pings: one now that the patch for that ticket got merged and one once it is about to reach a stable release. ggus is working on that. GeKo is talking to the network-team folks about a timeline for getting the patch backported] Statuses ======== GeKo: Last week: - more sbws work - #32864 (I wrote a script to parse the JSON output and contacted affected operators) - got back to EFF for the legal questions update - looked again at #33361 for review This week: - more #32864 (further testing and tweaking new script and bad-exiting first relays) - more sbws work (#33599, #33009) - start work on exit relay blocking problem by large websites/CDNs etc. (#33500 etc.) - start looking closer at bad relay scanners we have and issues that have accumulated (#33180, #33181) juga (probably offline): Last week: - Continued with child of #30719: #30905 (change state values when sbws is restarted) - Had voice meeting with GeKo and ahf (separately), we decided or commented: - to have regular meetings the 3 of us together (so nice to talk by voice!) - to report back in the network-health weekly meeting - migrate trac to gitlab.tpo soon, migrate remaining tickets in gh to gitalb.tpo, make reviews in gitlab.tpo - we will run longclaw bwauth with last maint-1.1 branch to be able to detect bugs before migrating all bwauths to sbws, since currently we don't have a way to test sbws as it'd run for several days and doing so would require quite more time - i'll make minor changes in #30905 (not just bugfixes) because i don't think there's currently a way to know when things happened storing only numbers - general overview and history of sbws (why things are like they are) Next week: - Continue with #30719 - Continue with #30735 gus: this week: - Tweet about 0.2.9 and 0.4.0 patch Georg

1 0

Tor Project is participating in GSoC and the next Outreachy (May to August 2020) round
by Pili Guerra 17 Mar '20

17 Mar '20

Hi everyone, You may have noticed that we have a lot of eager students showing up on irc these days looking for help to get started :) Both of these schemes are currently in the application/contribution periods, which run as follows: GSoC: February 20, 2020 to March 31, 2020 [1] Outreachy: March 5, 2020 to April 7, 2020 [2] During this period applicants are expected to get in contact with mentors to discuss the project and complete a series of tasks to demonstrate their skills. Please help them to feel welcome and direct them as follows if they are asking for help: 1. For GSoC, we have an ideas page[3] which lists the mentors for each project. They should direct their questions to the mentors and follow the “Getting Started” instructions in the project description. If the project does not currently have “Getting Started” tasks, please work with me to add some 2. For Outreachy, we have a wiki[4] which also lists the mentors for each project and a set of tasks to complete. If applicants are not clear on how to proceed or they need further help, please direct them to me or the project mentors. Thank you! Pili [1] https://summerofcode.withgoogle.com/how-it-works/#timeline <https://summerofcode.withgoogle.com/how-it-works/#timeline> [2] https://www.outreachy.org/docs/applicant/#outreachy-schedule <https://www.outreachy.org/docs/applicant/#outreachy-schedule> [3] https://community.torproject.org/gsoc/ <https://community.torproject.org/gsoc/> [4] https://trac.torproject.org/projects/tor/wiki/Outreachy#Projects <https://trac.torproject.org/projects/tor/wiki/Outreachy#Projects> — 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

WWW February 2020 report
by Hiro 16 Mar '20

16 Mar '20

Hi all, Here is what has happened in February in the Tor www world * We debugged errors in the build process for the websites. Now there are no more randomly broken builds and less resources are spend on jenkins. * Looking at lego documentation for giant rabbit: https://gitlab.dip.torproject.org/torproject/web/wiki/blob/master/lego.md * Updated template for creating a new website: https://gitlab.torproject.org/torproject/web/template * WWW contributing workflow: https://gitlab.torproject.org/torproject/web/wiki/blob/master/Our-Workflows… * Started planning to migrate the blog to a static website https://trac.torproject.org/projects/tor/ticket/33115 Meeting notes for February can be found: https://gitlab.torproject.org/torproject/web/www-meeting-notes/blob/master/… This summary and past and future ones can be accessed online: https://gitlab.torproject.org/torproject/web/www-monthly Please notice that we will not be using trac to collect new issues for the website but gitlab.torproject.org. You can log an issue here: https://gitlab.torproject.org/groups/torproject/web/-/issues Gitlab will ask you to chose a project. If unsure feel free to use tpo which is our main website www.torproject.org Thanks all! -hiro

1 0