- tor-project - lists.torproject.org

No Tor Browser release meeting this week
by Pili Guerra 28 Jan '20

28 Jan '20

Hi everyone, We’ll be pushing this one out to next week. The next Tor Browser release meeting will be held on Wednesday 5th February @ 19UTC. 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

Happy 2020! Privacy by Design
by isabela 27 Jan '20

27 Jan '20

Hello Tor! Happy 2020! First off, I’d like to thank all of you for your amazing support in 2019. Looking back, it is really inspiring to see how much we achieved despite all the challenges. I will try to list some highlights from 2019, but before I do, I want to say that I know we have done much more than what I am listing here. In 2019 we kicked off the year with the stable release of Tor Browser for Android, which is the result of a big effort to improve the Tor experience on mobile. We organized a plan to ensure our network can scale if more people start to use it. We started to look at how to improve user perceived metrics on our network, like speed. Our User Testing Program is now a mature program that we can rely on to receive user feedback about our tools. The Money Machine team really invested in our relationship with donors, and all that great work almost doubled the individual donations in 2019, bringing ~$850k in donations. We also saw the difference in our lives with a dedicated team working on anti-censorship efforts. This front is much better organized, moving projects forward, and we are better informed about what is working and what is not around the world. Thanks to everybody for helping with all this work! For 2020, we will continue to execute our scalability plan for our network, continue to improve its performance metrics, and kick off our Network Health team, a new initiative to ensure that the network is healthy as it grows. Scaling our network is not a small thing, and it will be our priority for a while. But as the demand for privacy increases, [1] we will see more and more people using Tor to improve their own tools’ privacy features. And we want Tor to be able to meet that demand. We should demand privacy by design, because right now, even privacy laws enacted to respond to the crisis we are facing, as it allows too much room for interpretation on the industry side. Privacy cannot be an afterthought. We need technology to be designed in an ethical way that respects people’s rights. Tor is in a position where we can offer privacy protections that others can use on their sites or applications. Onion services are a technology that can serve that goal. And of course onion services wouldn’t be possible without the combined efforts of every team at Tor. In 2019 our year-end campaign was Take Back the Internet with Tor. Throughout 2020, we will campaign for Privacy by Design. And we will promote Tor as both an example of it and one of the ways to achieve it. We have many challenges ahead of us to meet this goal of serving as a solution for other tools to enhance their privacy features. For instance we will have to figure out how to work better on mobile. We want to bring privacy to the internet and people are mainly using mobile devices to access it. There is no way for us to avoid that. We already made progress on this front with Tor Browser for Android and our work on the tor network to improve its performance for mobile devices. But there is a lot more to do, and just like we are doing with scalability, we will break down this work into phases so it's easier to manage and advance it. I am excited with all of the above and I am happy to chat more with folks about it. I would suggest keeping an eye here at this email list for our team’s updates. Folks are working their roadmaps right now and sharing it with their team meeting notes and or reports. Thanks again for all of your support this past year. I know 2020 will be even better. Cheers, isabela -- Isabela Bagueros Executive Director The Tor Project https://www.torproject.org http://expyuzz4wqqyqhjn.onion/

1 0

Next Global South Meeting - Jan 28
by cy63113 27 Jan '20

27 Jan '20

[EN] Hi Tor friends, just a quick reminder of our Global South meeting will be tomorrow, Tuesday, January 28, 16UTC[1] at #tor-south[2][3] ----- [ES] Hola amigos de Tor, solo un recordatorio rápido de nuestro encuentro de Global South, será mañana, martes, 28 de enero, 16UTC, en #tor-south [2][3]. ----- [PT-BR] Olá amigs do Tor, lembrete rapidão de nossa reunião do Global South será amanhã, 3ªf, 28 de janeiro, às 13h, no #tor-south[2][3] See y'all there! Cheers, [1] https://www.worldtimebuddy.com/ [2] https://webchat.oftc.net/ [3] https://trac.torproject.org/projects/tor/wiki/org/onboarding/IRC -- Cybelle DC8F 1F4C 9167 049F 7AA1 0BD6 2FB3 B0C9 F369 34C5 https://keybase.io/cy63113 @cyb3113

1 0

Outreachy interns o/
by Stephanie A. Whited 24 Jan '20

24 Jan '20

Hello Tor, In December, we welcomed 2 Outreachy[1] interns who will be working with us through March. You may have already seen them on IRC or some of the work they've been up to, but we wanted to introduce you and give a formal welcome. Cleopatra (c1e0 on IRC) is helping the Community team on the project "Help Tor support our users." C1e0 has been helping out in the frontdesk world by answering questions and has also been compiling user feedback in a monthly report[2]. Adriana (annalee_ on IRC) is helping the Communications team with "Improving Tor's image in the media and our communications resources." In the application period, she complied a list of influencers for us to reach out to in an upcoming campaign and has since been working on cleaning up our blog tags and press list. She'll soon start helping with more writing-focused projects. Welcome Cleopatra and Adriana! -Steph [1] https://www.outreachy.org [2] https://lists.torproject.org/pipermail/tor-project/2020-January/002645.html -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Fingerprint: E976 9771 7D46 2E63 9697 9F6D 6D6B 72C3 39A8 76AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

Network health kick-off meeting notes
by Georg Koppen 24 Jan '20

24 Jan '20

Hello! We had our kick-off meeting for the network health team yesterday and here come the notes. The IRC log can be found at: http://meetbot.debian.net/tor-meeting2/2020/tor-meeting2.2020-01-23-18.00.l… The pad we used to organize our meeting topics and outcomes is at https://pad.riseup.net/p/tor-networkhealth-2020.1-keep Highlights from this meeting are: 1) We talked about the long-term topics guiding the network-health team work. Breaking those down results in the following priorities for 2020: a) detect and resolve bad relays b) anomaly analysis / network health engineer [with network team] c) relay advocacy [with community team] d) make sure usage/growth stats are collected and accurate [with metrics team] e) maintain the components of the network to keep it healthy 2) Based on 1) we started our roadmapping (which is not finished yet) to figure out the most urgent work to do for the next coming weeks and months. You'll find the progress we made so far on the above pad, too. 3) We agreed on having weekly meetings and status updates as the other teams are doing. Our tentative meeting time will be Monday, 1900 UTC in #tor-meeting on OFTC's IRC network, starting Monday, 2/3. If any of you have questions/concerns/comments, don't hesitate to send them! Georg

1 0

Notes from Vegas Meeting JANUARY 23 2020
by Erin Wyatt 23 Jan '20

23 Jan '20

Notes from Vegas Meeting JANUARY 23 2019: + NEW BUSINESS [anarcat] - Debian 9 stretch EOL this summer, want to check in with service admins and teams how to schedule buster upgrades Discussion: will coordinate/discuss with Gaba next week and make a plan to move forward. [Sarah] - San Francisco party prep - do we know anyone at Reddit to invite? Discussion: maybe it’s time to make a wider call. If you’re reading this and you know someone, please contact sstevenson@torproject. Thanks! + GENERAL NOTES Georg * Network health planning; kick-off meeting will be after the Vegas meeting (see: https://lists.torproject.org/pipermail/network-health/2020-January/000452.h…) Antonela * S27, S9 regular duties * Submitted RightsCon proposal on Human Rights and Design track with Simply Secure, Jigsaw and A19 * Reading about cohosh bridge's proposal * Pushing the iterated download page from [dev] to [staging] * Traveling to Berlin this weekend; set meetings with Simply Secure and OTF for Metrics with Nina, OTF for S27 with Fiona, OTF for Metrics with Elio. FF <> Tor UX meetings are: Tracking Protection UX, Fenix High-level Road Map, Anti-tracking Engineering Planning * I will reach FOSDEM in the weekend * Meeting the OTF comms lab about onions with Steph and others * Meeting Soraya from EFF to sync about collabs Gaba * Roadmapping with anti-censorship, metrics, network, network health and syadmin temas... \o/ * Roadmapping new IPv6 project * Preparing S30 report for Bekeela to send * Traveling on Tuesday to attend Sustain Summit next week - https://sustainoss.org/summit-2020/ * FOSDEM in the weekend & meetings: Simply Secure for Metrics portal project (with Antonela), sbws with Juga and Alex Sarah * Sent 2019 tax receipts to monthly donors. * San Francisco party prep - do we know anyone at Reddit to invite? (See above.) * Planning NYC lunch in April. * Back to rolling invites to monthly and major giving programs. Erin * Moving office next Tuesday; selling stuff and packing up this week/weekend * HR/Personnel stuff * New shadow dev starting Monday 1/27 * Trying to get caught up Alex: * Team seems to be doing good. People seems to be hacking on roadmap stuff and/or 0.4.3 stuff. * Going through Gitlab todo list. * Next week I'll be at FOSDEM in Brussels. Might miss next Vegas meeting due to traveling. * Did first round of 1:1's with network team folks this week. Nick. * Status w walking onions proposal. * Released 0.4.3.1-alpha: woo! * More stable releases likely next week. Mike: * Circulated research director roles pad; worked on 2020 goals * Worked on tor-dev congestion control epic mail (still fixing details) * Prepping for Mozilla all hands next week. Anarcat: * started setup of new ganeti node (#32937) which will give us some breathing room to shutdown old servers * experimented fairly successfully with setup-storage to standardize disk formatting in our install automation work (#31239) * decom'd a ARM build box that was having trouble at scaleway (#33001), future of other scaleway boxes uncertain, delegated to weasel * looked at the test Discourse instance hiro setup * new RT queue ("training") for the community folks (#32981) * upgraded meronense to buster (#32998) surprisingly tricky * Debian 9 stretch EOL this summer, want to check in with service admins and teams how to schedule buster upgrades * established first draft of sysadmin roadmap with hiro https://help.torproject.org/tsa/roadmap/2020/ * various small tweaks (proper headings in wiki #32985, ticket review, followup with jim's key, irl acceses in #32999, logging issues on archive-01 #32827, cleanup old role #32787, cleanup old rc.local cruft #33015, puppet code review #33027) Philipp * Slowly wrapping up TTP grant * Worked on roadmap for the next three months isabela * Coordinating w/ anto, steph, asn, roger the onion services/nodarkweb strategy, I will plan a meeting and add Hiro to this game. We are in touch with OTF labs on this as well. * Had my first meeting with the Board in 2020 and we discussed a mid FY analysis that I presented. * Continue 1:1 w/ vegas leads for 2020 prep * first meeting on creating guildelines for relationships regarding funds * Continue to organize EFF event, event at Ford and Membership Program. Gus * Following up with Cleopatra and reviewing her work * Submitted RightsCon proposal - Tor Meetup in Global South + invited to talk about the future of activist communication organized by Harvard's Shorenstein Center. * Attended to IFF Village meeting last friday, I'm working on a private pad to put together our proposals. * Travelling next week to Fosdem, offline on Jan 31th. * Doing 2:1 with Pili and volunteers in Community Team. * Organizing S9 work (creating training workflow) Pili * FOSDEM prep * GSoC wrangling * Some website updates * S27 deliverable review * Regular trac triage and other maintenance tasks Matt: * Sketching some team organizational improvements * Preparing for Moz All Hands next week * Trying to keep up with all the announcements happening in the Browser Privacy space Steph: * Working with OTF Learning Lab for onion services. Mapped out initial work plan * Working with annalee_ on blog tag organization and planning next projects * Writing a piece on our press coverage last year * Submitted a session on privacy laws and privacy tools to RightsCon Karsten: * Upgraded metrics website host to buster, with help from anarcat. * Resolved a bunch of defects in Metrics/* components.

1 0

Anti-censorship meeting notes, 23 Jan 2020
by Philipp Winter 23 Jan '20

23 Jan '20

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-23-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday January 23rd 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://dip.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting's notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Projects 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 ------------------------- --- January 23rd 2020 --- ------------------------- == Announcements == * Thanks to atagar, BridgeDB is now ported to Python 3! == Discussion == * Anyone want to mentor a student developer during the summer? We have time to apply until early February. https://summerofcode.withgoogle.com/how-it-works/#timeline Ideas from last year: https://2019.www.torproject.org/getinvolved/volunteer.html.en#Coding Ideas for this year: https://pad.riseup.net/p/anti-censorship-gsoc * Anything else to report as done for last year on Sponsor 30? Please fill in: https://pad.riseup.net/p/sponsor30-first-report * Kyle Undergrad Thesis: Fingerprintability of Snowflake == Actions == * Our GSoC deadline is approaching: Feb 5 * https://pad.riseup.net/p/anti-censorship-gsoc == 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. 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 phw: This week (2020-01-23): * Made modifications to https://bridges.torproject.org/scan/ as per arma's suggestions * Uses GET instead of POST now, and explains the expected format of IPv6 addresses * Filed #33008, so Relay Search shows a bridge's distribution bucket * Prepared for and attended roadmapping meeting * One-on-one with isabela * Reviewed #32711 * TTP grant writing and meeting Next week: * Roadmap post-processing (e.g., formalising goal statements) * More grant writing * #33007 * #30946 Help with: * https://trac.torproject.org/projects/tor/ticket/31872 Gaba: () Last week (Jan 16th): This week (planned): * roadmapping * sponsor 30 report cecylia (cohosh): last updated 2019-01-23 Last week: - anti-censorship team roadmapping - revised, merged, and deployed gettor gitlab fixes (#32711) - switched github gettor provider to new repository (#32977) - wrote up some descriptions for GSoC projects - more work on snowflake throughput checks (#32938) - started working on a localization fix for gettor binaries(#33002) - grant writing - fixes for local GetTor tests (#33004) This week: - grant revising - look at reports of shadow socks blocking - check in on censorship measurements again - finish up snowflake throughput checks (#32938) - finish up localization fix for gettor (#33002) Needs help with: - review of #31971 (from tor browser team) - review of #33004 (hiro?) arlolra: 2020-01-23 Last week: - nothing Next week: - read up on turbo tunnel - start on #19026 Help with: - dcf: 2020-01-23 Last week: - small logging fixes in Snowflake (#33011) - opened an issue to decide the fate of the go-webrtc repo https://github.com/keroserene/go-webrtc/issues/109 Next week: - turbo tunnel in Snowflake - do Let's Encrypt upgrade for Snowflake bridge (#32964) Help with: cjb: 2019-01-23 Last week: - took a stab at #31009, but couldn't find an IPv6 replacement for router_pick_published_address(). ahf's going to take it. Next week: - try to do better at asking for help :) Help with:

1 0

Metrics Team Meeting Notes, January 23rd 2020
by Gaba 23 Jan '20

23 Jan '20

Hi! We had our weekly metrics team meeting today. We are going to skip next week's meeting. The next one is going to be on February 6th. The pad for the meeting in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The log for the meeting is: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-23-15.01.log… And the agenda/notes: ------------------------------------- Agenda Thursday, January 23rd, 15 UTC ------------------------------------- potential gsoc project (georg is interested in mentoring with somebody else): Tor weather (#26124) <-- pili is going to follow up on this to define scope of this gsoc project --gaba --> schedule next roadmap session When? Mostly we need to complete the scalability/onionperf project. Organized in https://pad.riseup.net/p/0K2Q5uuN0CbjbOGxJQsL-keep and will send mail for tasks before session. Needs review tickets: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Defect tickets: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… Roadmap (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap cheers, gaba -- 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

Network Team Meeting Notes, 22 January 2020
by Alexander Færøy 23 Jan '20

23 Jan '20

Hello, Here is a short summary of the network team meeting from Wednesday the 22nd of January 2020. 1) We started out with roadmap. We went over our Q1 2020 roadmap and checked if everything looked good. Gaba had imported tickets from Trac before the meeting such that all of that was ready. 2) We went over review assignments. Things looked fine. 3) We looked at the 0.4.3 status page. People were asked to make sure that tickets had the 043-must/043-should/043-can keywords and otherwise they will be moved to 0.4.4 planning. Nick and Alex will meet next week and try to distribute some of the tickets out to team members. 4) Nick asked if anybody had any blockers of 0.4.3.x and if not, he would roll an alpha release after the meeting. 5) We talked shortly about the upcoming IPv6 grant (s55): teor is going to be working on this but they are open for other people to join in. There is a planning meeting on 23/01/2020 at 22 UTC for this sponsor. 6) We could use more people that are up for doing merging to master. 7) We discussed some Stem CI issues and how we should handle them. 8) We discussed getting more eyes on sbws. Ideally we should talk with the network health team here too such that they have an idea about what is happening with bandwidth scanning. 9) Nobody had anything else to discuss. --- end of summary --- You can read the network team meeting log at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-22-22.59.html Below are the contents of our meeting pad: Nick: Week of Jan 13 (planned): - Freeze 0.4.3 in two days - more work on whatever gets reviewed. - reviews and merges - Write a test for 20218 - Try moving dirauth_mode() to src/core - More investigation on 32835 (log bug) - More investigation on 32868 (assertion bug) - More releases? Or wait for more fixes? - 0.4.3.1.x-alpha? - Split up core/include.am (32137) - PETS discussion - PETS artifact review Week of Jan 13 (actual): - 0.4.3 freeze - Completed and merged a bunch of branches - Worked on a fix for a practracker issue (32705) - Testing for 20218 - More investigation on 32868 (assertion bug); added mitigation - Split up core/include.am (32137) - PETS discussion - Revised 32695 (remove consensus methods 25-27) - Revised 32487 (--disable-relay-mode disables directory caches) - Review and hacking on 32709 (onionbalance subcredential fix) - Fixed an add_c_file bug (32962) - More reviews, merges, fixes, revisions. Week of Jan 20: (planned): - US HOLIDAY ON MONDAY - Finish fixes on #32709 (onionbalance subcredential fix) - 0.4.3.1.x-alpha - More releases? Or wait for more fixes? - Help with triage and assignment on 0.4.3.x - work on clusterfuzz failure - PETS discussion and artifact review catalyst: week of 01/13 (2020-W03) (actual): - reviews - helped out with NT service patch troubleshooting (#32984, #32883, #32778) - helped out with add_c_file troubleshooting (#32962) - GSoD week of 01/20 (2020-W04) (planned): - reviews - TPI holiday 01/20 - GSoD - create tickets for roadmap items that need them - investigate some clang-format stuff (#32921) week of 01/20 (2020-W04) (actual): - TPI holiday 01/20 - investigated availability of features in various clang-format versions (and availability in OS packages) ahf: Last week (planned): - Send out 1:1 schedules to team members. - Sync with Gaba. - Some meetings. - Hack on roadmap items. Last week (actually): - Synced with Gaba. - Sent out 1:1 schedules to everybody. - Submitted PRs for some s28 tickets. - Looked a bit at the dalek Rust code for one of the optional roadmap items. - Some ticket triage with Nick. This week (planned): - 1:1s with everybody pretty much. - A few meetings. - Continue to work on s28 tickets. Mike: Last week (planned): - Have gaba+isa review role descriptions - Metrics kickoff meeting - Work on explicit congestion notification meta-proposal - File perf-related roadmap tickets - Triage + prioritize circpad, vanguards bugs Last week (actual): - Had gaba+isa review role descriptions; worked on 2020 plan - Metrics kickoff meeting - Worked on explicit congestion notification meta-proposal This week (planned): - Mozilla all hands - Congestion control tor-dev post Maybe dropping due to Mozilla: - File perf-related roadmap tickets - Write mails to researchers re circpad docs + simulator - Triage + prioritize circpad, vanguards bugs dgoulet: Week of Jan 6th (actual): - Triage some tickets - Patch on #32892 - Reviewed some tickets. - Opened #32910 and started to work on it. - Code needed before feature freeze for s27: #32709. - Answered some tor-dev emails about HS DoS defenses. More in the pipe now as people have been responding. - Fixed #32847 Week of Jan 13th (planned): - Finalize asap #32709 with asn before freeze on Wed. - Continue with #32910 Gaba: Week of Jan 13th (actual): - Get up to date with mails and Trac - Follow up on Gitlab status - Roadmapping for Scalability (with metrics team) - Check on sponsor work. Week of Jan 20th (planned) - Roadmap life - Run behind Trac teor: (online first meeting of the month, offline at the usual meeting time) Week of 13 January (actual): Take Time for: - catching up on emails and IRC - post-0.4-stable backports and ticket triage - Draft sponsor 55 (relay IPv6) roadmap - Split into stages, no ticket numbers yet - Review IPv6 tickets for relevance Roadmap: - 0.4.3 bug fixes - #32588 Fix ORPort IPv6 auto port - #32822 Make Authorities add their own IPv6 ORPort to trusted dir servers - #32705 Practracker tests - #32772 Git scripts - remove 0.2.9 - #32778 Initialise pubsub in Windows NT Service mode - #32962 add_c_file.py refactor Other: - Fallback Scripts: CI fixes, list changes - Code Reviews: Bugs, Manual Page, Modularisation, Removing Obsolete Code, Volunteers - Proposal 306 (Client IPv6) Review and Changes - Triage old 0.2.9 backport tickets Week of 20 January (planned): Take Time for: - Draft sponsor 55 (relay IPv6) roadmap - Add existing ticket numbers - Make existing tickets child tickets of sponsor objective tickets (once Gaba has created the sponsor objective tickets) - Draft sponsor 55 proposals - If I write the proposals now, we can have them reviewed by 1 February, when the grant officially starts - O1.1: Relay IPv6 Reachability Checks - O1.2: Relay Auto IPv6 Address - O1.5: Relay IPv6 Statistics Roadmap: - Hand over or triage out 0.4.3 bug fixes Other: - Code Reviews Week of 20 January (actual): Take Time for: - Draft sponsor 55 (relay IPv6) roadmap - Add existing ticket numbers Roadmap: - 0.4.3 bug fixes - #32778 Initialise pubsub in Windows NT Service mode - #32962 add_c_file.py refactorservers - Triage #32314 Can't connect to literal IPv6 address containing double colon - Diagnose #33006 Fix test-stem `test_take_ownership_via_controller` failure Other: - Fallback Scripts merges, CI fixes - Code Reviews: Bugs, Volunteers - Ticket triage Need help with: - 0.4.3 bugs: I need to hand them over so I can do Sponsor 55 work. (See the list in the discussion section.) -- Alexander Færøy

1 0

Gitlab Migration Status 17/1 2020
by Alexander Færøy 23 Jan '20

23 Jan '20

Hello list! Gaba and I recently talked about how it would be good to have some status about where we are with the Gitlab migration project. In December a lot of you reported a lot more issues than I had spotted, which was both extremely good, but also not so good in that every issue was another thing for me to fix :-) Thanks to everybody for reporting these! Fortunately, with anarcat's suggestion of using some parts of tracboat I got over some of the "Trac markup" to Markdown issues quickly, but some of them remained. Recently, cohosh reported an issue with the Gitlab instance we were running where PR's generated 503 messages. Hiro spend a lot of time trying to debug this, and with this new issue in mind, we have decided to move to Gitlab's own "omnibus" package method for maintaining the Gitlab instance instead of Debian's "salsa" Ansible playbooks. We feel that a larger number of us are more confident with operating the omnibus Gitlab instance and those of us who have been running Gitlab instances this way before (hiro, gaba, and myself) haven't run into issues like the ones we have had with Salsa so far. Here's a summary for my Gitlab hackday today: - Synced my local cache of Trac tickets (used for speeding up runs). - Worked on "missing information" issues reported in December: points -> estimation, actual points -> spending (both based on a conversion function Gaba and I talked about in December), owner, milestone, reviewer, and "reported by". I still use my own username for these to avoid spamming folks with emails. - CC in issues for *known users* so far. That is the people who have users on GL when we move. - Figure out how to handle parents. - Extended the "Tracboat" conversion code with handling some of our {{{ }}} (code blocks) and headlines better. Checking the cosmetic changes for errors takes longer time than all the metadata issues since I need to go over tickets and see if things "looks right" and not just look out for missing or wrong information. Right now it's running against my local GL install in a Qubes VM for speed, and once I've gone over the results I'll make it post to a new repo on dip.torproject.org (this makes the difference of a sync from 8h for a complete sync to 20min). I will be using "strike through" on the text on our December pad to indicate that I think something is fixed, then we can walk over it together at a later point. Have a nice weekend all! All the best, Alex. -- Alexander Færøy

2 2