Community issueshttps://gitlab.torproject.org/groups/tpo/community/-/issues2024-01-24T21:11:38Zhttps://gitlab.torproject.org/tpo/community/onion-tex-slim/-/issues/3Setup script2024-01-24T21:11:38ZSilvio RhattoSetup scriptSimilar to tpo/web/onion-mkdocs#3.Similar to tpo/web/onion-mkdocs#3.https://gitlab.torproject.org/tpo/community/onion-tex-slim/-/issues/2Document localization options2024-01-24T21:11:37ZSilvio RhattoDocument localization optionsSimilar to tpo/web/onion-mkdocs#5.Similar to tpo/web/onion-mkdocs#5.https://gitlab.torproject.org/tpo/community/hackweek/-/issues/33Add license2023-11-15T15:08:32ZSilvio RhattoAdd licenseThis project needs a copyright/copyleft license.
This is not a regular Hackweek proposal. Instead, it's is an actual task to improve it's documentation.This project needs a copyright/copyleft license.
This is not a regular Hackweek proposal. Instead, it's is an actual task to improve it's documentation.https://gitlab.torproject.org/tpo/community/hackweek/-/issues/32Improve formatting for past Hackweek documentations2024-02-13T20:06:20ZSilvio RhattoImprove formatting for past Hackweek documentationsWhile working on tpo/community/hackweek#13, Hackweek got a website: https://tpo.pages.torproject.net/community/hackweek/
Now it's way easier to browse and search for past projects, but this also exposes the need to fix formatting at som...While working on tpo/community/hackweek#13, Hackweek got a website: https://tpo.pages.torproject.net/community/hackweek/
Now it's way easier to browse and search for past projects, but this also exposes the need to fix formatting at some pages.
This ticket is about fixing the formatting for the existing docs.
This is not a regular Hackweek proposal. Instead, it's is an actual task to improve it's documentation.https://gitlab.torproject.org/tpo/community/training/-/issues/124Index of presentations in the home slide deck2024-01-24T21:10:16ZSilvio RhattoIndex of presentations in the home slide deckBuild an index of presentations in the [home slides]:
* Listing the ones from the current year, and the outdated ones.
* Linking to all available assets for a given slide (ODP, PDF, HTML etc).
* To be built as part of the CI Pipeline.
...Build an index of presentations in the [home slides]:
* Listing the ones from the current year, and the outdated ones.
* Linking to all available assets for a given slide (ODP, PDF, HTML etc).
* To be built as part of the CI Pipeline.
[home slides]: https://tpo.pages.torproject.net/community/training/https://gitlab.torproject.org/tpo/community/training/-/issues/123Switch from "master" to "main" branch2024-03-05T16:32:50ZSilvio RhattoSwitch from "master" to "main" branch# Tasks
* [ ] Switch the repository from "master" to the "main" branch.
* [ ] Update references on the [Training resources page at the Community Portal][] pointing to the correct branch, like in [this file][].
[Training resources page ...# Tasks
* [ ] Switch the repository from "master" to the "main" branch.
* [ ] Update references on the [Training resources page at the Community Portal][] pointing to the correct branch, like in [this file][].
[Training resources page at the Community Portal]: https://community.torproject.org/training/resources/
[this file]: https://gitlab.torproject.org/tpo/web/community/-/blob/main/databags/community-training-materials.jsonhttps://gitlab.torproject.org/tpo/community/training/-/issues/122[Training] Make Tor training slides compatible with Reveal JS format2023-11-13T18:38:40Zraya[Training] Make Tor training slides compatible with Reveal JS formatEventually all training slides prepared and maintained by the Tor Project should be compatible with Reveal JS so as to provide an option for users to view our material through their browser: https://community.torproject.org/training/reso...Eventually all training slides prepared and maintained by the Tor Project should be compatible with Reveal JS so as to provide an option for users to view our material through their browser: https://community.torproject.org/training/resources/rayarayahttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40128Retire 'gettor web' component2023-11-08T11:18:05ZemmapeelRetire 'gettor web' componentThe small website for GetTor has been replaced with a forward to the support portal gettor page, for easier maintenance and updates.
We need to retire the component:
* [x] Remove it from weblate
* [ ] Remove it from the docs
* [x] Remo...The small website for GetTor has been replaced with a forward to the support portal gettor page, for easier maintenance and updates.
We need to retire the component:
* [x] Remove it from weblate
* [ ] Remove it from the docs
* [x] Remove it from the stats
* [ ] move branch to the translation attic
* [ ] archive translation memoryemmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40127stats: Add clear 'needs review' column to tables2023-11-21T17:54:50Zemmapeelstats: Add clear 'needs review' column to tablesOn our translation stats: https://tpo.pages.torproject.net/community/l10n/stats.html or for each language: https://tpo.pages.torproject.net/community/l10n/ar.html we have several actionable links to go to weblate queries: strings failing...On our translation stats: https://tpo.pages.torproject.net/community/l10n/stats.html or for each language: https://tpo.pages.torproject.net/community/l10n/ar.html we have several actionable links to go to weblate queries: strings failing checks, suggestions, needs edit. But we don´t have a clear 'needs review' list for reviewers to go straight there.
Hopefully adding that column will help increase the number of reviewsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/policies/-/issues/12Rename gitlab branch master -> main2023-11-10T19:06:47ZGusRename gitlab branch master -> mainSilvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/31Tweets for the comms team2023-11-30T16:16:40ZemmapeelTweets for the comms team# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a cale...# About the project
* Contact: emmapeel
* Chat: #tor-project on `irc.oftc.net`
* Video room: https://tor.meet.coop/<FILL IN>
# Participants
- emmapeel
- pavel
# Summary
Last year we started a bank of content to tweet, with a calendar as well for important dates. This was to be put for translation, and used in our social media.
This year we did a test in weblate with a simpler format ( Here you can see the format for the Spanish translation: https://gitlab.torproject.org/tpo/translation/-/blob/social-content/es.csv?ref_type=heads ) , and we want to review last year's strings and add them to this new format component in weblate. This format is easier to use for the comms team and does not use as much resources as the previous setup with lektor and gitlabCI etc.
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
# Skills
- We need tweets to use and translate, please add your suggestions to this ticket.
# Links
Last years repo: https://gitlab.torproject.org/tpo/web/social-bank/
In weblate: https://hosted.weblate.org/projects/tor/social-copy/#translations
New repo in gitlab: https://gitlab.torproject.org/tpo/translation/-/tree/social-content?ref_type=headsHackweek 2023emmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/30design.torproject.org2023-12-08T21:30:56Zdonutsdesign.torproject.org# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing ...# About the project
* Contact: @donuts
* Chat: **#tor-ux** on `irc.oftc.net`
* Video room: message donuts for the link
# Participants
- @donuts
- @jag
- @nicob
# Summary
The UX Team have been discussing replacing the [existing styleguide](http://styleguide.torproject.org) with a new resource that's wider in scope – e.g. "design.torproject.org". In addition to updating our brand and web guidelines given their evolution over the past few years, we're also considering adding new sections to document our human-centered design principals, user research program, and overall methodology. The revised portal should serve as a central point of reference for external resources too, including for example our Figma libraries for the browser, web and VPN, and any open source design resources we use.
Given the large scope of this project, it's expected that we'll make some progress in planning the structure, content and design of the new portal – however we'll likely need to wait for a second hackweek or future funding opportunity to complete the implementation.
**Hackweek goals:**
- [x] Site map
- [x] Some content planning/development
- [ ] Figma prototype
- [ ] Basic HTML templates (stretch goal)
# Requirements
Institutional knowledge:
- Direct knowledge of the Tor Project's brand, design systems, user experience and/or user research practices.
- Or the ability to communicate your needs as a consumer of this documentation.
Technical skills:
- Graphic and/or web design (required)
- Front-end development (optional)
- Experience with lektor (optional)
# Links
Existing documentation:
- [Tor Project Styleguide](https://styleguide.torproject.org)
- [Community / User Research](https://community.torproject.org/user-research/)
- [User Research repo](https://gitlab.torproject.org/tpo/ux/research)
- [Firefox Acorn](https://acorn.firefox.com/latest/acorn-aRSAh0Sp) (external)
Design libraries:
- [Tor Browser for Desktop](https://www.figma.com/file/RtZ0fqkNMRc7GOjK3FLclz/Tor-Browser-for-Desktop?type=design&node-id=611%3A55&mode=design&t=1YIBBFxWnpmQUHwP-1)
- [Tor Browser for Android](https://www.figma.com/file/LaU3qFpem2xQOfBF6MEYVR/Tor-Browser-for-Android?type=design&node-id=611%3A55&mode=design&t=mjkrcP2LegGQLM8K-1)
- [Icons & Illustrations](https://www.figma.com/file/sd4yASXsToxFECsraTlAsw/Icons-%26-illustrations?type=design&node-id=0%3A1&mode=design&t=jGmz3Uwj5OmdsGoK-1)Hackweek 2023donutsdonutshttps://gitlab.torproject.org/tpo/community/support/-/issues/40129Update Forum guide:"Tor blocked in Russia - how to circumvent censorship"2023-11-04T02:03:55ZGusUpdate Forum guide:"Tor blocked in Russia - how to circumvent censorship"Let's review and update the Forum guide "Tor blocked in Russia - how to circumvent censorship".
https://forum.torproject.org/t/tor-blocked-in-russia-how-to-circumvent-censorship/982Let's review and update the Forum guide "Tor blocked in Russia - how to circumvent censorship".
https://forum.torproject.org/t/tor-blocked-in-russia-how-to-circumvent-censorship/982ninaninahttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/29Document how to verify reproducibility of build of a mullvad/tor browser release2023-11-30T16:16:39ZboklmDocument how to verify reproducibility of build of a mullvad/tor browser release# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify...# About the project
* Contact: @boklm
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: no
# Participants
- @boklm
# Summary
I think many users don't know that our builds are reproducible, or how they can rebuild to verify that they get a matching build.
We could generate a `reproducible-build.txt` file in the release directory containing the following informations:
* which git repository to clone
* which commit to checkout
* which command to use to start the build
* which sha256sums to expect after the build finished
* how to remove embedded signatures from exe and mar files we publish to check that they match the unsigned build
# Skills
Need to know how to build Tor Browser.
# Links
* tpo/applications/tor-browser-build#40997Hackweek 2023boklmboklmhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/27TPA issue templates2023-11-30T16:16:39ZanarcatTPA issue templates# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and i...# About the project
* Contact: @anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
# Summary
An ancient ticket in the TPA issue tracker has been found, and it is full of precious metals, behold https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398. The idea is that many (MANY) tickets issued in TPA often require the same basic data. Want a server? How big? who's team? Your PGP key expired? Please ship the key, etc. We waste an inordinate amount of time collecting that information when people open new issues.
The task here is to setup those templates in the TPA issue tracker. The twist is that right now the TPA project doesn't have any code at all: it's a "wiki only" GitLab project, and the code is instead in the tpo/tpa/wiki-replica project, mirrored into the tpo/tpa/team wiki, which shows up as the frontpage for the project. We need to find a way to do this transition cleanly, probably by moving wiki-replica directly into tpo/tpa/team (in which case we lose the homepage) or some other sheninagan.
# Skills
Some experience with GitLab is important. Probably relevant only to TPA people, but other contributors are of course welcome!
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/29398
* https://gitlab.torproject.org/tpo/tpa/wiki-replica/
* https://gitlab.torproject.org/tpo/tpa/team/Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/26wiki replacement considerations2023-11-30T16:16:40Zanarcatwiki replacement considerations# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproj...# About the project
* Contact: anarcat
* Chat: #tor-admin on `irc.oftc.net`
* Video room: https://tor.meet.coop/ana-amp-2kq-z2o
# Participants
- @anarcat
- @shelikhoo
# Summary
[TPA-RFC-38: Wiki replacement](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service) is a draft from TPA aiming at reviewing whether or not to replace the current GitLab wiki(s) by something else. It's mostly stalled, so let's see if we can move it forward a nudge.
Let's review the requirements to see if they cover what we need and what we want to accomplish. I particularly want to discuss which content we intend to throw "in the wiki" and whether a wiki is the appropriate tool for this. I particularly do *not* feel like it's a good tool for technical team to document their software projects, where alternatives like mdbook, sphinx or mkdocs seem better suited (see the recent torspec change for example).
It's unclear how this should be organized. In Costa Rica we've had an informal discussion about this which was useful, maybe having a BBB call or two to shake things up could move this ahead?
# Skills
Everyone from the community is welcome to join the discussion.
# Links
* https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service
* https://gitlab.torproject.org/tpo/tpa/team/-/issues/40909Hackweek 2023anarcatanarcathttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/25tor-browser-build project survey2023-12-01T14:28:56ZPier Angelo Vendrametor-browser-build project survey# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
...# About the project
* Contact: @pierov
* Chat: #tor-browser-dev on `irc.oftc.net`
* Video room: nope
# Participants
- suggested: apps team members and other people who regularly use tor-browser-build or curious about it
- @boklm
# Summary
We have 120 projects in tor-browser-build.
Understand why we have some them is easy (e.g., Firefox), but some other are platform-dependent (e.g., the shenanigans that macOS signing needs), some other are Namecoin dependencies.
## Dependencies graph
It'd be great to create a graph with all the dependencies.
Hopefully it should contain just a single connected component (`browser`/`release`), or a few additional components that make sense to have (e.g., signing tools).
If we find components that don't make sense to have, we should then purge them from `tor-browser-build` (e.g., dependencies that aren't needed anymore and recursive dependencies).
I'd expect the graph to be directed and cyclical (some components depend on themselves with a different target).
So, we might find also some projects/nodes that just depend on other nodes, without being a dependency for anything.
We might want to purge them as well.
## Project readmes
At the moment, each project is required to have a `config` file, but most have also a `build` file.
It'd be great if we added a `README.md` (or something similar) to each project, to explain:
- what it is
- why we have it
- what we do here if it isn't trivial (e.g., for `browser`) and/or caveats of the build process (e.g., we have to do these additional steps because we cross compile, or we have to do also this for reproducible purposes)
- references (e.g., link to the website, when we follow Mozilla's build script, a reference to these build scripts, or known issues, such as NSIS requiring to be built with GCC).
# Skills
Know tor-browser-build (well, this documentation project might help knowing it more).
# LinksHackweek 2023Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40126Improve Access Keys documentation: explain difference to shortcuts2024-01-24T21:11:50ZemmapeelImprove Access Keys documentation: explain difference to shortcutsWe already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way t...We already have some documentation about Access Keys: https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-translators#access-keys
But it needs to be improved.
We need to differentiate Access Keys, that are a way to navigate menus, from keyboard shortcuts.
One difference: Shortcuts are the same for all locales, Access Keys depend on the locale.
ref: https://hosted.weblate.org/translate/tor/tor-browser/tb-newidentityproperties/ru/?checksum=73b4988ed95a84d9#commentshttps://gitlab.torproject.org/tpo/community/support/-/issues/40127[User support] Review the "Private bridges cn" (front desk) and /commands (cd...2024-02-06T03:36:26ZGus[User support] Review the "Private bridges cn" (front desk) and /commands (cdr.link)In our user support documentation, we have included an option for users in China to request a 'private bridge' by emailing us. However, we have been receiving requests for private bridges from countries without heavy censorship, like Mex...In our user support documentation, we have included an option for users in China to request a 'private bridge' by emailing us. However, we have been receiving requests for private bridges from countries without heavy censorship, like Mexico, where internet restrictions can be bypassed using bridges from other distributors (https, telegram...). The feedback and emails received may indicate a possible misunderstanding of requesting a private bridge. Some users believe that because censorship in China is so sophisticated, they need "that bridge" to bypass their local censors, which is a misconception.
Let's review and check how we can improve the tb-manual text and the commands in CDR.Link.
(cc @ebanam @nina)https://gitlab.torproject.org/tpo/community/l10n/-/issues/40125Add documentation section about RTL for developers2024-02-26T19:28:02ZemmapeelAdd documentation section about RTL for developersWhen we release translations RTL some questions are always repeated, and it would be nice to have a documentation that developers can read, with examples and best practices. Also with screenshots to understand the common problems.When we release translations RTL some questions are always repeated, and it would be nice to have a documentation that developers can read, with examples and best practices. Also with screenshots to understand the common problems.emmapeelemmapeel