Closed Bug 288371 Opened 20 years ago Closed 18 years ago

Add new "SeaMonkey" suite to AMO

Categories

(addons.mozilla.org Graveyard :: Administration, defect)

Product:
addons.mozilla.org Graveyard
Component:
Administration
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kairo, Assigned: morgamic)

References

Details

As the new suite product (the renamed, revived version of Mozilla suite) has a
different name and versioning, it would be nice to be supported as a new product
on UMO.
I've already selected a GUID for it: 92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a
(And yes, we even plan to use it in the code for the future, but for now it's a
dummy like the one of the Mozilla suite)
Assignee: Bugzilla-alanjstrBugs → kveton
Depends on: suite-rebranding
OK, the main rebranding has happened, the name is officially "SeaMonkey" now,
and the GUID is now even available in that application as we also implement
nsIXULAppInfo now.

We have planned a SeaMonkey 1.0 alpha within weeks, so I think we can start
thinking about if and how it can be added to UMO.
Summary: Add new suite product to UMO → Add new "SeaMonkey" suite to UMO
Assignee: kveton → Bugzilla-alanjstrBugs
QA Contact: mozilla.update → administration
For the record, SeaMonkey 1.0 Alpha is out, so there's an official release out
now (even if it's a testing one), and if we were listed on UMO/AMO, people could
go out and get extensions up there theoretically.
Now that SeaMonkey 1.0 has been released, can we get something going here?
Assignee: Bugzilla-alanjstrBugs → morgamic
I plan to submit a Seamonkey ONLY extension to A.M.O.
The Seamonkey Suite now has a product page:
<https://addons.mozilla.org/extensions/?application=seamonkey> but:

1. Is currently not reachable from the main A.M.O. page.
2. Still uses the Firefox banner.

Is there someone who can take ownership of this bug and get something moving?

Thanks.
Additionally, that page uses wrong capitalization of the name. "SeaMonkey" (capital M) would be correct.
Severity: normal → major
Status: NEW → ASSIGNED
Target Milestone: 1.0 → 2.0
What can we do to make this happen?
Paul, would it be possible to get a SeaMonkey logo to go along with the others and replace the Mozilla Suite ones?
morgamic, I can provide a SeaMonkey in any needed size if that plan is accepted, thanks for looking into this matter.
(In reply to comment #8)
> I can provide a SeaMonkey

A SeaMonkey logo, of course ;-)
Bugspam makes us be-come druggies
Fa-la-la-la-la, la-la-la-la
Get morgamic some more coffee
Fa-la-la-la-la, la-la-la-la

Updating all the bugs which have "Update" or "UMO" in them.
Summary: Add new "SeaMonkey" suite to UMO → Add new "SeaMonkey" suite to AMO
Depends on: 342816
Is something similar to the patch in bug 352641 what we need?
(In reply to comment #11)
> Is something similar to the patch in bug 352641 what we need?
> 

Bug 342816 is going to land soon. If that goes fine, this bug will be "half" resolved. If that does go fine, we MAY do a similar update for Sunbird. 

The patch on bug 352641 is not going to land for some considerable time, if ever, as per http://morgamic.com/2006/09/18/amo-code-freeze/ I'm unsure how things are going to work with the side-by-side remora/current AMO, but if we do continue maintaining AMO, the patch on 352641 might get looked at. I'd hope that we will promptly get remora working for multiple apps and away we go, but that may not be the case. The silly app-specific header stuff just plain sucks. 

So yeah, in the event that we do end up running remora and the current AMO side by side a patch like the one on bug 352641 may be considered. I wouldn't recommend you waste any time on it until Shaver has looked at those patches though (which won't be for at least a month.) Personally, I'd prefer we just worked on Remora until it has all the required features to replace the existing AMO, but I'm not 100% on what the plan is. 
SeaMonkey is one of the four supported apps in the upcoming version 3 of AMO. It fixes this bug.

I still think you should provide a SeaMonkey in an arbitrarily big size, Robert ;)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
I thought we have the imagery up we needed - or was this just a joke?

If just bug 374477 would be completely fixed (at least the themes part look to not work yet on preview)
Just a joke.

The other bug is actually fixed (in the trunk, that is); have to find the related bug.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.