The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-08-05T08:31:28Zhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40037Go through issues raised by translators in Transifex2021-08-05T08:31:28ZemmapeelGo through issues raised by translators in TransifexI started going through the issues translators raise in transifex, it takes some time, so I decided to open this ticket to account for the work.
Pending issues:
- [x] tpo:/about/history: "The network needed to be operated by entities wi...I started going through the issues translators raise in transifex, it takes some time, so I decided to open this ticket to account for the work.
Pending issues:
- [x] tpo:/about/history: "The network needed to be operated by entities with diverse interests and trust assumptions, and the software needed to be free and open to maximize transparency and separation." - [Separation? of what, concerns maybe? is not clear what does it mean regarding free and open software. Also, maybe is 'open source', not 'open'.](https://gitlab.torproject.org/tpo/web/tpo/-/issues/192)
- [ ] "In 2007, the organization began developing bridges to the Tor network to address censorship, such as the need to get around government firewalls, in order for its users to access the open web." - needs to be rephrased to be better understood:'... began developing bridges as an addition to the Tor network to provide solutions against censorship, such as government firewalls, to help users to maintain access to the open web.
- [x] Suggest feedback: change 'suggest feedback' on our lektor templates for 'give feedback' or 'leave a suggestion' (see in the bottom at for example: https://support.torproject.org/misc/bug-or-feedback/ )
- [x] in https://tb-manual.torproject.org/circumvention/ we say: `Or, if you have Tor Browser running, click on "Preferences" in the hamburger menu and then on "Tor" in the sidebar.` But there is no "Tor" sidebar in preferences.
- [ ] [main ticket](https://gitlab.torproject.org/tpo/web/manual/-/issues/94) On the manual, at https://tb-manual.torproject.org/mobile-tor/ , we say: When Tor Browser is running, you would see so in your phone's notification panel along with the button "NEW IDENTITY". But:
- to see the "new identity" button you must expand the notification.
- better: "in your device's notification panel"Sponsor 9 - Phase 5 - Usability and Community Intervention on Support for Democracy and Human Rightsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40023Go through process of distributing private bridges2021-07-15T17:32:56ZPhilipp Winterphw@torproject.orgGo through process of distributing private bridgesOver at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-tr...Over at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-trivial number of censored users. Once we did, we need to document our experience and iteratively improve the process.Sponsor 30 - Objective 2.3GusGushttps://gitlab.torproject.org/tpo/web/manual/-/issues/142Google Play instructions need updating2023-07-03T14:48:49ZemmapeelGoogle Play instructions need updatingreported by translator olavinto, thanks!
The instructions for updating and uninstalling tor Browser with Google Play at
https://gitlab.torproject.org/tpo/web/manual/-/blob/main/content/mobile-tor/contents.lr
Need to be updated:
```...reported by translator olavinto, thanks!
The instructions for updating and uninstalling tor Browser with Google Play at
https://gitlab.torproject.org/tpo/web/manual/-/blob/main/content/mobile-tor/contents.lr
Need to be updated:
```
12:09 < olavinto[m]> * This phrase: "Tap on the hamburger menu next to the search bar and navigate to "My apps & games" >
"Installed". Select Tor Browser from the list of installed apps, then press the "Uninstall" button." has not been
exactly accurate for a while. The hamburger menu is still there although these days it's the logged in user's
icon and "My apps & games" has been "Manage apps and device" for a long time, and lastly, there is no "Installed"
12:09 < olavinto[m]> section under it anymore either but isntead there is a "Manage" (not the default tab, default is an overview) tab
and an "Installed" filtering option under that. Mainly that.
12:16 < olavinto[m]> Basically the whole section related to uninstalling the mobile app via Google Play now reads about like this in
Finnish: "Tap the user icon next to the search bar and select "Maintain apps and devices" > "Maintenance" from
the menu that opens. By default, the filtering options at the top are set to show only apps for which an update
is available. You can also search for Tor browser from the search field on the front page if you have a lot
12:16 < olavinto[m]> of applications on your device."
12:19 < olavinto[m]> s/By default, the filtering options at the top are set to show only apps for which an update is available.//
```championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/20637Grammar issue in HiddenServiceSingleHopMode documentation2021-07-22T16:22:54ZfkGrammar issue in HiddenServiceSingleHopMode documentationCurrently the tor man page contains the sentence:
```
Since a Single Onion is non-anonymous, you can not to run an
anonymous SOCKSPort on the same tor instance as a Single Onion service.
```
The attached patch is one way to fix it.Currently the tor man page contains the sentence:
```
Since a Single Onion is non-anonymous, you can not to run an
anonymous SOCKSPort on the same tor instance as a Single Onion service.
```
The attached patch is one way to fix it.Tor: 0.2.9.x-finalhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/35Hackweek 2023 documentation2023-11-30T17:35:12ZSilvio RhattoHackweek 2023 documentationDocument the 2023 Hackweek.Document the 2023 Hackweek.Hackweek 2023Silvio RhattoSilvio Rhatto2023-12-07https://gitlab.torproject.org/tpo/community/hackweek/-/issues/8Hackweek 2023: call for proposals message2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: call for proposals messageSend the call for proposals email.Send the call for proposals email.Hackweek 2023Silvio RhattoSilvio Rhatto2023-08-30https://gitlab.torproject.org/tpo/community/hackweek/-/issues/6Hackweek 2023: call for proposals text2023-11-30T16:17:39ZSilvio RhattoHackweek 2023: call for proposals textCreate call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can l...Create call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can learn to help with this effort".
* [x] Why: goal of the Hackweek:
* [x] Explore how documentation is working or not in your projects.
* [x] Do problem-solving around documentation in the organization and projects we maintain.
* [x] Sharing the problems we have with documentation at Tor.
* [x] When: timeline:
* [x] Previous all hands meeting: people present the project they will work on.
* [x] During the Hackweek: people work on whatever they want related to
documentation (4-day Hackweek, from Mon to Thu).
* [x] Next all hands meeting: people present the project they worked on.
* [x] How: how the Hackweek is going to work (when, where):
* [x] People will add proposals to [Hackweek's issue tracker][] using an
[issue template][] and others can join to work together.
* [x] In order to join a proposal, subscribe yourself to it's ticket.
* [x] Accepting documentation in all formats, including videos/screencasts,
including things like "a video tutorial on my documentation best
practices".
* [x] References:
* [x] [Diátaxis](https://diataxis.fr/): The Grand Unified Theory of Documentation.
* [x] [How to pick up a project with an audit](https://bluesock.org/~willkg/blog/dev/auditing_projects.html)
[Hackweek's issue tracker]: https://gitlab.torproject.org/tpo/community/Hackweek/-/issues
[issue template]: tpo/community/hackweek#10Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-08-23https://gitlab.torproject.org/tpo/community/hackweek/-/issues/3Hackweek 2023: create organization tickets2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: create organization ticketsHackweek 2023Silvio RhattoSilvio Rhatto2023-06-30https://gitlab.torproject.org/tpo/team/-/issues/190Hackweek 2023: create organization tickets2023-06-27T16:43:46ZSilvio RhattoHackweek 2023: create organization ticketsSilvio RhattoSilvio Rhatto2023-06-30https://gitlab.torproject.org/tpo/community/hackweek/-/issues/7Hackweek 2023: save the date message2023-11-30T16:17:39ZSilvio RhattoHackweek 2023: save the date messageSend a mail now so people have time to organize (save the date).Send a mail now so people have time to organize (save the date).Hackweek 2023tylertyler2023-07-05https://gitlab.torproject.org/tpo/core/tor/-/issues/19294Have tor-guts cover how to use OS functionality from Tor2021-07-22T16:23:45ZNick MathewsonHave tor-guts cover how to use OS functionality from TorThis should cover all our compatibility layers, including compat*, address.c, and the relevant parts of util*This should cover all our compatibility layers, including compat*, address.c, and the relevant parts of util*Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/19295Have tor-guts cover our cryptography functions2021-07-22T16:23:15ZNick MathewsonHave tor-guts cover our cryptography functionsWe should write a guide to where to find the cryptography functions in tor. This doesn't need to be a replacement for the doxygen but it should let you know where to look.We should write a guide to where to find the cryptography functions in tor. This doesn't need to be a replacement for the doxygen but it should let you know where to look.Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/19297Have tor-guts cover string-related util functions2021-07-22T16:23:15ZNick MathewsonHave tor-guts cover string-related util functionsTor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/19296Have tor-guts cover time-related util functions2021-07-22T16:23:15ZNick MathewsonHave tor-guts cover time-related util functionsTor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/19298Have tor-guts describe containers2021-07-22T16:23:16ZNick MathewsonHave tor-guts describe containersTor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25284hidden-service-dir description in dir-spec should reference HSDir protovers2021-09-30T13:50:08Zteorhidden-service-dir description in dir-spec should reference HSDir protoversSince 0.3.0, tor supports HSDir versions 2 and 3 by default, and advertises no hidden-service-dir VersionNums.
But the spec says:
"If any VersionNum(s) are specified, this router supports those descriptor versions. If none are specified...Since 0.3.0, tor supports HSDir versions 2 and 3 by default, and advertises no hidden-service-dir VersionNums.
But the spec says:
"If any VersionNum(s) are specified, this router supports those descriptor versions. If none are specified, it defaults to version 2 descriptors"Tor: 0.3.4.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/20486HiddenServiceDirectory is created if it doesn't exist2021-07-22T16:22:54ZteorHiddenServiceDirectory is created if it doesn't existSplit off legacy/trac#20484
* Update the man page, which incorrectly says that HiddenServiceDirectory must exist - tor creates the HiddenServiceDirectory if it doesn't existSplit off legacy/trac#20484
* Update the man page, which incorrectly says that HiddenServiceDirectory must exist - tor creates the HiddenServiceDirectory if it doesn't existTor: 0.3.0.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/12670HiddenServicePort TARGET IPv6 address2021-07-22T16:26:02ZgrarpampHiddenServicePort TARGET IPv6 addressThe man page HiddenServicePort does not say anything about TARGET being an IPv6 address. Since Tor is becoming IPv6 enabled it probably should (ie: ::1, and precedence). There are some combinations to consider supporting if not already d...The man page HiddenServicePort does not say anything about TARGET being an IPv6 address. Since Tor is becoming IPv6 enabled it probably should (ie: ::1, and precedence). There are some combinations to consider supporting if not already done (latter dependant on host if tor is not bound to both)...
4 -> TARGET 4
6 -> TARGET 6
4 -> TARGET 6
6 -> TARGET 4Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/tpo/web/manual/-/issues/88How to install Tor Browser on Linux is not working or clear enough2021-09-04T13:26:17ZGusHow to install Tor Browser on Linux is not working or clear enoughToday on #tor channel we had a Ubuntu user that couldn't start Tor Browser.
We need to update our instructions on Tor Browser User Manual to make it more clear how they can launch Tor Browser.
```
You'll need to tell your GNU/Linux that...Today on #tor channel we had a Ubuntu user that couldn't start Tor Browser.
We need to update our instructions on Tor Browser User Manual to make it more clear how they can launch Tor Browser.
```
You'll need to tell your GNU/Linux that you want the ability to execute shell scripts from the graphical interface or the command line. Navigate to the newly extracted Tor Browser directory. Right click on start-tor-browser.desktop, open Properties or Preferences and change the permission to allow executing file as program. Double-click the icon to start up Tor Browser for the first time.
Note: On Ubuntu and some other distros if you try to launch the start-tor-browser.desktop file a text file might open up. To change this behavior and launch Tor Browser instead, follow this: Open "Files" (GNOME Files/Nautilus) → open Preferences → go to the 'Behavior' Tab → Select "Run them" or "Ask what to do" under "Executable Text Files". If you choose the latter click on "Run" after launching the start-tor-browser.desktop file.
```
https://tb-manual.torproject.org/installation/
ps: This issue is not open for Outreachies.championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/28How we are going to use Gitlab for organizing projects and Tor's work2020-11-13T17:50:19ZGabagaba@torproject.orgHow we are going to use Gitlab for organizing projects and Tor's work- [ ] ***CONVERT THIS THREAD INTO DOCUMENTATION* (Tails example https://tails.boum.org/contribute/working_together/GitLab/)**
Attention @tpo/core @tpo/ux @tpo/metrics @tpo/anti-censorship @tpo/community @tpo/applications @tpo/tpa
We ...- [ ] ***CONVERT THIS THREAD INTO DOCUMENTATION* (Tails example https://tails.boum.org/contribute/working_together/GitLab/)**
Attention @tpo/core @tpo/ux @tpo/metrics @tpo/anti-censorship @tpo/community @tpo/applications @tpo/tpa
We have [user stories](#26) for how we need to use Gitlab. I'm writing down here a proposal on how to use Gitlab, open up for discussion.
**SPONSOR/PROJECT PLANNING AND WORK**
- To track a sponsor's project, including how much time there is for the project and what is still not assigned (pm user stories #26):
Create a milestone per objective of the project OR for the whole project, depending on size. The milestone should be in the group that includes all groups working on this project. Examples:
* For OnionPerf https://gitlab.torproject.org/groups/tpo/metrics/-/milestones/1
* For objectives in the Sponsor 30: https://gitlab.torproject.org/groups/tpo/-/milestones/4
Each milestone will have:
* dates when the project/objective starts or end
* information about the project or objective
* all the tickets that need to be completed with this milestone
To mark that a ticket could be in a specific sponsor/project:
* Mark that ticket with the label for the sponsor. For example label 'Sponsor 55'. The tickets with this label may not go into the sponsor but are a possible fit for it.
To divide objectives/tickets into smaller tasks (dev stories for sponsor planning):
* Create an issue for that objective with the label 'project'
* In that issue write down a list of "children" that are the tasks that need to be completed. Each child is a new issue. Example: https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/31274
**RELEASE PLANNING**
To decide which open bugs must be finished before we can put out the next release.
* Create a milestone for each release. The milestone will be at the level of the team's group or project. For example:
* Tor 0.4.4 https://gitlab.torproject.org/groups/tpo/-/milestones/tor-044x-final?title=Tor%3A+0.4.4.x-final
* Tor unspecified https://gitlab.torproject.org/groups/tpo/-/milestones/tor-unspecified?title=Tor%3A+unspecified
**TEAM WORK**
To organize work per team or per project (TBB, tor, onionperf, etc):
* Create a kanban board where we can set stacks with:
* backlog: indicates all the work that we have planned to do
* next: indicates all the work that we are doing in the next sprint. (decide with your lovely PM and your team how long your sprint should be)
* doing: indicates all the tickets that people are working on right now
* needs review: some teams needs this label to indicate the tickets/issues that needs somebody to review them.
* Each "stack" in the board will be a label. The labels that we are all using for this are: backlog, next, doing, needs review.
* The issues at the top of the stack are the ones with the most priority in that stack.
For example:
1. OnionPerf https://gitlab.torproject.org/tpo/metrics/onionperf/-/boards
1. SysadminXs https://gitlab.torproject.org/groups/tpo/tpa/-/boards
1. Network https://gitlab.torproject.org/groups/tpo/core/-/boards
**To decide on what to work next**
* There is this neat place where you can see all the issues assigned to you, issues that you were mentioned in, merge requests. https://gitlab.torproject.org/dashboard/todos
**To assign reviews**
* Issues in Gitlab do not have a review but merge requests do have them. To work around this (as we still need to mark down issues for review) we will have labels at the project or group level (not TPO level) to mark who is reviewing which issue. The labels will be "review-by-X" with X the name of the person.
**COMMUNICATION BETWEEN TEAMS**
In an issue you can mention a group (for example @core) and that issue gets into the dashboard of all the people in that group. Use this power with responsability.
**REPORTING BUGS**
We still do not have signups in Gitlab so for now people have to send a mail to gitlab-admin@torproject.org to be able to get an account in Gitlab. Once they have an account they can easily report a bug in https://gitlab.torproject.org/groups/tpo/-/boards or https://gitlab.torproject.org/groups/tpo/-/issues
I'm not totally sure if that board in TPO is the best one so we need to think a little more about how to show all the work happening as well as all the work to be done in the whole organization. https://gitlab.torproject.org/groups/tpo/-/boards
I would like to add issue templates to all projects so people can easily follow the template to post the information that we need from the issue. Example: https://gitlab.torproject.org/ahf/lobby/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
**Templates** to report a bug should contain:
* summary
* steps to reproduce
* expected results
* actual results
* version that the bug was found in
For people to search between all the issues in TPO (if they for example want to check all the issues they authored) they can do it in https://gitlab.torproject.org/groups/tpo/-/issues
**VOLUNTEERING WORK**
To help volunteers I think we could have labels that help people find something they can collaborate to:
* Documentation
* 1st contribution
**We are discussing email interaction with Gitlab on #29**
**We are discussing labels in #4**
Please, make commments, things that may not work, something that I maybe forgot.Gabagaba@torproject.orgGabagaba@torproject.org