Opened 8 years ago

Closed 8 years ago

#2796 closed defect (fixed)

GetTor should describe the available packages

Reported by: rransom Owned by: kaner
Priority: Medium Milestone:
Component: Applications/GetTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If GetTor doesn't recognize the package name in a user's message, it sends a list of the available packages' names, but with no description of what each package is.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by kaner

Priority: criticalnormal

comment:2 Changed 8 years ago by phobos

gettor sends out confusing package names, perhaps something like this would reduce confusion:

tor-browser-bundle-windows-32bit

tor-browser-bundle-windows-64bit

tor-browser-bundle-mac-osx-intel

tor-browser-bundle-mac-osx-powerpc

tor-browser-bundle-linux-32bit

tor-browser-bundle-linux-64bit

tor-browser-bundle-source-code

comment:3 in reply to:  2 ; Changed 8 years ago by phobos

Replying to phobos:

gettor sends out confusing package names, perhaps something like this would reduce confusion:

tor-browser-bundle-windows-32bit

tor-browser-bundle-windows-64bit

tor-browser-bundle-mac-osx-intel

tor-browser-bundle-mac-osx-powerpc

tor-browser-bundle-linux-32bit

tor-browser-bundle-linux-64bit

tor-browser-bundle-source-code

Even so, I keep running into people who don't know if they have a 32-bit or 64-bit operating system, and therefore don't know what to download.

comment:4 in reply to:  3 Changed 8 years ago by phobos

Replying to phobos:

Replying to phobos:

gettor sends out confusing package names, perhaps something like this would reduce confusion:

tor-browser-bundle-windows-32bit

tor-browser-bundle-windows-64bit

tor-browser-bundle-mac-osx-intel

tor-browser-bundle-mac-osx-powerpc

tor-browser-bundle-linux-32bit

tor-browser-bundle-linux-64bit

tor-browser-bundle-source-code

Even so, I keep running into people who don't know if they have a 32-bit or 64-bit operating system, and therefore don't know what to download.

Another thought, label the 32-bit bundles without 32bit, so it's

tor-browser-bundle-windows

tor-browser-bundle-windows-64bit

This way, if users don't know their bitness, they can just grab the one without the confusing 64bit on it and see if it works.

comment:5 Changed 8 years ago by kaner

I think the naming scheme should (except for the source) just let the user pick an architecture he's on, and that's it. We should decide what package is best for him/her for a given architecture. Following this, I suggest:

windows
macosx-i386
macosx-ppc
linux-i386
linux-x86_64
source

comment:6 in reply to:  5 Changed 8 years ago by phobos

Replying to kaner:

I think the naming scheme should (except for the source) just let the user pick an architecture he's on, and that's it. We should decide what package is best for him/her for a given architecture. Following this, I suggest:

windows
macosx-i386
macosx-ppc
linux-i386
linux-x86_64
source

except there is no macosx-ppc package that's valid any more. Otherwise, I say try it. Our benchmark will be the # of emails to tor-assistants before and after the change.

comment:7 Changed 8 years ago by kaner

Resolution: fixed
Status: newclosed

Fixes as described. Closing.

Note: See TracTickets for help on using tickets.