Custom Query (67 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 45 of 67)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#31212 Document known long-term issues of Tor Browser hiro Webpages/Website
Description

So far, while every Tor Browser release announcement points out known bugs specific to the most recent version, there's no documentation of preexisting issues that are not patched yet, and thus still affect current Tor Browser releases.

A summary of the most relevant ones would help users to keep track of those, and, if needed, adjust their set up/browsing behavior accordingly.

Furthermore, in case there are known ways to circumvent or mitigate a specific bug, the corresponding workaround could be shared as well.

To clarify what I mean: Tails' website is a fine example of how this could be implemented, their release announcement links to: https://tails.boum.org/support/known_issues/index.en.html

#31216 In the list of onion services run by the Tor Project, a domain name and an .onion-address link misdirect to the same wrong Tor Project https page hiro Webpages/Website
Description

List of onion services run by the Tor project https://onion.torproject.org/ List of onion services run by the Tor project http://yz7lpwfhhzcdyc5y.onion/ The listed domain people.torproject.org misdirects to https://www.torproject.org/ The listed address http://sbe5fi5cka5l3fqe.onion/, corresponding with the listed domain onion.torproject.org, misdirects to https://www.torproject.org/. Can we have the listed domain people.torproject.org direct to https://www.torproject.org/about/people/

Can we have the listed address http://sbe5fi5cka5l3fqe.onion/, corresponding with the listed domain people.torproject.org, direct to http://qrmfuxwgyzk5jdjz.onion/about/corepeople.html.en

#31295 please server Tor signature files with Content-Disposition that encourages a download rather than inline viewing hiro Webpages/Website
Description

When i click on the sig link in https://www.torproject.org/download/ (which points to https://www.torproject.org/dist/torbrowser/8.5.4/torbrowser-install-win64-8.5.4_en-US.exe.asc ) i find the OpenPGP signature displayed in the browser directly, rather than being saved to a file.

But the instructions for verifying the OpenPGP signature seem to assume that the signature file has been downloaded as a file.

If you use Content-Disposition you should be able to encourage the web browser to save the signatures as a file in the same way that the installer is a file.

I'm attaching a HAR archive of what my browser (Firefox 68) did when clicking on the sig link, which i think verifies that no Content-Disposition header was sent.

#31722 make a new product assignment page hiro Webpages/Website
Description

During the Stockholm meeting, the TPA team identified there were many sources of "service lists" in the wiki (and elsewhere). As part of #31261, some work was done to clean that up. One of the pages that remained after the work is this one:

https://trac.torproject.org/projects/tor/wiki/org/operations/ProductsandAssignments

Apparently, this could be covered by the new developer website, and I was told to open a ticket to track that work.

So basically, I think the job is to convert the above wiki page into something in the new developer website.

#31724 Localizations not working hiro Webpages/Website
Description

Selecting another language from the drop-down list does not reload the page with the new language.

#32460 download page has confusing flow, especially with donate banner hiro Webpages/Website
Description

We just had a user in #tor who was trying to download the Windows version of Tor from our website, but it wasn't downloading.

After much debugging, we discovered that they had clicked on "download" from our front page, and ended up at https://www.torproject.org/download/ and then waited for the download to begin.

They didn't realize that they needed to scroll down, look for the windows icon, and click on it.

Pastly says he has talked to a half dozen other users in the past few weeks who reported the same "download doesn't work" issue.

It would seem that we should improve the UX of our download page so it is more clear that you need to click on one of the pictures.

I also theorize that the big donate banner on the top of the page is adding to the confusing flow of the page -- maybe people are used to seeing a banner like that on a page that has already auto triggered a download.

mcs points out yet another confusion on that page: once you scroll down past the donate banner, the first thing you find is a box labeled "Download Tor Browser" with a down arrow signaling that you'll begin a download if you click it. And when you click it, it brings you to the download page, and does not begin any download.

#32749 Tor download button on your site does nothing when I click on it hiro Webpages/Website
Description

I'm on cyberghost vpn and your TOR download button does absolutely nothing when I click on it. I have tried turning off firewall, malwarebytes, and tried using both Internet Explorer and Firefox browsers but still nothing happens when I click on your Tor download button and I can't find any search result which give a direct reason and solution to get Tor to download on our pc with Windows 8.1

#32933 Please adapt GeKo's core people entry hiro Webpages/Website
Description

My current entry on our core people page says: "Currently lead of the Tor Browser team." That's no longer true. Please change that to "Works on network health."

#32946 Something in the jenkins setup is reverting the website to an older version hiro Webpages/Website
Description

Someone on IRC pinged us to report that the links to download Tor Browser from https://www.torproject.org/download/languages/ and https://www.torproject.org/download/ have the wrong version in all platforms and languages.

Website is serving: 9.0.2

Latest stable: 9.0.4.

#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.

#24132 dev.torproject.org work isabela Webpages/Website website redesign
Description

This is the main ticket for the work related to creating dev.torproject.org

  • Main stakeholders of this project:
  • Designer for this project: Antonela
  • Developer for this project: Hiro
  • PM for this project: Isabela

Project phases:

  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)
  1. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
#24133 community.torproject.org work pili Webpages/Website website redesign
Description

This is the main ticket for the work related to creating community.torproject.org

  • Main stakeholders of this project:
  • Designer for this project: Antonela
  • Developer for this project: Hiro
  • PM for this project: Isabela

Project phases:

  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)
  1. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
#29200 Make more accessible Core Tor documentation pili Webpages/Website website redesign
Description

There's Core Tor documentation distributed in three (at least) sources. Even if it's documentation intended for developers, it'd be great that it would be more accessible by providing the HTML version online and using some torproject.org subdomain or path or links. The sources are:

I can provide scripts to generate/convert the documentation automatically. We would need to decide where to put it, maybe get subdomain and get access to the server where it would live.

#27412 make bug tracker links on getinvolved page accessible without login qbi Webpages/Website
Description

The bug tracker link to Tor on https://www.torproject.org/getinvolved/volunteer.html.en requires a trac account. It is very unlikely that anyone visiting this page for the first time (like after clicking "Get Involved" on about:tor) is logged in.

This longer link gives the same result without login.

I don't know though if this should be fixed in trac or the website.

#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.

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