Closed Bug 1173431 Opened 9 years ago Closed 7 years ago

extend sumo suggest provider to cover all locales supported by sumo

Categories

(Input :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: willkg, Unassigned)

References

Details

(Whiteboard: u=user c=feedback p=3 s=input.2015q4)

We just pushed out a SUMO Suggest provider which only looks at Input feedback for the en-US locale and the Firefox product.

This bug covers extending that to other locales and products that SUMO supports.

There are some caveats:

1. Input and SUMO don't support the same set of products. We'll probably need to create and maintain a mapping of which Input products map to which SUMO products and which Input products don't have a SUMO match.

2. Input and SUMO don't support the same set of locales. We'll need to do the same mapping thing here, too.

3. We probably want to see event flow information in Google generally (across all locales and products) as well as by locale and by product to help us understand how to hone the SUMO suggestions algorithm. Ricky mentioned using custom variables for this:

https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables

I'm not sure what other options there are.

This bug covers figuring out the above and doing the work. It's possible this is a big project and we should call it "phase 2" and turn this into a tracker.

We don't want to do this work until after we've done analysis on the success of phase 1 (bug #1173430). Also, we might want to hone the algorithm for generating suggestions, too.
I think this is 3 points of work. We need to figure out how to deal with the caveats in a way that's dynamic so that the SUMO devs are ok with it and we're not manually updating things over time. Further we want to adjust the GA event categories appropriately so that we can track flows in a more granular way. It's possible that's not even possible. We might want to break this up into multiple bugs.
Whiteboard: u=user c=feedback p= s= → u=user c=feedback p=3 s=input.2015q3
Assignee: nobody → willkg
Status: NEW → ASSIGNED
I'm reducing the scope of this down to just the locales part. We can deal with products in another bug. I'll write up the products bug later.
Summary: extend sumo suggest provider to cover all locales and products supported by sumo → extend sumo suggest provider to cover all locales supported by sumo
Making this a P2. It's a bunch of work, but it's worth doing because supporting non-English is important.
Priority: -- → P2
Depends on: 1194899
New quarter!
Whiteboard: u=user c=feedback p=3 s=input.2015q3 → u=user c=feedback p=3 s=input.2015q4
I implemented the locales api, it landed and was pushed out yesterday. I can work on this now.

Docs for the locales api are here:

http://kitsune.readthedocs.org/en/latest/api.html#locales-api

I think we can cache the output of the api in memory. Then we don't have network-related lookup costs. Still need to figure out an algorithm for figuring out which SUMO locale to use given an Input locale.
I'm unassigning myself from this. I'm not going to get to it before I transition off.
Assignee: willkg → nobody
Status: ASSIGNED → NEW
The Input service has been decommissioned (see bug 1315316) and has been replaced by a redirect to an external vendor (SurveyGizmo). I'm bulk WONTFIXing Input bugs that do not appear to be relevant anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.