Closed Bug 1198340 Opened 5 years ago Closed 4 years ago

Add some useful content to the carousel in the SeaMonkey discovery pane

Categories

(addons.mozilla.org Graveyard :: Discovery Pane, defect)

Product:
addons.mozilla.org Graveyard
Component:
Discovery Pane
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: philip.chee, Unassigned)

References

(Blocks 1 open bug)

Details

This bug is for creating content for the discovery pane carousel for SeaMonkey.

Action items:
1. Find out from AMO devs the format of the content needed for the carousel (xhtml? json? MySQL?) - requires input from AMO admins.
2. Create content - SeaMonkey devs will provide content once we know the AMO requirements.
3. Upload content to the AMO CMS - requires action by AMO admins.
Hello Amy Tsay. Can you help us with item 1 above?
(In reply to Philip Chee from comment #1)
> Hello Amy Tsay. Can you help us with item 1 above?
NI :jorgev please let me know the correct person to deal with this patch thanks.
Flags: needinfo?(jorge)
Bug 1009759 is an example of a promo content request. I suppose a similar approach would be needed for SeaMonkey.
Flags: needinfo?(jorge)
(In reply to Jorge Villalobos [:jorgev] from comment #3)
> Bug 1009759 is an example of a promo content request. I suppose a similar
> approach would be needed for SeaMonkey.
That but appears to be for the AMO home page not the discovery pane.
(In reply to Jorge Villalobos [:jorgev] from comment #3)
> Bug 1009759 is an example of a promo content request. I suppose a similar
> approach would be needed for SeaMonkey.
That bug appears to be for the AMO home page not the discovery pane
Flags: needinfo?(jorge)
My understanding is that the same promo modules are used in both.
Flags: needinfo?(jorge)
Product: addons.mozilla.org → addons.mozilla.org Graveyard
Graveyard bugs will never be fixed.

If this must be fixed in AMO, please open a github issue wherever AMO bugs are now tracked. Nobody deigned tell me where that is.

If this can be fixed in some Bugzilla-tracked Product::Component, feel free to REOPEN it after moving it where it can be solved.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.