tpo issueshttps://gitlab.torproject.org/tpo/web/tpo/-/issues2021-09-08T19:36:37Zhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/56Add security policy link to https://www.torproject.org/contact/2021-09-08T19:36:37Zc1e0Add security policy link to https://www.torproject.org/contact/In https://2019.www.torproject.org/about/contact.html.en, you can find the sentence "Find links to acknowledgments and our security policy in machine readable form [here](https://www.torproject.org/.well-known/security.txt)."
Clicking on...In https://2019.www.torproject.org/about/contact.html.en, you can find the sentence "Find links to acknowledgments and our security policy in machine readable form [here](https://www.torproject.org/.well-known/security.txt)."
Clicking on "here" yields a 404 page.
Ideally, the right security policy link should be added to https://www.torproject.org/contact/https://gitlab.torproject.org/tpo/web/tpo/-/issues/375Improve visibility of Members2024-02-12T18:24:13Zal smithImprove visibility of Members# Problem
We have two ways organizations can financially support the Tor Project: as a *[sponsor](https://www.torproject.org/about/sponsors/)* or a *[member](https://www.torproject.org/about/membership/)*.
The difference between sponsor...# Problem
We have two ways organizations can financially support the Tor Project: as a *[sponsor](https://www.torproject.org/about/sponsors/)* or a *[member](https://www.torproject.org/about/membership/)*.
The difference between sponsors and members has not been clear to organizations who want to support Tor. Those who *do* support Tor have noted that they don't see their organization listed on our site (even when they are there) because they are confused between whether their organization is a sponsor or a member. This was been a point of refusal to renew for one member.
"Membership" has also caused a few issues on the accounting level, specifically about membership time frames--we've used this term with flexibility, including flexible time frames for renewal, but a membership in an accounting term needs to be more formal with specific timeframes.
This problem brings up some questions:
- How do we better recognize our Members and make it easier to find out that they support Tor?
- Can we combine the Sponsors and Membership page?
- If so, how do we delineate between Sponsors and Members?
- Do we *need* to delineate between Sponsors and Members? What do we gain or lose in either direction?
Below, I am proposing a change in the way we *publicly* recognize organizations and companies that support the Tor Project.
# Proposal
* We should diminish the *public* differentiation between 'sponsors' and 'members' by using the word "supporters," a term that encompasses all organizations that make donations to the Tor Project. (Sponsors and sponsor numbers will remain an internal mechanism for distinguishing discrete funded projects. This external change does not change our internal accounting and project management practices.)
* We should combine the `/about/sponsors` and `/about/membership` pages into one page, `about/supporters`.
* We should continue to use annual support renewal, and 'onion levels' as mechanisms of engaging corporate donors, including retaining these levels in a `about/supporters` page.
# Benefits of merging "sponsors" and "membership" into "supporters"
* Reduces confusion for corporate, foundation, and institutional donors about "what they are"
* We're able to continue to utilize mechanisms that *have* been working in the membership program: engaging corporations, giving them visibility and benefits, offering clear levels of support, and asking for them to renew their gifts annually.
* Current groups that are listed on the /membership page gain more visibility.
* Opens the door for "membership" terminology to be used with individual donors in the future if we decide to.
# Suggested page changes
When combining `/about/sponsors` and `/about/membership`, my vision is that we use visual size to differentiate the different membership levels, similar to how `/about/membership` does so now.
Below is my extremely rudimentary idea.
![Untitled](/uploads/91b9a6b3e96e22919ffc97d953e62f83/Untitled.png)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2024-02-07https://gitlab.torproject.org/tpo/web/tpo/-/issues/241Add board members to core & remove board section from /about/people2022-06-21T23:08:05ZGusAdd board members to core & remove board section from /about/peopleCollapsing/Expanding the bios may be a little weird in the grid, but I think it would be great to standardize the panel design (perhaps with a special flag or tag for board members), and to consider an alternative to the anchor links to ...Collapsing/Expanding the bios may be a little weird in the grid, but I think it would be great to standardize the panel design (perhaps with a special flag or tag for board members), and to consider an alternative to the anchor links to break the page up a little more.
https://gitlab.torproject.org/tpo/web/tpo/-/issues/228#note_2750665Isabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/tpo/web/tpo/-/issues/172[UX] Edge alignment in the website2021-08-31T18:14:30Zriyajawandhiya[UX] Edge alignment in the website**What is the user problem?**
alignment is vitally important in design as:
1. allows you to arrange elements in a way that matches how people naturally scan the page
2. helps balance your image so that it’s visually appealing
3. create...**What is the user problem?**
alignment is vitally important in design as:
1. allows you to arrange elements in a way that matches how people naturally scan the page
2. helps balance your image so that it’s visually appealing
3. creates a visual connection between related elements
![image](/uploads/67c28bd465e629e8fd70b6169e1b555d/image.png)
The screenshot is taken from [downloads website](https://www.torproject.org/download/)
**What needs to be done?**
naturally positions elements against a margin that matches up with their outer edges. I have drawn the differences.
- Red - Vertical alignment of the text - justified text to be used
- Yellow - Center-line acting as the pivot - every gap must be equidistant
- Blue - Horizontal alignment of the image - place image at equidistant locationhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/168[Download/Languages] Update the phrase 'Tor Browser is now available in 32 di...2021-04-05T21:38:38Zchampionquizzerchampionquizzer@torproject.org[Download/Languages] Update the phrase 'Tor Browser is now available in 32 different languages'Tor Browser is currently available in 35 different languages (yaay!) and we need to update the phrase -- 'Tor Browser is now available in 32 different languages' -- on the download page, here: https://www.torproject.org/download/languages/Tor Browser is currently available in 35 different languages (yaay!) and we need to update the phrase -- 'Tor Browser is now available in 32 different languages' -- on the download page, here: https://www.torproject.org/download/languages/https://gitlab.torproject.org/tpo/web/tpo/-/issues/147Verifying-signatures needs some work2020-12-21T17:12:26ZMike PerryVerifying-signatures needs some workhttps://www.torproject.org/docs/verifying-signatures.html.en is ridiculously complicated and stuffed with tons of irrelevant information.
We should break it into 2 pages. The list of keys that signs sub-components and/or email should be...https://www.torproject.org/docs/verifying-signatures.html.en is ridiculously complicated and stuffed with tons of irrelevant information.
We should break it into 2 pages. The list of keys that signs sub-components and/or email should be on a completely separate page. The only keys on this page should be those that actually sign user-facing packages: TBB and (maybe) the vidalia expert bundles.
The page should walk the user through verifying a signature of a specific package for each platform. The page should focus on only one key and only one package. This package should probably be TBB.
Also, much of the material on this page is out of date. For example, the Mac utilities are completely different now, are hosted at a new URL, and now have a GUI that handles the key import process (but sadly not package signature verification). They do at least put the gpg binary into the system path, so you no longer have to grovel through /Applications in order to find it.Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/tpo/web/tpo/-/issues/145Make the various javascript on Tor sites be LibreJS-compatible?2021-09-08T19:45:54ZRoger DingledineMake the various javascript on Tor sites be LibreJS-compatible?On reading https://www.gnu.org/software/repo-criteria.html (as pointed out on tor-talk), I came across "B0": "All code sent to the user's browser must be free software and labeled for LibreJS or other suitable free automatic license anal...On reading https://www.gnu.org/software/repo-criteria.html (as pointed out on tor-talk), I came across "B0": "All code sent to the user's browser must be free software and labeled for LibreJS or other suitable free automatic license analyzer".
I don't know anything about the politics behind libre JS or the like, but I know some of the Tor sites use JavaScript, and I also know we're not meaning to keep any of it non-free.
Is there some enthusiastic free software zealot out there who wants to inventory the javascript used on various Tor sites, and move us closer to labeling it all as free?traumschuletraumschulehttps://gitlab.torproject.org/tpo/web/tpo/-/issues/141adjust text shown on screen based on size of text2021-04-13T00:09:46ZTracadjust text shown on screen based on size of textWhen viewing this web page I find I have to increase the size of text because I have poor vision.
If I use the control-+ to increase the text size, your web page forces me to scroll the window left to right to read lines of text.
Use t...When viewing this web page I find I have to increase the size of text because I have poor vision.
If I use the control-+ to increase the text size, your web page forces me to scroll the window left to right to read lines of text.
Use the method that wikipedia.com uses for displaying the screen.
wikipedia.com adjusts the text to fit within the displayed window by making lines shorter as text size increases and making lines longer as text size increases.
Go to wikipedia.com and view any entry. Then do a control-+ to increase text size and see what it does. Then do a control-- to reduce size of text and see what it does. NOTE: I am using Ubuntu 16.04 - hence my control-+ increases text size and control-- will decrease text size. I don't know what keys are used to do this with other operating systems.
Just an idea from a 71 year old with bad eyes.
**Trac**:
**Username**: efitterytraumschuletraumschulehttps://gitlab.torproject.org/tpo/web/tpo/-/issues/137Usability of MacOS installation process2021-02-26T12:37:36ZcypherpunksUsability of MacOS installation processUsability of MacOS installation process
Consequence: User is unable to verify package signature
Steps to reproduce:
1. Download Tor browser
2. Go to https://www.torproject.org/docs/verifying-signatures.html.en for instructions.
3...Usability of MacOS installation process
Consequence: User is unable to verify package signature
Steps to reproduce:
1. Download Tor browser
2. Go to https://www.torproject.org/docs/verifying-signatures.html.en for instructions.
3. Read the block of text for MacOS and Linux.
4. Follow the link at the bottom of that section to:
https://www.gnupg.org/documentation/
5. Struggle with the information on that page.
6. Try to go to the SourceForge link there for GPG Mac download.
uBlock Origin blockade: uBlock Origin has prevented the following page from loading:http://macgpg.sourceforge.net/
Because of the following filter
| sourceforge.net^$other^ |
|-------------------------|
Found in: uBlock filters – Badware risks
7. Give up.
----
What should have happened:
Follow the GPGTools link at the top of the Tor page's Mac/Linux instruction block.
https://www.torproject.org/docs/verifying-signatures.html.en
----
Suggested fixes:
* Divide the MacOS instructions from the Linux instructions.
* Add numbers to the procedures... something like this, for the MacOS:
1. Download Tor Browser and save the signature.asc to your Desktop.
1. Download and install GPGTools.
1. Open a Terminal window (Terminal is in /Applications/Utilities or find it with search)
1. Paste the following into the terminal: [... ...]
...adding links appropriately in the procedure
* Use link colors to help people visually scan through the pages. Take advantage of the human tendency to skim over text and just read the bold, colored stuff:
-Use a color with better contrast against black (the green is wonderful but too dark for good contrast)
-Include more keywords in links
* Related installation issue that probably belongs somewhere else:
Opening the DMG and installing the Tor Browser: The application file shows a file modification date of Dec 31, 1999, so it's difficult to know whether the downloaded one is newer than one I have already.
No version number is in the file name.
Get Info (cmd-I) (which not every Mac user knows about) does show a version number, and it also shows the file has a creation date of Dec 31, 2000, which is before the mod date. The weird dates might cause version control issues but are also likely to worry people who see them.traumschuletraumschulehttps://gitlab.torproject.org/tpo/web/tpo/-/issues/134Add link to Tor SlackBuild on download-unix.html.en2021-09-08T12:48:25ZcypherpunksAdd link to Tor SlackBuild on download-unix.html.enI thought it would be nice to add link to the [Tor SlackBuild](https://slackbuilds.org/repository/14.2/network/tor/) on [download-unix.html.en](https://www.torproject.org/download/download-unix.html.en). The SlackBuild works fine and is ...I thought it would be nice to add link to the [Tor SlackBuild](https://slackbuilds.org/repository/14.2/network/tor/) on [download-unix.html.en](https://www.torproject.org/download/download-unix.html.en). The SlackBuild works fine and is updated regularly.
The code would be something like this:
```
<tr class="beige">
<td align="center"><img src="$(IMGROOT)/distros/slackware.png" alt="Slackware"></td>
<td>Slackware</td>
<td colspan="2"><a href="https://slackbuilds.org/repository/14.2/network/tor/">SlackBuilds.org</a></td>
<td>
<a href="<page docs/tor-doc-unix>">Linux/BSD/Unix</a><br>
</td>
</tr>
```
If nobody wants to design a new logo, there's generic.png in /images/distros/ folderhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/40UI bugs /press2021-09-15T19:03:16ZAntonelaantonela@torproject.orgUI bugs /press* [ ] release panels don't stack very neatly on medium-size screens (and could use some padding between rows on small screens too): https://www.dropbox.com/s/gnrxlckjibjbcdb/Screenshot%202019-02-12%2015.54.36.png?dl=0
* [ ] Preamble te...* [ ] release panels don't stack very neatly on medium-size screens (and could use some padding between rows on small screens too): https://www.dropbox.com/s/gnrxlckjibjbcdb/Screenshot%202019-02-12%2015.54.36.png?dl=0
* [ ] Preamble text on all subpages is a little big on mobile, and could be reduced at a suitable breakpoint: https://www.dropbox.com/s/6t6s4kcoj5n8sxz/Screenshot%202019-02-12%2015.53.21.png?dl=0donutsdonuts