Custom Query (103 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 15 of 103)

1 2 3 4 5 6 7
Ticket Summary Owner Component Milestone
#26298 link more than one stable and one unstable from download page Webpages/Website Tor: unspecified
Description

Right now the download page at https://www.torproject.org/download/download.html.en seems to only have the ability to provide source code download links for a stable and an unstable tarball. We might want to provide multiple unstable tarballs at once from time to time.

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

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

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

#22405 Fix onion links for downloading Tor Browser hiro Webpages/Website website redesign
Description

When using the onion service of torproject.org, clicking download links unfortunately redirects to clearnet dist.torproject.org instead of its onion service.

For example:

http://expyuzz4wqqyqhjn.onion/dist/torbrowser/6.5.2/torbrowser-install-6.5.2_en-US.exe

redirects to

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

instead of

http://rqef5a5mebgq46y5.onion/torbrowser/6.5.2/torbrowser-install-6.5.2_en-US.exe

#22611 Make TB uninstall instructions more detailed in FAQ linda Webpages/Website website redesign
Description

macOS requires special treatment.

See https://github.com/pastly/webwml branch macos-tb-uninstall

#22637 Find a more maintainable approach for the signing-keys page Webpages/Website website redesign
Description

Right now we have this page: https://www.torproject.org/docs/signing-keys which is supposed to provide an official set of keys that have signed various Tor packages in the past.

We pointed to it from https://www.torproject.org/docs/verifying-signatures among other places.

But people keep generating new subkeys, so the text on that page goes out of date after a month or so.

We should come up with a better way to distribute these keys, in a way that provides good enough authenticity while being easy to automate.

Maybe that's a script that gets run every so often to generate the page automatically? Maybe that's creating a gpg keyring with the right keys on it, and getting rid of the webpage?

We can think of this as part of the grand website redo, but also we can think of it as a bitesized improvement that needs to be made and can be independent of the grand website redo.

#22888 Permanent download URL for the latest release hiro Webpages/Website website redesign
Description

https://ftp.mozilla.org/pub/firefox/releases/latest/README.txt says

Please use download.mozilla.org to retrieve the latest Firefox release.

For example, if you wish to download the US English installer for Windows (32bit) the url is

https://download.mozilla.org/?product=firefox-latest&os=win&lang=en-US

This could be pasted into the location bar of a browser, or used with curl or wget, e.g. wget -O FirefoxSetup.exe "https://download.mozilla.org/?product=firefox-latest&os=win&lang=en-US"

Can you please offer this for Tor Browser too?

#23266 Carryover Tasks Webpages/Website website redesign
Description

This page keeps track of things we need to fix in the old torproject.org that we'll still need to fix when we make a new version of torproject.org.

#23432 Move CSP style attributes into external stylesheets Webpages/Website website redesign
Description

Suggested by the Mozilla Observatory https://observatory.mozilla.org/analyze.html?host=torproject.org

Your current CSP policy allows the use of 'unsafe-inline' inside of style-src. Moving style attributes into external stylesheets not only makes you safer, but also makes your code easier to maintain.

#23446 Write a guidelines documentation for requirements with Tor integration by third parties tbb-team Webpages/Website website redesign
Description

I heard that one of the discussions in the Montreal meeting was "Encouraging Tor integration by third parties" which spawned for me the idea that there must be some guidelines documentation the requirements that should be met for each use case. For example for browsers (where integrating Tor is a goal with Brave in private browsing and it has been suggested by the (ex?)-CEO of Mozilla) among the requirements I can think of,

  1. Having the user agent the same as the Tor Browser (Otherwise fingerprinting would be easy).
  2. Stream isolation should be enforced, otherwise a single exit can watch all traffic.
  3. First party isolation should be enforced.
  4. ...etc

Of course there's already the Tor Browser design documentation, but it doesn't address this question directly, and more importantly those folks don't want to make an alternative Tor Browser, rather just a "Tor mode" to their private browsing that can enable true privacy by design.

What do you think of such an idea?

Note that this finds its parallel with little-t-tor in another ticket that I couldn't find about alternative implementations of the tor client.

#24129 support.torproject.org work isabela Webpages/Website website redesign
Description

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

  • Main stakeholders of this project: Community Team - Alison and Collin
  • 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]

Content:

https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Support

#24131 torproject.org work hiro Webpages/Website website redesign
Description

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

  • Main stakeholders of this project: Shari and Communications Team
  • Designer for this project: Antonela
  • Developer for this project: Hiro
  • PM for this project: Isabela

Process:

  1. content architecture - map current content related to the portal and organize it
  2. whiteboard draw organization of the content into pages
  3. wireframe these pages
  4. create design for these pages [these include design reviews till we are happy with what we have]
  5. start organizing content for the pages (with the design already done we will be working with that)
  6. update high definition mockups with real content
  7. guerrilla user testing #1
  8. start coding the pages
  9. once content is finished we upload them on transifex for translation to start
  10. Once coding is done we can start QA by language (as translations gets complete)
  11. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]

Translation:

The languages we will support are our tier1 languages : ​https://storm.torproject.org/shared/o7Rh2S9bsMNN7Eh7C9cKaqxR371pR1AmpRxbu--nC34 English - EN Farsi - FA Spanish - ES Russian - RU Simplified Chinese - zh-CN Portuguese - PT-BR French - FR German - DE Korean - KO Turkish - TR Italian - IT Arabic - AR

#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]
1 2 3 4 5 6 7
Note: See TracQuery for help on using queries.