These sound like good changes to me. They make more sense based on the current set of supported applications and for new application development going forward. Using browser as a catchall for everything else, was probably never really correct.

How about doing something about the keywords? Perhaps only listing the ones that are actually used (or listing the most-used ones at the top), including who should add them and when, when they should be removed...

I had a bug before about keyword asking to introduce some more to describe bugs present in one product (e.g. seamonkey) that are present in another one (e.g. toolkit).
The alternative is of course to fill two bugs and adding dependencies but it is most probably more cumbersome - and may lead to wasted effort or worse absence of effort.

I feel in the same way we list platform as 'all' when it as been confirmed on different platform we should have a way to tell it belongs to semaonkey and toolkit - maybe instead of a keyword mechanism, it would be better to introduce a new component called 'seamonkey+toolkit'?

Networking: IMAP/News/POP/SMTP are in Seamonkey but should be in Core, because it is shared with Thunderbird.

Extension Manager is in Firefox but should be in Toolkit, because it is shared with Thunderbird.

XP Apps* and XP Tookit* are all in Core. The XPFE components that /mozilla/toolkit/ has forked should be in the Seamonkey product.

Besides Extension manager, at least these Firefox components need to be moved to Toolkit:
Download Manager (there is already a DM component in Toolkit), Help Viewer, JavaScript Console, Software Update, View Source.

It's time to allow people to vote Thunderbird bugs :-)

Great that this is happening :)

Someone should come up with some kind of policy on Thunderbird/Seamonkey-mail bugs for the front end. For fixes and feature requests filed against Seamonkey mail, it has previously been said that there's no need to move bugs across to the Thunderbird product, or file identical bugs in Thunderbird. Does that still apply?

I had a couple of other points, but Jesse has already made them more concisely than I would've done... :)

HMm. I think perhaps mailnews should be added as a component. Seems to be much confusion as to where bugs effecting thunderbird and the mailnews part of Seamonkey should go.

I meant to say that perhaps mailnews should be added as a seperate product.

On the bug report pick-a-category page, Core should be placed much higher - people are going to see 'Firefox' and click without reading on...

I don't think that this will help. Most of the users that use Thunderbird and Firefox will file bug under Thunderbird general, and not in Core product, just like they do not file in Browser/MailNews now.

The solution is to add all relevant categories to each product at the level of reporting, and then you can auto-switch product to Core for shared categories. So there should be Junk filter category in both Thunderbird and MailNews, but when bug is submitted product should be changed to Core.

I agree with Ivan Icin.

Though the re-organisation is good from the developers' point of view, it's just going to confuse the ordinary users doing their bit to improve Mozilla.

I foresee many more bugs filed in the wrong categories, and many more dups. Or maybe people will just give up in their confusion.