Custom Query (55 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 30 of 55)

1 2 3 4
Ticket Summary Owner Component Milestone
#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]
#24206 newsletter subscription sends me to donate.torproject.org hiro Webpages/Website website redesign
Description

When I try to sign up for the newsletter at newsletter.torproject.org, the confirmation link that I get in my email is for donate.torproject.org, not newsletter.torproject.org.

To me this feels like a bait-and-switch, where I asked to receive news and suddenly I'm going to be on some donation rolodex.

I guess we used the donate site because it was easier to run the newsletter software there? How hard would it be to separate them? Or at least to send URLs for newsletter, and have that redirect behind the scenes?

#24376 Search backend for websites - Test and deploy Solr hiro Webpages/Website website redesign
#24727 Add onion service for check.torproject.org and use it Webpages/Website
Description

Currently check.torproject.org don't have onion. Use .onion to determine whether user is via Tor or not.

#25131 Add a security.txt file to torproject.org Webpages/Website website redesign
Description

security.txt files give people the information they need to contact Tor when they find a security issue.

It's an IETF draft, and Google has done it, so maybe we should too: https://securitytxt.org/

We can use the existing information at: https://www.torproject.org/about/contact#security

And we might want to:

  • add a PGP key file
  • add a signature
  • maybe add a policy or acknowledgements when we decide how they work
#25475 TB Credits traumschule Webpages/Website website redesign
Description

We should have a page of contributors, either on the website or Tor browser. Tor Community members, translators etc

#26307 Add link to Tor SlackBuild on download-unix.html.en Webpages/Website website redesign
Description

I thought it would be nice to add link to the Tor SlackBuild on download-unix.html.en. The SlackBuild works fine and is updated regularly.

The code would be something like this:

<tr class="beige">
<td align="center"><img src="$(IMGROOT)/distros/slackware.png" alt="Slackware"></td>
<td>Slackware</td>
<td colspan="2"><a href="https://slackbuilds.org/repository/14.2/network/tor/">SlackBuilds.org</a></td>
<td>
<a href="<page docs/tor-doc-unix>">Linux/BSD/Unix</a><br>
</td>
</tr>

If nobody wants to design a new logo, there's generic.png in /images/distros/ folder

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

#26539 add checksums to download page; make checksum vs. sig file purpose much clearer traumschule Webpages/Website
Description

Gpg recently failed to verify a Tor Browser download - a first for me. Since data errors in downloads aren't as common as years ago, I assumed an error in the *.asc sig file itself, or other issues.

Such as my Linux GPG version not playing well with the version used to sign Tor Browser.

I wanted to verify checksum of the downloaded TBB, but after a few searches on TorProject didn't find the checksum, I re-download TBB. It was faster in the long run, but it's a big package to re-download for users with limited data plans, when a few byte checksum would suffice to see if there was a download data error.

I propose that checksum files - or a prominent link, be added to the download page - not make users hunt them. That's how many well run projects seem to do it - app packages, sig files & checksums are all easily found, or have links on the same page.

The statement, "See our instructions on how to verify package signatures, which allows you to make sure you've downloaded the file we intended you to get. Also, note that the Firefox ESR in our bundles is modified from the default Firefox ESR " should be placed above the packages & sig files, where users are far more likely to see it.

The wording could be stronger, clearer - why users would want to verify the TBB / other packages PGP signatures of downloads, EVEN from TorProject's site (not rely solely on checksums). A brief statement why verifying signed packages is important & how it's unrelated to using checksums. If users (of anything) don't understand a real purpose or need, they're more likely to skip steps.

I could write something to make changes, additions & submit for consideration, but only if there's interest in making changes to general security methods to educate users, that work for many products.

  • Verification instructions: They're generally good & someone did a lot of work, but many users unfamiliar w/ PGP / GPG's real purpose & the procedures may be clueless.

On the Windows verify instructions (maybe Linux, OS X), it's unclear which signature & which "package" they're verifying. If they're installing GPG or gpg4win, the instructions should include steps (or link to clear instructions) to first verify GPG itself (once), then a separate verification of downloaded Tor products - EVEN from TorProject's https site.

The statement, "make sure you've downloaded the file we intended you to get." means little to non-gpg users or slightly familiar. To many, they downloaded the correct platform package, therefore they "have the file intended for their OS." As far as they know, they did everything required.

#26808 Publish policy documents on www.torproject.org ggus Webpages/Website
Description

Background

In the past years we worked on many policy documents (CoC, membership policy, etc). We should make them available on a prominent page on torproject.org.

Current situation

The policy documents are published in the gitweb: https://gitweb.torproject.org/community/policies.git/tree/

Some other bylaws can be found here: https://www.torproject.org/about/financials.html.en

Expected situation

Create a section within "About Tor" named "Policies". With a general text describing our current policies.

I would also suggest that we inline describe our current values, how membership works, how voting works, etc.

Create formatted versions of:

  • CoC
  • Membership guidelines
  • statement of values
  • voting system
  • board documents (like bylaws)
  • ...

and link them from the main policy page.

*Timeline*

I would suggest that we collect ideas within this ticket and make a meeting in Mexico :-)

#26836 Update and refresh the research portal Webpages/Website
Description

The research portal isn't the prettiest website, nor does it contain the most up to date information. This ticket will act as a central ticket for tasks around updating and refreshing the research portal.

#26837 Move the "research-ideas" tickets to research ideas page Webpages/Website
Description

The Metrics/Analysis trac component has been gathering tickets that are not really suited to being trac tickets. The Metrics team certainly isn't going to look at them any time soon. I had tagged these with the keyword research-ideas.

The ideas page is at https://research.torproject.org/ideas.html on the portal.

#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
Note: See TracQuery for help on using queries.