The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-06-20T18:34:40Zhttps://gitlab.torproject.org/tpo/web/manual/-/issues/145Improve this phrase in TB mobile manual2023-06-20T18:34:40ZGusImprove this phrase in TB mobile manualThis paragraph is very redundant ("if you know..."), we should improve it: https://tb-manual.torproject.org/mobile-tor/
>If you know that your connection is censored, you should select the settings icon. Tor Browser will take you throug...This paragraph is very redundant ("if you know..."), we should improve it: https://tb-manual.torproject.org/mobile-tor/
>If you know that your connection is censored, you should select the settings icon. Tor Browser will take you through a series of configuration options. The first screen will tell you about the status of the Tor Network and provide you the option to configure a Bridge ('Config Bridge'). If you know your connection is censored, or you have tried and failed to connect to the Tor network and no other solutions have worked, tap on 'Config Bridge'. You will then be taken to the Circumvention screen to configure a pluggable transport.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41188Migrate new machine docs to new swap file policy2023-05-25T15:05:34ZJérôme Charaouilavamind@torproject.orgMigrate new machine docs to new swap file policyFollowing adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should implement the changes to our new-machines documentation and templates.
- [x] new gane...Following adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should implement the changes to our new-machines documentation and templates.
- [x] new ganeti instance docs
- [x] new physical machine docs
- [x] fabric installer disk templatesJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41187Document swap file resizing2023-05-24T21:55:16ZJérôme Charaouilavamind@torproject.orgDocument swap file resizingFollowing adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should document how to resize the ganeti installer-created swap file for instances that requi...Following adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should document how to resize the ganeti installer-created swap file for instances that require more swap space.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40866Remove `Using ansible to set up a nightly build machine` from README2023-06-07T21:43:13ZboklmRemove `Using ansible to set up a nightly build machine` from READMEIn aadd6feb0302552da49eac8cae440c1510a436f3 we removed
`tools/ansible/roles/tbb-nightly-build`, but forgot to remove the section
`Using ansible to set up a nightly build machine` in the README file.In aadd6feb0302552da49eac8cae440c1510a436f3 we removed
`tools/ansible/roles/tbb-nightly-build`, but forgot to remove the section
`Using ansible to set up a nightly build machine` in the README file.https://gitlab.torproject.org/tpo/core/arti/-/issues/867Update in-tree docs to refer to TROVE2023-09-13T17:33:22ZIan Jacksoniwj@torproject.orgUpdate in-tree docs to refer to TROVEAt least our what do we support doc, and perhaps a general readme, should have appropriate link(s) to TROVE.At least our what do we support doc, and perhaps a general readme, should have appropriate link(s) to TROVE.https://gitlab.torproject.org/tpo/web/community/-/issues/313Update Tor abuse templates with more updated links2023-06-08T19:12:18ZemmapeelUpdate Tor abuse templates with more updated linksThe documentation at https://community.torproject.org/relay/community-resources/tor-abuse-templates/ is very interesting for our relay operators, but it has lots of links to documents on our old website.
Some of the documents do not hav...The documentation at https://community.torproject.org/relay/community-resources/tor-abuse-templates/ is very interesting for our relay operators, but it has lots of links to documents on our old website.
Some of the documents do not have a proper new document, maybe we should wait till we have a dev portal and reproduce them there:
- https://www.torproject.org/projects/tordnsel.html.en (maybe we should have an entry on the glossary about it?)
- https://www.torproject.org/about/torusers.html.en - isn't this a bit like our personas? or maybe we have a newer link to our users
- https://2019.www.torproject.org/about/overview.html.en / we ask people to read this page to have an idea of what tor is. do we have a better page for it? maybe our main page?
Thanks to tornth for starting the updates!https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40861Add README to update_responses to document downloads.json etc2023-08-26T05:46:31ZruihildtAdd README to update_responses to document downloads.json etcCurrently, we use the tag link using the following format for the Github release link, as follow:
`https://github.com/mullvad/mullvad-browser/releases/tag/mullvad-browser-102.11.0esr-12.0-1-build1`
This is inconvenient for:
- downstrea...Currently, we use the tag link using the following format for the Github release link, as follow:
`https://github.com/mullvad/mullvad-browser/releases/tag/mullvad-browser-102.11.0esr-12.0-1-build1`
This is inconvenient for:
- downstream packagers using the tag to download from the GitHub page new releases
- dynamically linking our changelog on our website
- generally being able to look at the release version from the link
This is why, we have changed the release tags to the following format:
`https://github.com/mullvad/mullvad-browser/releases/tag/12.0.6`
This needs to be updated when generating the XML update responses.
--------------
Additional considerations (Nice to have if trivial to add)
- For now, we're manually adding this tag to the branch pushed on Github. If this can someone get added automatically, then it's a win.
- https://cdn.mullvad.net/browser/update_responses/update_1/release/downloads.json actually contains a tag, which is not present on the branch moved to our Github repository. Could this tag be changed to the same format `XX.X.X`?
EDIT: The tag referenced in downloads.json is not self-evident as to what it is for, we should add some small documentation there for users that go looking for it.https://gitlab.torproject.org/tpo/web/support/-/issues/327Dead link to blog2023-11-06T19:25:02ZslrslrDead link to bloghttps://support.torproject.org/tbb/tbb-22/
contains 404 not found link to https://blog.torproject.org/why-tor-is-slow
It is not even on archive: https://web.archive.org/web/20220715000000*/https://blog.torproject.org/why-tor-is-slow
I a...https://support.torproject.org/tbb/tbb-22/
contains 404 not found link to https://blog.torproject.org/why-tor-is-slow
It is not even on archive: https://web.archive.org/web/20220715000000*/https://blog.torproject.org/why-tor-is-slow
I am unsure if the article is still present: https://www.ecosia.org/search?addon=firefox&q=tor+blog+why+tor+is+slow+site%3Ablog.torproject.org
Though the https://support.torproject.org/tbb/tbb-22/ should contain some more answer to the question in its title..https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40090Add links to all specs available on collector page2023-09-19T09:32:05ZGeorg KoppenAdd links to all specs available on collector pageWhile trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is goo...While trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is good. However, we should collect the links to all the missing specs and add them there, too, so we have at least one canonical place where all specs are just one click away.
Oh, and while we are at it we should replace those old gitweb links.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40089Go over bridge descriptor spec and fix it up where needed2023-06-15T10:29:39ZGeorg KoppenGo over bridge descriptor spec and fix it up where neededWe removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and ...We removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and make sure everything is up-to-date.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/14Reference the project in the upcoming Tor Development Portal2023-05-09T17:32:05ZSilvio RhattoReference the project in the upcoming Tor Development PortalReference the project in the upcoming [Tor Development Portal](https://gitlab.torproject.org/tpo/web/dev/-/issues/6).Reference the project in the upcoming [Tor Development Portal](https://gitlab.torproject.org/tpo/web/dev/-/issues/6).https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/10GitLab pages with l10n plugin2023-05-09T17:32:05ZSilvio RhattoGitLab pages with l10n pluginSetup GitLab pages with l10n plugin and using [onion-mkdocs](https://rhatto.pages.torproject.net/onion-mkdocs/).Setup GitLab pages with l10n plugin and using [onion-mkdocs](https://rhatto.pages.torproject.net/onion-mkdocs/).https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/9Add screenshots in the documentation2023-05-09T17:32:05ZSilvio RhattoAdd screenshots in the documentationAdd screenshots in the documentation.Add screenshots in the documentation.https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/8Documentation about Docker and Docker Compose installation2023-05-09T17:32:05ZSilvio RhattoDocumentation about Docker and Docker Compose installationAdd documentation (or references) about how install Docker and Docker Compose on popular OSes.Add documentation (or references) about how install Docker and Docker Compose on popular OSes.https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/7Support for documentation in various languages2023-05-09T17:32:05ZSilvio RhattoSupport for documentation in various languagesAdd support for documentation in various languages
One possible way is to have one document per language (like `README.pt-BR.md` etc).Add support for documentation in various languages
One possible way is to have one document per language (like `README.pt-BR.md` etc).https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/6Add reference to the onion-desktop project2023-05-09T17:32:06ZSilvio RhattoAdd reference to the onion-desktop projectAdd reference to the [onion-desktop](https://github.com/scanlime/onion-desktop) project.Add reference to the [onion-desktop](https://github.com/scanlime/onion-desktop) project.https://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/2LICENSE and other metafiles2023-05-15T09:49:43ZSilvio RhattoLICENSE and other metafilesAdd LICENSE and other metafiles.Add LICENSE and other metafiles.https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40088Bridge running flag is determined from bridgestrap tests, not bridge networks...2023-05-04T16:50:26ZGeorg KoppenBridge running flag is determined from bridgestrap tests, not bridge networks statushttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/112#note_2857497 claims we get the "running" flag from bridgestrap tests, which seems reasonable given the code linked to. However, the Onionoo documentation on the [Metrics...https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/112#note_2857497 claims we get the "running" flag from bridgestrap tests, which seems reasonable given the code linked to. However, the Onionoo documentation on the [Metrics website](https://metrics.torproject.org/onionoo.html) says: "Boolean field saying whether this bridge was listed as running in the last bridge network status."
It seems we need to change the documentation here.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/community/policies/-/issues/4Policies lack version number2023-05-25T18:24:44ZSilvio RhattoPolicies lack version numberIt would be great if each policy had a version number.
/cc @gus @arma @gkIt would be great if each policy had a version number.
/cc @gus @arma @gkhttps://gitlab.torproject.org/tpo/community/policies/-/issues/3Setup GitLab Pages for the Policies repository2023-11-12T17:56:06ZSilvio RhattoSetup GitLab Pages for the Policies repositoryWe could easily convert the text files to markdown and use something like [Onion MkDocs](https://gitlab.torproject.org/rhatto/onion-mkdocs) to render a fancy version of the policies repository.We could easily convert the text files to markdown and use something like [Onion MkDocs](https://gitlab.torproject.org/rhatto/onion-mkdocs) to render a fancy version of the policies repository.GusGus