223229 - Profile Directory Name should be "MozillaComposer"

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Peter Lairo]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

Prifile Directory Name should be "MozillaComposer"

From: news://news.Mozilla.org:119/bn3948$[e-mail]

The only thing that bothers me is that the name of the profile directory could
be better chosen. My preference would be: "MozillaComposer" (one-word, and
initial Caps). Below is a copy of my post in the calendar NG on the very same
subject (news://news.Mozilla.org:119/bn37tu$[e-mail]):

If a standalone calendar [or Composer] does materialize, I would suggest that
the profile directory be called "\MozillaCalendar" [or "\MozillaComposer"], in
anticipation of the re-integration of the components (TB, FB, SB, ...) into the
main Mozilla trunk. At this time, the applications are planned to be called
"Mozilla Mail&News", "Mozilla Browser", Mozilla Composer", Mozilla Calendar",
etc. So it will be more *consistent* to have the profile directory name(s) match
the name(s) of the program(s) whose data they contain. I am not too fond of the
current naming of the standalone apps' profile directories (\phoenix,
\thunderbird) as they will either cause increasing confusion as the app names
become "Mozilla Browser" etc and/or when people (once again) need to migrate
their profile to the then new (and hopefully final) profiles. Also, having the
name "Mozilla" in the profile name makes it much better to identify (in addition
to raising "brand awareness"). Additionally, if all standalone apps were to
follow this convention, all Mozilla apps' profiles would be grouped together in
the "\Application Data" subdirectory (if sorted by name, which is usually the
default sort order). 

Reproducible: Always

Steps to Reproduce:
1. look at profile's directory (different location for each OS).
Actual Results:  
Name is currently "composer"

Expected Results:  
Name should be "MozillaComposer"

Comment 1

[Peter Lairo]

Assigning to [e-mail] (as per his request)

Comment 2

[Peter Lairo]

Perhaps migration of existing composer profiles should be considered? (although
I don't consider this an mportant issue, being at 0.0.1 and all)

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420