Closed Bug 1577638 Opened 5 years ago Closed 1 year ago

[meta] Strengthen Thunderbird identity / brand. Reduce inconsistent naming

Categories

(Thunderbird :: General, defect)

Unspecified
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emoore, Assigned: ryan)

References

(Depends on 3 open bugs, )

Details

(Keywords: meta, Whiteboard: support68.0)

Thunderbird 68 (at least under Windows 10) seems to have shifted to consistently using Thunderbird rather than Mozilla Thunderbird as the name of the product, with a few exceptions.

The welcome page, Tools -> Options, the help menu, Help -> troubleshooting information, the profile manager, and the web pages for the Thunderbird tour, release notes, and help all seem to consistently use "Thunderbird". The default profile location even uses Thunderbird as a directory name.

  1. The text in Help -> About Thunderbird popup window calls the product Thunderbird but has a windows title of About Mozilla Thunderbird. The title apparently wasn't changed when the menu item was renamed.

  2. The name of the shortcut on the desktop is still called Mozilla Thunderbird. For consistency it should be Thunderbird.

  3. The Thunderbird setup program initially uses "Thunderbird". However, when you choose a custom install location the window title is Mozilla Thunderbird setup, and the text refers (twice) to Mozilla Thunderbird. The start page has a "Mozilla Thunderbird" entry.

  4. The Thunderbird setup program defaults to installing in C:\Program Files (x86)\Mozilla Thunderbird\ under Windows 10. It should be a Thunderbird directory, if you want to be consistent.

Indeed. There is some incomplete evolution

Pretty much all of that is code shared with firefox, or semi-forks. Have you done a comparison to Firefox?

https://www.thunderbird.net/en-US/organizations/ (Thunderbird for Organizations) has a "Mozilla Thunderbird Extended Support Release" header in big bold text and then talks about "The Thunderbird Extended Support Releases (ESR)". That is inconsistent.

Ryan, do we have a trello item for this?

Flags: needinfo?(ryan)

I don't believe this is an issue anymore. Or am I just blind (looking at the page, I don't see "Mozilla Thunderbird" on there).

Flags: needinfo?(ryan)

Problems #1, #2 haven't changed in Version 68.5. I didn't re-test for #3 and #4. Testing the beta (74.0b2) problems #1, #2 and #3 haven't changed.

Yes, you are correct Eric. I meant the website mention. I will follow up on the other ones.

Assignee: nobody → ryan
Depends on: 1637916

Changing this to meta.

While we are still using "Mozilla Thunderbird" and similar phrasing in several locations, it has been slowly dying out, including on our new website. We should continue to further unify our messaging with more consistent naming as much as possible, and we shouldn't let the fact that we use mozilla services (and may need to use "mozilla thunderbird" for licensing and other legal reasons in some places) to stop that progress.

Depends on: 1559891, 1479284
No longer depends on: 1637916
Keywords: meta
Summary: inconsistent Thunderbird branding → inconsistent Thunderbird branding [meta]
Depends on: 1637916
Depends on: 1664734
Summary: inconsistent Thunderbird branding [meta] → Strengthen Thunderbird identity / reduce inconsistencies [meta]
OS: Unspecified → All
Summary: Strengthen Thunderbird identity / reduce inconsistencies [meta] → Strengthen Thunderbird identity / brand. Reduce inconsistent naming [meta]
Depends on: 1726082
Depends on: 1726083

FWIW, I disagree. We should not de-emphasize the ties to Mozilla.

Summary: Strengthen Thunderbird identity / brand. Reduce inconsistent naming [meta] → [meta] Strengthen Thunderbird identity / brand. Reduce inconsistent naming
Severity: normal → S3

We've cleaned this up a number of places. Things look much better across most of our channels, and we continue to improve things in this regard, thanks in large part to Jason's work. Marking resolved.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.