Custom Query (71 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 60 of 71)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#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.

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

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

#30478 Make it easier to find tb-manual hiro Webpages/Website
Description

It is hard to find tb-manual.torproject.org from www.torproject.org. I found only one link, anywhere. On the webpage for downloading, scroll halfway down to find it in a sentence in the middle of similar looking paragraphs. I found the manuals on 2019.www.torproject.org from the www.torproject.org Documentation heading much faster than I found tb-manual.torproject.org.

It is easy to find support.torproject.org because it is on every page in the heading.

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

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

#28783 Incomplete Content-Security-Policy blocks video on "Set up Relays" page hiro Webpages/Website
Description

Affected page: https://www.torproject.org/getinvolved/relays.html.en

Problem: "No video with supported format and MIME type found" The video's URL is https://media.torproject.org/video/2012-03-04-BuildingBridges.ogv and forbidden by CSP.

Solution: Change

Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'

(https://www.hardenize.com/report/torproject.org/1544035352#www_csp)

to

Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; media-src 'self' https://media.torproject.org

or even to

Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; media-src 'self' https://media.torproject.org; frame-ancestors 'self'; block-all-mixed-content; disown-opener; plugin-types application/pdf; base-uri 'self'

#29944 In the onion.torproject.org list of onion services run by the Tor Project, can we add an onion address that opens a Tor: Mirrors onion page? hiro Webpages/Website
Description

Indeed, https://2019.www.torproject.org/getinvolved/mirrors.html.en directly opens the Tor: Mirrors https page, but, alas, no Tor: Mirrors onion address appears in the https://onion.torproject.org/ list of onion services run by the Tor Project. At some point in the recent past, did not the onion address http://4bflp2c4tnynnbes.onion/#website-mirror directly open a Tor: Mirrors onion page? If not, can we add a Tor: Mirrors onion address to the https://onion.torproject.org/ list of onion services run by the Tor Project? Today, http://4bflp2c4tnynnbes.onion/#website-mirror directly opens the How can we help? Most Frequently Asked Question | When I use Tor Browser, will anyone be able to tell which websites I visit? page, where you can select Topics Misc to go to the first page of the Tor Glossary, from where you have to scroll down 19 pages to see the website mirror section, which contains the Tor: Mirrors address https://2019.www.torproject.org/getinvolved/mirrors.html.en, not a Tor: Mirrors onion address.

#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

#30259 Improve verify signature flow for Tor Browser antonela Webpages/Website
Description

Verifying signature is a painful process for regular and power users. This ticket aims to explore how we can improve it.

#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

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

#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

#22842 Create a knowledge base that's more in-depth than FAQs hiro Webpages/Website WebsiteV3
Description

It would be useful for visitors to our web pages to have access to content that:

  • goes into more depth than a FAQ entry
  • is more formal than a blog post
  • is less comprehensive than a reference manual section
  • is more stable than a wiki page

These pages would form sort of a knowledge base or resource section.

#26314 Create "Learn More" Landing Page for TBA Webpages/Website
Description

When TBA is first launched there is a "Learn More" link the user can click. We should take advantage of this and create a useful webpage where the user can learn more. (Orfox currently has this, too, and the link goes to the Guardian Project's Orfox page.

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