- tor-project - lists.torproject.org

List announcement: tor-packagers@
by Damian Johnson 26 Nov '17

26 Nov '17

Hi all. I'm pleased to announce tor-packagers@, a list for our lovely tor packaging community... https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-packagers https://trac.torproject.org/projects/tor/wiki/doc/packages Care to get involved in packaging? Then please sign up! This is a moderated, low-traffic list for package maintainers to stay in the know about new releases, and for tor developers to pitch their project when they'd like to have help packaging. Cheers! -Damian

1 0

Weekly network team meeting notes (20 Nov 2017)
by Nick Mathewson 20 Nov '17

20 Nov '17

Hi, all! You can find the logs of our latest weekly meeting here: http://meetbot.debian.net/tor-meeting/2017/tor-meeting.2017-11-20-16.59.html Below are our notes: ============== Network team meeting pad, 20 November 2017 Welcome to our meeting! Every monday at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Meeting notes from last wek: * https://lists.torproject.org/pipermail/tor-project/2017-November/001568.html Announcements: - Remember, it's a US holiday on Thursday. Some US folks will be on limited availability Wednesday afternoon through Monday. - Sponsor M is no longer billable: please let me or isabela know if you need to do more work on M stuff, and we can work something out. - On the roadmap spreadsheet: Please start taking december/january tasks. (If somebody else has already taken something you want, please talk to them and/or add yourself too.) Discussion Topics: - 0.3.2 planning - Time allocations dgoulet: - Last week: * Various 032 tickets work (review and patches). * Finalized the hs v3 control port support (#20699). Missing some unit tests before ready for review. * Worked on TROVE-2017-012 * A bit of thinking on channel/scheduler problem especially how to better handle DESTROY cells. I've started writing a proposal (not finished). (https://lists.torproject.org/pipermail/tor-dev/2017-October/012536.html) - This week: * Making #20699 in needs_review. * As usual, ticket work on 032 milestone. * Tackle #23709 which is the removal of the in/out queues from channels. This will need much more unit tests than we currently have so I expect most of the work will be writing those and chasing down bugs. * Continue the "cell handling" proposal. Isabela: Last week: - working on proposals and reports (never ends) - sent Tor Launcher check in email - start to QA the new UI too :) - scheduled sync for HS UX tasks (which is schedule for wed) This week: - send out an earlier reminder to testers for Nov test (left for last moment the previous months :( - review where teams are on roadmap / state of deliverables - I have a big deadline on Dec 1st so I might be busy with that just FIY† asn Last week: - Progress with md (#21969) work. #23817 got merged! Might need a bit of a fixup still. Progress with #24113 and #23863 but need more work. - Reviewed #23100 some more, but got stuck with #23114. Will continue next week. - Wrote two UX improvement proposals for onions: https://lists.torproject.org/pipermail/tor-dev/2017-November/012595.html https://lists.torproject.org/pipermail/tor-dev/2017-November/012610.html - Opened master ticket for onion service DoS improvements: #24298. We got many requests to look into this but we didnt really do much, let's use that ticket to coordinate. - Wrote some things for our censorship circumvention position. This week: - Hopefully finalize #23817. - Attend UX+TB+network team meeting on Wednesday. - Take some personal time off. Mike (may miss part/all of meeting :/) Last week: -- Git juggled #23100 and #23114 into more reviewable shape. - Did some work on #23101 - Reviewed and discussed #23681 This week: - Maybe get #23101 working? komlo: (will be on IRC for the meeting ~15 minutes late) This week: - I want to have a patch for #23881 this week (adding logging support for rust) - One question about this: we use macros on the C side to wrap log_fn_ (such as log_warn), I'm not sure if we want to replicate this in Rust, or if we should instead create helper functions in C. - I was thinking about taking a first stap at #23891 (writing a blogpost about Rust) to get a long headstart and lots of feedback before the 0.3.3 release ahf: Last week: Sponsor 4: - Attended the OTF summit together with GeKo, Shari, and the OONI people. Some highlights: * Met with Hans from the Guardian Project and discussed a lot of Android tooling/problems I have had. * Met with two activists from Nigeria who gave me some insights in mobile usage in their country (focus country for Sponsor 8). We exchanged contact information to be able to stay in touch. * Conversations with the Briar people about what they could be interested in from Tor. Sponsor 8: - Tried out my `simpleperf` notes in a clean VM to ensure things worked. Misc: - Reviewed some small patches in #24167, #24097, and #20963. This week: Sponsor 8: - Talk with Nick about initial set of optimizations for bug #24062. - Get `simpleperf` document into the `doc/` tree of tor.git. - Begin optimization work. - Land my Android logging patch for #24362. - Look at Nathan's "split" Orbot work. [nickm: please let the rest of us know what you find.] [ahf: yes, will update the https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/Sponsor8 page for it] - Finish automated build's of Orbot-with-tor-master to an fdroid repository and find people who are interested in testing it out (maybe some people from the network team are up for that?) Nick: - Last week: - Worked on separating key/cache directory for limited disk users. - Hunted/triaged bugs in 0.3.2 milestone. Fixed some - Solicited review on 24107, 24204 APIs (hibernation and communication for mobile) - Started work on making tor restartable in-process (#23847), which led to #24337 (make all the X_free()s into macros that NULL their targets). Is that a good idea? - Dove into glibc 2.26 and how to make it play nice with libseccomp2. - Backported various fixes. - Updated UTF-8 proposal - Reviewed David's channels thread. - This week: - Release 0.3.2.5-alpha (on Tuesday or Wednesday!) - Ahf, do you have time to talk about prioritizing the optimizations to be made for mobile? [ahf] Yes! Let's do it early in the week? - Taylor, would you like to talk more about bootstrapping some time? I can make time tonight or tomorrow or maybe even another day. [catalyst: yes! tomorrow probably works] - Try to finalize fixes for TROVE-2017-{009,010,011} [dgoulet] TROVE-2017-12 as well :) [nickm] I'm hoping you'll finialize it :) (On the mailing list) (will look) - Try android performance/developer tools recommended by ahf - Fix or defer remaining consensus-diff tickets in 0.3.2.x - Analyze severity of HS descriptor hashring failures corresponding to missing ed25519 identities. - Continue work on #23847 (restartable in-process tor). - Time permitting, start groundwork on making Tor wake up less often. - Open review-group-26, if we finish review-group-25 (hint, hint) - Time permitting, write a logv variant for komlo to use in rust for 23881. catalyst: Last week (2017-W46): - tried to make more progress on bootstrapping stuff; useful talk with nickm - TB auto-update did some weird things (#23968 is back) - useful chat with Sebatian and others on IRC about expectations about LOG_NOTICE messages and how comprehensible they should be to relay ops. we should clarify these expectations and document in easier-to-find places This week (2017-W47): - talk more with nickm about bootstrapping stuff - investigate the cold cache guard state initialization stuff some more in the client-is-in-the-future scenario (having narrowed down +3h..+4h as the possibly most problematic case, confirm whether that holds in practice) - review some CoC stuff - do we want to move our meeting to 18:00 UTC? isis: last week: - fixed some bugs in the moat server and deployed it #22891 - spent a bunch of time debugging the meek -> apache -> meek -> bridgedb tunneling, gave up and emailed dcf asking for help - started rewriting prop#269 - reread the XE5 lattice handshake reconciliation paper and started thinking about what that would look like for another PQ proposal - made my tooling/setup for testing out alpha releases locally better this week: - finish up proposal writing - still haven't done expense reports (oops)

1 0

Notes from November 16 2017 Vegas team meeting
by Karsten Loesing 17 Nov '17

17 Nov '17

Notes for November 16 2017 meeting: Nick: 1) Planning next alpha release (0.3.2.5-alpha) around 22 or 27 Nov; and for stable releases and 0.3.2.6-rc around 8 Dec. 2) Who should help figure out what a Censorship Team is? [Roger, please review the pad!] Georg: 1) New releases are out (7.0.10 and 7.5a8) 2) Blog post about our Fastly usage, who is working on that one? Deadline is probably Friday next week (Nov 24) 3) Being at OTF and talking to quite some people: Adam from OTF, Torsten from the Briar project and others Karsten: 1) Rebranded Tor Atlas to Tor Metrics Relay Search and made it visually part of Tor Metrics. https://lists.torproject.org/pipermail/tor-relays/2017-November/013547.html 2) Made some internal improvements to ExoneraTor by migrating from Tomcat to Jetty, which facilitates operation. 3) Included as much feedback on our roadmap as we could, will send roadmap PDF to tor-dev@ tomorrow (Friday). 4) Planning to write a blog post about Tor Metrics improvements (Relay Search, metrics timeline, ExoneraTor) later this month or even year. Shari: 1) met with various funders and others in Valencia at OTF Summit 2) hired Antonela! :) Isabela: 1) working on MDF final report 2) getting process for building sites organized as well as other UX team roadmap items (such as testing new tor launcher configuration UI!) 3) November 17 - tomorrow is the deadline to get your needs synced with people. And to sync with those who needs your help. Please add keyword 'TEAMNAME-need' to tickets/tasks that are dependencies from other teams. Steph: 1) first newsletter went out 2) fundraising campaign emails out this morning 3) kat and i started talking about this in montreal, she’s now updating hidden to onion across the site 4) RightsCon submission is due Nov 24 Brad: 1) Updated Grant/Contract Compliance spreadsheet through 10/31 and will be sending out the new version today or tomorrow. Next Vegas team meeting will be in *two* weeks on November 30!

1 0

A little bit about tor browser user path + user feedback on it!
by isabela 16 Nov '17

16 Nov '17

Hello Tor! USABLE project from Internews collected some feedback [attached a summary of it] from a group of 10 East African digital security trainers that they met earlier this year. They will be doing more of these and we hope to coordinate with them as well, giving feedback on their process, getting their help to test improvements we will be working on and so on. I decided to take this opportunity to talk about the user path for tor browser :) I would like to start to use the areas of this path when describing user actions so we can think by those different moments of the user experience. For instance, this feedback Internews collected is more focus on the 'acquisition' part of this path. So what are these moments for Tor Browser? Before Montreal I was working with TB team, helping them prep stuff for their roadmap session. I asked them to organize tickets by 'awareness','acquisition' and 'retention'. These are very common phases that you can identify on any product. But for Tor Browser, this is how I think of them: awareness Is the moment someone hear, read, learn about Tor. That can be at a talk, training, social media or through a friend. So our presence on social media, our support to trainers, our outreach efforts, all goes into this. The common next step for someone here is to either search for Tor to find our site or try to go directly to our site. Or in some cases search for Tor on app stores. So our work on what information is displayed at search results, our work on our app store pages and most important, our work for solutions when these common paths are censored, like Get Tor, is very important. Here is an example of improvement focus on the above, we changed the copy of the search results to give a tip to the user in case they can't open our site [1]. Looking at data early this year (specially from our play store analytics page [2] we are not doing bad here, most people who comes to the store downloads the app. And looking at the steady number of downloads of the desktop browser [3] is not that bad either. Of course we need to improve a lot, our sites are not localized and are terrible. But in general we are doing better here than in other areas of the user path. acquisition If this was a social media app, acquisition is the 'sign up flow' the user goes through. For Tor, the way I think of it is that acquisition are all the steps the user goes from being able to download the browser and install it, then being able to launch and connect to the Tor network. Once the user has the browser open and can browse the internet, they are done with their acquisition path. You will see at the Internews feedback pdf, the tasks they asked the user to perform are around this area. Even though this feedback is not a big surprise for us, it does help us build a baseline to support our reasons to change things :) and of course, with this baseline we can later on, validate if our changes actually helped user. If their perspectives related to the experience has changed. For instance, problems related to tasks #3 and #6 of the attached pdf are things we are working on or has already on our roadmap[4]. With this baseline, we can test our changes and compare if we have improved from there. BTW - we assume we are loosing a lot of people here by looking at download numbers of clients and actual connections at the network. that said, this are assumptions, we can't prove anything :P retention This is one of the most important and hard parts of the user experience. For one we have no idea who we are retaining today, because we don't track that. We don't know if the 2M connections on the network today are users and if they are, we have no idea if they are the same ones that were there yesterday, or the day before and so on. This part of the path starts with the about:tor page and is everything else that is related to enable the user to understand what is going on and have control to customize their experience so they can have the results they are looking for. The more frustration the user has on any of the above, related to things not working or not knowing how to use things or not understanding what is going. Is a good enough reason for them to close the browser and maybe not open it again. That is a lot of work to be done here, and we do have items on TB team, Network team and UX team roadmaps related to it. And face to face user testing will help us validate if what we are doing is indeed helpful for the user. 'resurrection' Tor doesn't do this. Like, the moment a user gets frustrated with TB and closes it, we can't contact that user, send them an email saying 'hey we got a new feature, give us another chance' which is what resurrection means hehe getting someone who left your product to come back. But we should be pro-active in telling the world about our improvements. Specially visible changes improvements. That is our moment to reach people who have tried Tor and gave up, to give it another chance. I have been talking about this with the comms team and with their help we will start doing more of this type of work. Conclusion? This is just a little summary of how we are organizing our thoughts and tasks related to helping the user. Is a work in progress too :) we are always talking and reflecting about these things. I wanted to share these thoughts with a broader audience, I have done it before but have been a while, so I thought of doing it again. Thanks for those who read so far! Cheers, Isabela [1] https://share.riseup.net/#3iFTZxsII6C8Q0i9lx5k0g [2] https://docs.google.com/presentation/d/1a0Lwuj44mjtDqm28cSRKr2Udu2QVArLtGYc… [3] https://docs.google.com/presentation/d/1a0Lwuj44mjtDqm28cSRKr2Udu2QVArLtGYc… [4] https://docs.google.com/spreadsheets/d/1ELMvnIksL-m_r0vJt_rwpIkcjyzZpCyYiQJ…

1 0

Damian's Status Report - October 2017
by Damian Johnson 14 Nov '17

14 Nov '17

Hi all! Here's what I've been up to this last month... http://blog.atagar.com/october2017/ Cheers! -Damian

1 0

An update on teams roadmaps coordination
by isabela 14 Nov '17

14 Nov '17

Hello Tor! I am happy to share some updates on how we are trying to better coordinate communication between teams, specially related to the work each team is doing. At Montreal I was in the laptop sitting at the inter-teams communication session where this was raised as a pain point, and it has been raised before as well in other conversations. So right after Montreal I suggested to Vegas leads to started a process for reviewing each other roadmaps and to acknowledge dependencies other teams might have on your team to better coordinate this collaboration between teams. This pad contains the outline of this plan: https://storm.torproject.org/shared/URX6Jkt3eFjDpAEjtq0oJeWs25AFj8eK-myHKzj… Last Friday, Nov 3rd, we had a meeting with all the teams leads (and others) for the first 'check in' about each others roadmaps. We organized questions for each team roadmap in another pad ( https://storm.torproject.org/shared/6_vKbNygWaF8WcG6xz3lTW6RWbJzlBdm8ZezRYW… ) and if you have one you can add yours there. But please make sure to ping the teams directly about it too. Otherwise they might miss it! :) This was just the kick off of the conversation. At this meeting we didn't had 2 roadmaps: UX Team roadmap and Service roadmap. Those are now integrated and we are already in touch with other teams about collaborating on projects etc. After November 17 - when this chat/coordination phase is over. We will continue with progress check-ins to make sure coordination is happening during execution phase as well. I will organize those too. The goal is to do something like this after each Tor Meeting. So in short the cycles would be: - At Tor Meeting teams meet and build roadmaps - After Tor Meeting we start this process - Once the 'acknowledging phase' and 'dependencies check in' is done we enter execution phase - We do periodically check ins during execution phase to learn about delays or road blocks - Next Tor Meeting is arriving, we do the balance of what we have finished, what we will carry on and start selecting tasks for the next roadmap we will be building at the next Tor Meeting. Not saying this is perfect, we will learn as we go. But at least now we have a process to use and modify. Here is a bonus for those who read so far:) a quick direct link to each team roadmap :P Network: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… Tor Browser: https://storm.torproject.org/shared/roevbMxlBi5rxSAh57iRjy8w1MB2HZArEmM2Jek… OONI: https://storm.torproject.org/shared/CTMRUHLTGG0VEA727afz3Unb7VWfkkRjcshyssP… Metrics: https://storm.torproject.org/shared/m-QJrsoQY23x9mv2SSfMPFjx2pbP91wsWpQtjyW… Community: https://docs.google.com/spreadsheets/d/1biph8qhxvUc_VetcaJjkS9H3kKC95yPB9Z1… Service: https://storm.torproject.org/shared/h82FhoIDG9ZB9-qMd5w0F0GYyvNf0k0zovLjs5x… UX: https://docs.google.com/spreadsheets/d/1ELMvnIksL-m_r0vJt_rwpIkcjyzZpCyYiQJ… Cheers, isabela ps: Some of these spreadsheets was created as copies from the original team roadmap to be easy to consume and review. So, over time they might not stay updated. Please ask the teams directly for more information on their roadmaps like 3 months from now :P

2 2

Notes from weekly network team meeting, 13 Nov 2017
by Nick Mathewson 14 Nov '17

14 Nov '17

Hidden, we are free: Free to speak, to free ourselves, Free to hide no more. Hi! We had our weekly network-team meeting this week, but a lot of folks were busy with travel or healthcare or other important things. So, we had a little but awesome meeting. We love new people at these meetings! Come to the next one! The logs and the summary messages are at http://meetbot.debian.net/tor-meeting/2017/tor-meeting.2017-11-13-16.59.html Below are the contents of the pad where we took our notes: Network team meeting pad, 13 November 2017 Welcome to our meeting! Every monday at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) 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! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Meeting notes from last week: - * https://lists.torproject.org/pipermail/tor-project/2017-November/001560.html - Announcements: - Review-group-25 is open - Does everybody know about the current time allocations that Brad sent around? (ie, where Accounting thinks that we're spending our time) - We need headcount for TeamRotation. Nobody is assigned for ticket triage this week. - Planning for 0.3.2.5-alpha around 24 Nov; and for stable releases and 0.3.2.6-rc around 8 Dec Discussion Topics: - Sprint updates: start of Nov, end of Nov. How did it go? - How are we doing on 032 stability? - Remember to cross-check other teams' roadmaps. (See Isa's email.) - Who needs help with end-of-november? teor (offline): Last week: * Ongoing work with Karsten to graph relay and bridge IPv6 ORPorts, and exit IPv6 support (This shows the impact of authority IPv6 support changes around 22 October) https://trac.torproject.org/projects/tor/ticket/23761#comment:5 * Looked at some security issues * Continued to implement domain counting in Experimental PrivCount * Reviewed the inter-team roadmap pad and added some info This week: * Revise the IPv6 proposal * Review the shamir sharing proposal draft by nickm, and add a section about noise limits * Confirm the details of noise limits with Aaron * Finish domain counting in Experimental PrivCount, and maybe do country/AS as well catalyst (might miss this meeting if medical stuff takes longer than expected): Last week (2017-W45): - some HackerOne review - more download schedule investigation - reviewed more floating point stuff (#23523, #23061) - looked at some circuit build timeout stuff (#24228) - more support on IRC: another instance of someone needing to delete the special macOS directory to get Tor Browser to work. filed #22611 so we can improve our documentation This week (2017-W46): - more bootstrapping research - make more progress on #23605 (don't report progress in building circuits when we don't have a sufficiently live consensus to initialize our guard state) asn: [Physical training starts colliding with the meeting schedule (training ends 19:10, meeting starts 19:00). Might be 20 mins late...] Last week: - Continued progress with md bugs and #23817. We still have some tests failing that we need to figure out. - Found #24228 which seems concering. Unclear if it's a bug and how to handle it. - Reviewed #23985, #23100. - Looked into #23764. Important hsv3 ticket, some work required. This week: - More progress with md stuff. - Get #24228 fixed. - More progress with prop224 stuff. - Figure out guard stuff. ahf - I wont be around during the meeting. My flight lands in Valencia airport an hour after the meeting is over. - Last week (don't have my notes from home - writing from Zurich airport): - Sponsor 8: - - Setup a VM locally to build android packages automatically when there are commits in Tor (runs every 5 min.): missing to setup an fdroid repo to give everyone access to the apk's (if people dare). - - Looked at Nick's proposal for hibernation. - - Finish up on doc/HACKING/android documents. Will create merge requests this week for it. - - Trying to find a way to run some automatic tests on the device for battery consumption reproducibility. - This week: - Misc: - - At the OTF summit in Valencia with GeKo, Shari, and a lot of other people. Let me know if I need to chat with anybody on your behalf or anything! :-) - Nick: - Last week: - - Piles of review and merging! - - Put out 0.3.2.4-alpha. Too many last-minute fixes :( - - Opened a few TROVE entries - - Wrote a proposal draft for improved hibernation design & implementation for mobile platforms. (#24107) - - Wrote a proposal draft for privcount + shamir secret sharing (#22955) - - Wrote a "move ed25519-to-consensus" proposal (#23170) - - Wrote an API draft for more controller C API improvements This week: - Begin preparing backports for upcoming stable releases. - More review and merging - Work on some mobile performance code with Ahf - Help people with end-of-November stuff. - Solicit feedback on designs. dgoulet: - Last week: * Worked on HSv3 control port spec (prop#284) and implementation (#20699). * Reviewed and made patches for 032 tickets. * Helped asn with #24228. * Opened #24186 and worked on getting it fixed asap for the last week alpha release. - This week: * Hope to finish the #20699 ticket (control port implementation) and set it in needs_review for 033 merge. * Plan to work on tor-sched stuff (#23993) from the answers I got on my tor-dev@ thread ("Intense Trek"). * Move forwards my 032 tickets in needs_information and review tickest from the review group. isabela: -Last week: * submitted DRL Q3 report (august and september) * didn't had time to send out Tor Launcher check in email - hope to do it today - This week: * Pinged people on follow up with other teams * Send out check in email for Tor Launcher work * coordinate with UX, HS and TB folks for HS usability work isis: Last week: - Finished up moat #22871 - Commented on H1 report and learned my way around the interface and how to use it - Meeting with Moz about Tor integration - (It's very early here, I'll remember more stuff as I boot up) This week: - Deploy beta moat - Start on proposal (re-)writing for prop#271 and prop#269 and/or PQ TLS proposal Mike: Last Week: - Submitted review/merge requests for #23100 and #23114; fixed them up a bit - Started working on #23101 and #13837 This week: - Fix up #23100 and #23114 as per reviews - Draft patches for #23101 and #13837

1 0

Coordination / booth for 34c3
by Roger Dingledine 10 Nov '17

10 Nov '17

Hi folks! 34c3 is getting closer, and I know a bunch of Tor people are considering going. (A) If you don't have lodging figured out, do it ASAP or earlier. There are not as many options in Leipzig as there were in Hamburg. (B) I hear that OONI is planning to have a real-live booth and assembly area. It would be awesome to get more Tor people than that, and turn it into a broader Tor booth, with swag and people to answer questions and so on. If you want to help there (like commit to working some hours at the booth), let us know. (C) If you are hoping that Tor will help pay for your travel, be sure to ask travel@tpo soon. I think Shari is (rightly) hesitant about paying for travel for a bunch of Tor people to "just go and hang out", so the more specific you can be about planned activities and how they will benefit Tor, the better that will go. --Roger

3 2

Notes from November 9 2017 Vegas team meeting
by Karsten Loesing 10 Nov '17

10 Nov '17

Notes for November 9 2017 meeting: Alison: 1) Submitted Tor 'State of the Onion' proposal to LibrePlanet 2) Montreal meeting survey responses: I just compiled them and I'll share with this group sometime in the coming week. Overall, very positive feedback for the meeting, and lots of requests about improving the open days. 3) Speaking in Paris next week! 4) Anyone have any idea when we can start submitting talk ideas to HOPE? 5) Coordinating with other teams on user support/support related feedback 6) Phoul is making plans to translate the website, starting with the Downloads page. 7) Phoul and I are working on a blog post to encourage new relay operators 8) Doing a lot of work to prepare for LFP's new IMLS grant (starts in December) Georg: 1) Done with a security release (7.0.9, 7.5a7) which was tricky as we only have a workaround which was incomplete first and breaks functionality; furthermore it did cost a lot of time at the end of Sponsor4; thanks again to Filippo Cavallarin + Mozilla and all the others that helped to make this a less bumpy experience than it could have been 2) We are trying to wrap up all remaining pieces for Sponsor4 this month Nick: 1) Onward with releases! 0.3.2 stability is a priority; work on 0.3.3 is slowing a bit because of that... but it's important. 2) Promising discussion with mozilla folks earlier this week. I should make sure that at least some folks attending moz all-hands are briefed on the issues that the moz folks were interested in. Arturo: 1) Many from the OONI team will be at the OTF summit next week (I will probably miss the vegas meeting) 2) We got nominated for the Index on Censorship Freedom of Expression Award for the Digital Activism category (see: https://www.indexoncensorship.org/2016/11/awards-2017/) and we are writing answers to their questions to hopefully get shortlisted. 3) Various 34c3 logistics. We have an OONI assembly at 34c3: https://events.ccc.de/congress/2017/wiki/index.php/Assembly:OONI-verse. Is Tor going to have a presence at 34c3? Should we join forces? 4) Circulated a call for volunteers to work with us on developing a methodology to measure internet blackouts in regions affected the most: https://lists.torproject.org/pipermail/ooni-talk/2017-November/000090.html 5) Gave an interview to an Italian TV channel about the TorMoil bug. 6) Maria gave a presentation about OONI at FSCONS in Norway 7) Simone started a ICFP fellowship at MLAB this month for on year to work on Measurement Kit 8) We contributed to the Citizen Lab's submission to the UN by providing relevant OONI data: https://citizenlab.ca/wp-content/uploads/2017/11/Final-UNSRVAG-CitizenLab.p… 9) Making progress on the mobile app revamping mockup. Karsten: 1) Put draft specification of Tor web server logs on Tor Metrics. https://metrics.torproject.org/web-server-logs.html 2) Discussed next steps for writing better notifications for metrics services and a unified Java package naming scheme for all metrics code bases. https://lists.torproject.org/pipermail/metrics-team/2017-November/000523.ht… 3) Made some sample IPv6 graphs for Tor Metrics. https://trac.torproject.org/projects/tor/ticket/23761#comment:6 4) Made mockups for adding metrics timeline entries underneath graphs. https://lists.torproject.org/pipermail/metrics-team/2017-November/000525.ht… Steph: 1) Enjoying being in Seattle 2) Working on comms strategy 3) Lining up blog content, fundraising emails, newsletter, post on Nyx out yesterday 4) Tweets, tweets, tweets 5) Fundraising: we're up to ~72k, 144k with match Brad: 1) In final stages of financial statement and compliance audit. Auditors expect to issue draft audit report this week. 2) TPI is required to issue formal response to DRL Monitoring Report issued after site visit in Aug 2016. Need assistance with response to Programmatic portion. 3) Between now and year-end, I'll be making a push to update all finance and accounting-related policies & procedures, and will be creating new policy docs as needed. I may reach out to some folks on the vegas team for assistance during that process. Isabela: 1) Roadmaps process is moving pretty good. Last week teams check in meeting were a good start. This week the UX team and Service have created their roadmaps. I will also send an update to tor-project for all community. ux roadmap -https://docs.google.com/spreadsheets/d/1ELMvnIksL-m_r0vJt_rwpIkcjyzZpCyYiQJO1PveRZM/edit#gid=0 service roadmap -https://storm.torproject.org/shared/h82FhoIDG9ZB9-qMd5w0F0GYyvNf0k0zovLjs5xG80- 2) Submitted sponsor8 Q3 (august and sept) report - still for this week there are some sponsor4 reports 3) Organizing some ideas for a 2018 grant strategy meeting in Seattle early december 4) organizing new hires coming up with SIDA contract and kickoff meeting with people who will be involved in this project 5) organizing a plan for building support.tpo (while thinking about the other portals - cuz we will share a lot from design decision to framework). 6) working with Geko on Sukhbir onboarding - 'defining working plan', exercise we are doing/following is here: https://storm.torproject.org/shared/hFzY4dVTL4HJFg0ki0fTy6zu8LT2ajp_YKfJ76x… Shari: 1) met with funder in San Francisco 2) in Valencia next week for OTF Summit 3) so much going on, but not really much to report! Roger: 1) Shari, can you ask Marcin at the OTF summit about the "Roger goes to Sweden to do talk for SIDA" topic? Planning my travel ahead of time works best. 2) I'll be gone next week for two conferences (Monday to Thursday, then Friday to Saturday).

1 0

Community team October 2017 update
by Alison Macrina 09 Nov '17

09 Nov '17

Hello Tor World, Behold, the Community Team did some work in October: October 2017 Community Team report Meeting notes October 2017 ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting Montreal ================================================================== A bunch of us went to the Tor Meeting and had a great time! We had sessions on things like Global South outreach, the support portal, creating a code of conduct, and more. You can find the notes from those sessions, plus all the other sessions from the meeting, here: https://trac.torproject.org/projects/tor/wiki/org/meetings/2017Montreal/Not… Support portal ================================================================== In October we began working more intensively with the UX team and hiro to build support.torproject.org, which will replace the current support wiki which is not very beautiful and not very easy for users to find. The new support portal will be beautiful and searchable with answers to all the most frequently asked questions about using Tor. After the support portal goes live, we will continue adding new content to it. We're also prioritizing localization for the portal. Front Desk ================================================================== We started promoting frontdesk(a)torproject.org for user questions. Ideally, once the support portal is in place, this address will receive much less traffic. Community documents ================================================================== We made a ton of progress on the Code of Conduct draft at the Montreal meeting. We expect to get this out for the proposal period by the end of November. Library Freedom Project ================================================================== LFP got a beautiful website redesign thanks to Mike Finch. Check it out: libraryfreedomproject.org. We're also doing the preliminary work for Library Freedom Institute, our new IMLS-supported 6-month privacy training program for US librarians. We'll open up the call for participants when the grant begins in May. Tor talks ================================================================== Sukhbir gave a talk at the CJFE in Toronto: http://www.cjfe.org/digital_self_defence Alison gave a talk at the Ohio Library Council's annual conference in Dayton, Ohio. Tor meetups ================================================================== There is a Tor meetup planned for Primavera Hacker, which will take place December 2-3 in Santiago, Chile. We hope to encourage many meetups like this, and we're currently thinking about how we could get funding to support them. Team roadmap ================================================================== Like the other teams, we worked on the community team roadmap a bunch at the Montreal meeting and right after. Teams are now in the stage of working out dependencies and adding them to our roadmaps, so once that's finished, we'll publish our roadmap on the community team wiki. The major themes of our roadmap include user support, Global South outreach, relay operator support, improving the Tor Meeting, Library Freedom Institute, more Tor talks from more people, community documents, and translation. ================================================================== -- Alison Macrina Community Team Lead The Tor Project

1 0