Version 0.2 is up at: http://www.gerv.net/temp/bmo-reorg.html
It contains most of the uncontroversial, clearly-defined changes
proposed in this group. Please check to see if your favourite is there,
and if so, if I got it right.
Somehow we got embedded a nesting level under "unclassified" a bit
longer than needed.
(Grendel and "Platform Obsolete" ended up under that heading)
~Justin Wood (Callek)
On the right side:
> Startup and Profile System [moved from Firefox; merge in Core:XRE
Startup; bug 272026]
should be "merge in Toolkit:XRE Startup" instead.
Consequently, Toolkit:XRE Startup is to be removed.
> Somehow we got embedded a nesting level under "unclassified" a bit
> longer than needed.
And "CCK" seems to be splitted under "Unclassified" and "Client Software
> Other Applications"...
I can't parse that sentence :-(
> (Grendel and "Platform Obsolete" ended up under that heading)
Both of these are supposed to be under "Unclassified".
Because that's how things are now. There's a CCK product, closed to new
bugs, and a CCK component as well (currently in use).
And now version 0.4, with all issues raised in this group resolved.
Again, please shout if the change you wanted isn't in there, or you
don't like something.
I still think that, under Thunderbird, "View" should be split out of
"Mail Window Front End".
When I do a Bugzilla on Thunderbird for any of the terms "view",
"thread", or "sort" in the Summary, I get 411 open bug reports. That's
over 20% of all the Mail Window Front End bug reports.
Yes, I realize that those three terms might appear in a bug report that
has nothing to do with viewing a message. However, there might also be
bug reports about viewing messages that have none of those three terms.
David E. Ross
Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation. © 1997
Lots of them aren't in the right order; Bugzilla sorts them
How would people know which of the two components to file their bug in?
The calendar protocol components are capitalized like so: CalDAV and WebDAV.
When you create a bug report and select a component, there is a
description of theat component to the right. The description for "Mail
Window Front End" could indicate that bugs for viewing, threads, etc
should be reported for the View component.
Actually, just leave "Sidebar" as "Sidebar" then and "Search" as
"Search". This had been proposed originally anyways by some people
involved in the code.
This basically boils down to "just read the documentation", which we
know nobody does.
"This component is too big" is not a particularly good reason on its own
to split it. "Different developers work on part A and part B", and/or
"Bug filers can easily distinguish between part A and part B" would be
good reasons for a split.
Notably, I believe that this is the only split (as opposed to rename or
combination) which has been suggested so far.