Custom Query (73 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 45 of 73)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#30709 expyuzz4wqqyqhjn.onion redirects to clearnet: 2019.www.torproject.org hiro Webpages/Website
Description

http://expyuzz4wqqyqhjn.onion/docs/tor-manual.html.en redirects to clearnet: https://2019.www.torproject.org/docs/tor-manual.html.en

#30740 link.tl skip button is not working with tor browser hiro Webpages/Website
Description

i tried many times and can not see any link on this site. you can see what happen .i am using windows 10 pro and last tor browser version 8.5 (based on Mozilla Firefox 60.7.0esr) (64-bit)

https://gyazo.com/87a411437830c727d8a126acaaa0ed89

#30748 torproject onion sites unreliable hiro Webpages/Website
Description

rougmnvswfsmd4dq.onion <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p> <some random weird strings>

what is this base64 similar looking strange string in the end? any signature to make sure I'am talking to tpo? I'am worried. because in another torbrowser session i can reach the sites fine. how can come such difference behavior?

#30838 Update the Debian instructions for experimental-0.4.1 hiro Webpages/Website Tor: 0.4.1.x-final
Description

The 0.4.1 branch is now separate; the 0.3.4 branches are now deprecated.

We should update the website accordingly: https://2019.www.torproject.org/docs/debian.html.en

This change requires the deb.torproject.org change in #30836, and a successful nightly build of experimental-0.4.1.

#30965 Tor Browser is now on F-Droid so remove the "s00n" (soon) from button and make it clickable hiro Webpages/Website
Description

Fix F-Droid button near the bottom of this page: https://www.torproject.org/download/

Link to https://f-droid.org

#30966 Install instructions for Linux/Ubuntu users who might not be entirely familiar with tar.xz hiro Webpages/Website
Description

Its been a few months since I've installed it myself. I know that it needs to be extracted somewhere, but I need to remind myself of the location. A simple page similar to the page instructing users how to verify the gpg signature may be advantageous and improve the new user experience.

ON THIS PAGE: https://tb-manual.torproject.org/

Between the subsection "Downloading" and "Running Tor for the first time" there may be an "Installation" section listed with basic instructions.

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

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

#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

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

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

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