Closed Bug 1902118 Opened 2 years ago Closed 2 years ago

please create new collection "newtab-wallpapers-v2"

Categories

(Cloud Services :: Server: Remote Settings, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nbarrett, Assigned: acottner)

Details

Collection name: newtab-wallpapers-v2 (eg. fingerprint-fonts, focus-experiments, ...)
Description: Collection of attached images that will be used on the newtab page
Estimated collection size: ~28 records, ~100 kB / record

List of LDAP emails allowed to change the records (editors):

nbarrett@mozilla.com
achurchwell@mozilla.com
sdowne@mozilla.com
mcrawford@mozilla.com

List of LDAP emails allowed to approve the changes (reviewers)

sdowne@mozilla.com
nbarrett@mozilla.com
achurchwell@mozilla.com
mcrawford@mozilla.com

(optional) Allow file attachments on records: YES
(optional) Are attachments required on records: No
(optional) List of fields names to display as columns in the records list UI: title, category
(optional) JSON schema to validate records (in YAML format): https://gist.github.com/nathan-barrett/894456195b5bbfe3543824bdf3557d2e

Assignee: mathieu → acottner
Status: NEW → ASSIGNED

Nathan, could you please give us a bit of details why a v2 is required? Or a link to another bug?
The diff in the schema seems relatively limited that's why I'm curious :) Only a new field solid_color and high-contrast in the theme enum. Are you stuck with backwards compatibility?
It could be worth adding this rationale in the collection description too IMO.

Flags: needinfo?(nbarrett)

Also, we can run a cronjob that backports records to the old collection automatically in case you'd need it.

Hey Mathieu - here is the associated bug for the v2 version of wallpapers: https://bugzilla.mozilla.org/show_bug.cgi?id=1899796. Essentially, the idea was that the first version will be running an experiment at the same time that version 2 is landing in nightly. Since the experiment is starting next week, we needed a way to work on both simultaneously. Once the experiement has wrapped up for version 1, and we switch to the newer version we would remove the original "newtab-wallpapers" collection from remote settings. :thecount maybe have more info if that is helpful.
Version one only has 12 items that are shown, while version2 has 28 i believe. I originally tried to find a solution using a single collection, but it would require a a code change that would need to ride the trains.

Flags: needinfo?(sdowne)
Flags: needinfo?(nbarrett)
Flags: needinfo?(mathieu)

That is pretty much it. I would only add a few notes. The reason why any solution that would ride the trains is an issue is timing. We wanted v2 as a pretty fast followup to v1, and if we waited until v1 was done before making a fix in nightly, it would cause delays.

The reason why we're doing a v1 and v2 is, v1 is not testing v2, we are pretty sure already about the value of v1 to v2.

v1 was just the quick way to get it out there and so we could test the impact (potentially positive and negative) this would have on our other guard rails metrics like search and sponsored content.

Flags: needinfo?(sdowne)

Thank you for the details! It was worth a few notes 😉

We created the collection.

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(mathieu)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.