Along with rebranding (bug 285696) and newly forming the SeaMonkey project, we request the "Mozilla Application Suite" product on bmo to be renamed to "SeaMonkey" and the components being restructured. I'll attach a list of the changes we like to happen.
Perhaps we should add an additional line to the product description I proposed in the attachment, stating "Mozilla Application Suite bugs also belong in that component."
oh man. let's move the receipts and offline and whatever bugs to core first. i rally don't want the categorization lost. some people reasonably presume that they don't need to list the component in the summary.
further note that we'll need justdave or myk to setup backwards compat when we rename the product.
(In reply to comment #3) > oh man. let's move the receipts and offline and whatever bugs to core first. i > rally don't want the categorization lost. some people reasonably presume that > they don't need to list the component in the summary. Then we should get those moved to Core soon, please, as we don't want to move out our new structure for too long. For the most components touched here, the eventual merging is intentional, as we need to consolidate our project structure.
Well, from our (SeaMonkey Council) point of view, we would be good to go for that change. What do we still need and what can we do to drive it forward?
*** Bug 300337 has been marked as a duplicate of this bug. ***
Created attachment 188943 [details] placeholder logo (64x64) for report a bug page I'm attaching a 64x64 version of our placeholder logo so that it can be used on the new "report a bug" page once the renaming is done. Note that we'll need to change this icon later on to our final logo, once we have one.
Comment on attachment 188943 [details] placeholder logo (64x64) for report a bug page argh, I'm too used to click "patch" on an attachment :(
> request the "Mozilla Application Suite" product on bmo to be renamed to "SeaMonkey" Just a note that I don't think it should be simply renamed. Rather, SeaMonkey should be added as a separate product altogether. Since, AFAIK, there will still be a need to track (security) changes specific to the 1.7 MAS branch while it's still being maintained - won't there? Also tweaking summary, as I couldn't find this bug on my own.
Also, from looking at the new component structure, shouldn't Tabbed Browsing be included as a separate component? (Distinct from Core, since SeaMonkey may implement things differently than Firefox in that area.) Or is it planned to lump everything with respect to tabs under UI design?
(In reply to comment #10) > Just a note that I don't think it should be simply renamed. Rather, SeaMonkey > should be added as a separate product altogether. Since, AFAIK, there will > still be a need to track (security) changes specific to the 1.7 MAS branch while > it's still being maintained - won't there? Those (hopefully very few) issues are very likely issues that are common to both, and even more likely to not be suite-specific, so no need for seperate products here. Additionally, the Mozilla suite may be retired sooner than some might think, from hearing how tired some MoFo folks are of supporting it. Creating a new SeaMonkey product, moving almost all open bugs there (as we usually only track trunk with open bugs) and retiring the old Mozilla suite product a few months later is just stupid in my eyes. We don't want to have abandoned Bugzilla products lying around if they still carry history of the same code as the active SeaMonkey Bugzilla product. So we should just go and rename it, along with refitting it to the new and active project's needs. What we still need is Asa's OK on all that, though. (In reply to comment #11) > Also, from looking at the new component structure, shouldn't Tabbed Browsing be > included as a separate component? After the move to the toolkit architecture will be complete, I think we will just be using toolkit's tabbrowser implementation, and everything else will be just small UI tweaks.
> Creating a new SeaMonkey product, moving almost all open bugs there > (as we usually only track trunk with open bugs) and retiring the old > Mozilla suite product a few months later is just stupid in my eyes. I agree. After I posted, I realized I should have said to rename it, but then also create the original "Mozilla Application Suite" again. That way all old bugs get put into the correct product, while there's still some place for suite-specific bugs. But if, as you say, there's no need to continue with MAS specifically, then all is well with the world. :) > we will just be using toolkit's tabbrowser implementation, and everything > else will be just small UI tweaks. Okay, let's hope. Although, FF does some things quite differently, so I'm not sure how "small" the UI tweaks might be. I suppose, if need be, components can be revisited later.
(In reply to comment #3) > oh man. let's move the receipts and offline and whatever bugs to core first. i > rally don't want the categorization lost. some people reasonably presume that > they don't need to list the component in the summary. OK, bug 292917 is fixed now, and bug 292917 comment 0 says "The shared backend stuff from "MAS: Offline" and "MAS: Return Receipts" may well go into the existing "Core: MailNews: Backend" component, so there's no need for extra components there." So, basically, it looks we're ready to proceed with this from the technical side. Asa, can we get an OK for that?
OK, the "Localization" project area has been dropped by the Council meeting before we finally uploaded our project structure to http://www.mozilla.org/projects/seamonkey/project-areas.html - that means we don't need the new bugzilla component for it as well. Everything else stays unchanged. Asa, you already said "that's reasonable" on IRC some time ago, could you give a formal OK here so we can get this done?
Comment on attachment 188943 [details] placeholder logo (64x64) for report a bug page This has been obsoleted by the real logo, which is available as a 64x64 version at http://www.mozilla.org/projects/seamonkey/images/seamonkey64.png
As a note for those who are CCed here, we have the OK from Asa on this now, and we are in contact with the people who actually can work on it. This is a big change though, needing movement of many bugs to the new/consolidated components, and it might take some time until that can really be done. We are working on it though. We also have done some tweaks to the list, I'll attach the new version here once we are satisfied with those changes going live as shown on that version.
marcia is now the default assignee for Bugzilla: Keywords & Components.
Created attachment 213575 [details] Updated list of component changes As I got no further comments on our proposed reorganization, here's the updated list of component changes for the suite product. We've done some minor changes and corrections, the basics stayed unchanged though.
Robert: Is this ready to go, and we just need to coordinate a date to do this?
Marcia: Yes, it's ready to go. We're only waiting on someone to do the work of merging a bunch of components and doing all the renaming (and account creation/reuse for the new watchable addresses).
I filed a couple of bugs to move components from Core to Suite/SeaMonkey: - Core:Tabbed Browser (bug 334545) - Core:Location Bar (bug 334959) - Core:Keyboard: Navigation (bug 334960) - Core:Search (bug 334962) - Core:Themes (bug 334964)
What can we do to make this actually happen?
I can do some of the actual work, but it sounds as if this needs involvement from justdave as well. Let me talk to him about the easiest way to do this and after I do that I will post an update in the bug. (In reply to comment #23) > What can we do to make this actually happen? >
justdave and I are meeting this week to talk about planning when we will do this - the script has to be complete and then we have to plan a time to do it.
According to bug 282178 there are still significant differences between xpfe and toolkit tabbrowsers. Most recently I think there is the tab previews in xpfe and scrolltabs in toolkit/browser. So I think there should still be a separate tabbrowser component for SeaMonkey if we want to retain SeaMonkey specific features which might not make it into the toolkit tabbrowser.
(In reply to comment #26) > So I think there should still be a separate tabbrowser component for SeaMonkey > if we want to retain SeaMonkey specific features which might not make it into > the toolkit tabbrowser. This would be a new component anyways, and this can be created after this current bug has been resolved (and it needs to be discussed first). For now, xpfe/suite tabbrowser bugs belong to the "UI design" component of the SeaMonkey product (see attachment).
Hello Robert can you add the open serverless p2p Instant Messenger to seamonkey installer ? http://cspace.in Thanks
comment #28 is completely unrelated to this bug and probably WONTFIX anyways. That said, what's the status on this? marcia? justdave?
Comment on attachment 213575 [details] Updated list of component changes marcia/justdave: What is blocking this bug at the moment? Anything we can do to help it getting along?
I will talk to justdave about this today and see if we can get some traction on this.
The big Bugzilla reorg is being discussed in m.d.planning, and I did throw in this change as well once again. A few small changes to the list came up when I thought about it once more from a current point of view and cleared even more things up (I'll noted those on the newsgroup as well, discussions should be done there): - Instead of creating a new SeaMonkey::Themes component, Core::Themes should move into SeaMonkey and get the desc, etc. we have in the SeaMonkey list. The current component in Core does only track SeaMonkey's default and Modern themes, actually. - Core::Search is also suite only and should move to the SeaMonkey product. - Core::Location Bar is another such case, move it. - same with Core::Tabbed Browser - We might want to rename Bookmarks to "Bookmarks and History", including history UI in preparation of using places backends, but I got to discuss that with other SeaMonkey people first. - We shouldo rediscuss with MailNews folks which MailNews components really belong to SeaMonkey and which to a shared product.
This has been FIXED by the big Bugzilla reorg. Please file any errors that were made as dependencies on this bug and bug 448639 and file any additional things coming up as new bugs.