Custom Query (74 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 15 of 74)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#3893 Verifying-signatures needs some work arma Webpages/Website website redesign
Description

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.

#14686 Consolidate or de-emphasize our many download pages traumschule Webpages/Website WebsiteV3
Description

During the UX Sprint, several of the users found alternate download pages other than download-easy, and became confused. If you search for Tor, download Tor, or Tor Browser, you get one of the following links:

https://www.torproject.org/download/download https://www.torproject.org/projects/torbrowser.html.en https://www.torproject.org/download/download-easy.html

Each of these has a different flow for downloading Tor Browser, and all but download-easy caused users to stop and become confused. I personally think https://www.torproject.org/download/download should simply redirect to download-easy, and the https://www.torproject.org/projects/torbrowser.html.en page should remove the matrix and either behave like download-easy, or its download button should take the user to download-easy.

We will still need some place to put installation instructions, and the alpha downloads, but those should be broken off into different pages that replace the outdated mess in https://www.torproject.org/docs/documentation.html.en.

#16546 Should we move anonbib to the Tor website? cypherpunks Webpages/Website WebsiteV3
Description

Right now, anonbib exists under freehaven auspices, and is not maintained by Tor.

"Not maintained" being the operative word.

Should we move it to a torproject url and try to pretty it up a bit?

#16548 Change the HS nomenclature from hidden to onion cypherpunks Webpages/Website WebsiteV3
Description

As discussed during the anonymous services meeting, we should change (or discuss changing) the nomenclature on the website to reflect Syverson's Genuine Onion'' paper.

Please do not make the mistake of grepping for Hidden and replacing it with Onion.

#17393 Make the various javascript on Tor sites be LibreJS-compatible? traumschule Webpages/Website WebsiteV3
Description

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?

#17413 Usability of MacOS installation process traumschule Webpages/Website WebsiteV3
Description

Usability of MacOS installation process

Consequence: User is unable to verify package signature

Steps to reproduce:

  1. Download Tor browser
  1. Go to https://www.torproject.org/docs/verifying-signatures.html.en for instructions.
  1. Read the block of text for MacOS and Linux.
  1. Follow the link at the bottom of that section to:

https://www.gnupg.org/documentation/

  1. Struggle with the information on that page.
  1. 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

  1. 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.
  2. Download and install GPGTools.
  3. Open a Terminal window (Terminal is in /Applications/Utilities or find it with search)
  4. 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.

#17669 Old links to outdated versions of Tor Browser should redirect to a page with the latest version of Tor Browser hiro Webpages/Website WebsiteV3
Description

When I follow a link online to an old version of Tor Browser Bundle, e.g.

https://www.torproject.org/dist/torbrowser/3.6.6/torbrowser-install-3.6.6_en-US.exe

I receive a 404 message. Instead of displaying a default 404 page, a Tor Browser specific 404 response should helpfully redirect users to the latest version of Tor Browser, either by providing a helpful message such as "Click here to download Tor Browser" or via a 301 redirect.

#17805 The website should support "stable" and "oldstable" tor releases cypherpunks Webpages/Website WebsiteV3
Description

Right now we have "alpha" and "stable". But sometimes we want to have an extra stable listed as well.

No hurry on this one.

#18243 Website redesign - Phase 1 isabela Webpages/Website WebsiteV3
Description

This is the master ticket created to track the efforts to implement a new site for Tor Project, based on the discussion done during Berlin Dev Meeting in Oct 2015: https://trac.torproject.org/projects/tor/wiki/Website/MainSiteRedesign

You can find the other phases of the project and more information on the link above as well.

Phase 1:

  • Content mapping
  • Decide what to do with content we are moving out of the main site
  • Start mocking how the new site will look like
  • Test our mocks (get user research help)
#18245 Collect different mocks for new site isabela Webpages/Website WebsiteV3
Description

This ticket is for tracking different mocks proposed for torproject.org site based on the Berlin Dev Meeting 2015 discussion: https://trac.torproject.org/projects/tor/wiki/Website/MainSiteRedesign

We will reach out to designers in the community and ask for their help.

#18925 Add instructions for removing the code signing parts of OS X bundles and MAR files tbb-team Webpages/Website
Description

We start with code signing on OS X now and should have instructions on our website for getting rid of the code signing parts to make it easier for comparing the things we ship with the things we built.

#21178 torproject.org submenus and page structures behave inconsistently hiro Webpages/Website WebsiteV3
Description

I've found some behavioral inconsistencies in torproject.org, which I think can confuse our visitors. It would be great if we could fix some of these things.

  1. If you go to the "About Tor" page or the "Contact" pages, both are highlighted in the horizontal menu. (to view: https://www.torproject.org/about/overview.html.en)
  1. About Tor > Projects leads to "Software and Services" (https://www.torproject.org/projects/projects.html.en). I think that this should be consistently named.
  1. About Tor > Projects does does not redirect to a different page and has submenu items visible from the About Tor page. About Tor > Documentation and About Tor > Projects both do. My suggestion is to making Tor People redirect to a separate page with a separate vertical side menu, but also having the About Tor> Projects and About Tor > Documentation menus nested in the vertical menu on About Tor is also acceptable, as long as these side menus behave consistently.
  1. Some pages are blank: https://www.torproject.org/docs/manual.html.en, https://www.torproject.org/docs/installguide.html.en. This is bad because it makes them look broken. I don't have a better idea of what to put here without restructuring the whole website contents, but I think at the very least it should not be blank.
  1. You can browse to some pages that have different styling (go https://www.torproject.org/docs/documentation.html.en, click "Install Tor Browser" to get to https://www.torproject.org/projects/torbrowser.html.en), which really throws me off. It looks like it's a different site, or I've been redirected/scammed. I think there are other instances of this, but I can't recall every instance of where this happened.
  1. This may not be too big of an issue, but the main menu (Tor Home About Tor Documentation Press Blog Contact) keeps the current tab highlighted if the user is in that tab (Press is highlighted on https://www.torproject.org/press/press.html.en), but this doesn't happen for the submenu (Download Volunteer Donate)--the volunteer page https://www.torproject.org/getinvolved/volunteer.html.en does not have volunteer highlighted.
#21222 Main ticket for website redesign project isabela Webpages/Website website redesign
Description

Website redesign main ticket introduction

This is a huge project the UX team is leading and it has a lot of steps involved on it. Our goal is for this project to be the base of something that can scale while we continue to iterate on it.

What problems are we trying to fix?

This project aims to fix many problems that goes beyond just a redesign thing, even though we are calling it 'website redesign'.

Yes, Tor Project website is not the best thing in the world and is a big problem that must be fixed. And this is a problem that we can't ignore anymore, is hurting many initiatives we have at Tor Project.

Our community is growing and this growth is part of the 'website problem'. A lot of information have been added to torproject.org over the years leading to what we have now. Is a good problem to have, but right now we must reorganize this information to better set ourselves to continue grow.

Here is a list of some problems easily recognizable with the current site:

  • Not localized
  • Too much information at the front page
  • Still hard to find information
  • Hard to add new information (ends up contributing to the mess) and we need to add more information because we are growing :) we have a lot to share
  • inconsistency with the design

And we could go on but the point of this doc is not to have a full description of all the problems we have but just an introduction to set the stage for explaining what we are thinking for a solution and the steps of its implementation.

How we solve it?

Our solution right now is to create new portals to better organize information and also at the same time keep torproject.org simple and easy for first comers to find their way around into what Tor is and how to get/use it.

So we will be building:

  • torproject.org - with 'new user' as our main audience for this portal [of course with easy way to navigate to the other portals:
  • dev.torproject.org - short explanation: "all things related to the development of free software projects of Tor Project"
  • community.torproject.org - short explanation: "a umbrella of things that are power by our community, or a portal to 'help people help Tor'.
  • support.torproject.org - user support website

Are we loosing press? FAQs? Donate page? The Blog? No :) the list above are the main entrance to all these things and more.

I invite you to read more about each of this portal and other work related to this initiative in the children tickets (and their children tickets) associated with this project. Is a big project and the information written here is a summary of the summary ;)

Why now?

Right now we are with fund and a team to carry this work. And we need to do this to enable many other great work at Tor to have infrastructure to support their project. We believe that these portals will help a lot of groups inside of Tor Project to better provide information about their work and therefore receive help to do so.

The short version of the process we will follow for each portal

#### process for each site will be:

  1. content architecture - map current content related to the portal and organize it
  1. whiteboard draw organization of the content into pages
  1. wireframe these pages
  1. create design for these pages [these include design reviews till we are happy with what we have]
  1. start organizing content for the pages (with the design already done we will be working with that)
  1. update high definition mockups with real content
  1. guerrilla user testing #1
  1. start coding the pages
  1. once content is finished we upload them on transifex for translation to start
  1. Once coding is done we can start QA by language (as translations gets complete)

10.[we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]

What we will use to build it?

Right now we are testing Lektor for the framework to use: https://trac.torproject.org/projects/tor/ticket/24275

We are also working on a project that will help us build the themes for these portals but also anyone else who would like to follow our style guidelines for their site.

We are creating a fork of bootstrap and changing its css based on our guidelines, we plan to use it to build the front end of the portals. You can follow this project here (and it's children tickets):

[ need to add ticket ]

Some portals like 'support' need a search tool as well. For that we are looking at:

[ need to add a ticket ]

Are we planing to test things?

Yes, not only our framework but everything! We hope to do as many research and test we can, it will all depend on our bandwidth and resources. Since we have been working on building this 'testing' and 'research' steps into our processes we already have some stuff in place that can help us carry those on. We hope to continue to add more resources in this front to be able to do even more of those in the future!

This project is actually the first year of a 3 years project where we hope to build this user feedback / testing process and have it happening in large scale for all the projects we are working on.

What about translation?

We will localize first:

  • torproject.org
  • support.torproject.org

The languages we will support are our tier1 languages : https://storm.torproject.org/shared/o7Rh2S9bsMNN7Eh7C9cKaqxR371pR1AmpRxbu--nC34

  1. English - EN
  2. Farsi - FA
  3. Spanish - ES
  4. Russian - RU
  5. Simplified Chinese - zh-CN
  6. Portuguese - PT-BR
  7. French - FR
  8. German - DE
  9. Korean - KO
  10. Turkish - TR
  11. Italian - IT
  12. Arabic - AR

Translation will be done using Transifex community, thousands of people who have already been translating other Tor things.

We will add a step for Localization Review of the translated sites with a native speaker of each language. So we can have a review in context since as many other crowdsourcing translation tools, translation within context is something they miss. But they do have other features, such as translation memory and vocabulary features that helps a lot on making sure of the translation quality across so many pages and product UIs.

So we will stick with the good practices of using a good tool like Transifex to do the translation and incorporate a review in context step with native speakers. Hopefully we will have volunteers to help us out with all those tier 1 languages.

What have we done

*this part is not done yet* The story of Tor Project website is long! But to cut it short we will talk from 2015 - now (EOY 2017)

This work will incorporate work from past efforts. We did some work on the support page before this site-wide effort.

#22076 adjust text shown on screen based on size of text traumschule Webpages/Website WebsiteV3
Description

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.

#22265 write high-level overview of bootstrap process catalyst Webpages/Website website redesign
Description

There needs to be a better high-level overview of the bootstrap process so developers, users, and UX people can have a better mental model of what's going on, what can go wrong, and how to fix it when it does.

Probably should be a wiki page unless someone has a better idea of where to put it. There is some text in control-spec.txt that is a decent starting point, but could use more elaboration of background material.

1 2 3 4 5
Note: See TracQuery for help on using queries.