Mechanisms for converging store and snap metadata

[matiasb]

@mpt

Maybe, but I don’t see how that’s viable long-term, for the reason I gave. A vendor shouldn’t be prevented from mentioning their app’s cool new features, in the app description, merely because they’re thoughtfully also providing an old version for enterprise/low-end users.

I raised it because it would save time and confusion if conflict handling is designed to work as similarly as practical, now, as it will when per-version descriptions are introduced.

I see your point, and I agree we would probably want some metadata per revision. That will require another discussion and extra work to be scheduled. We are adding a session for next week in the rally.

@mpt

Another issue that might influence conflict handling is localization. Apparently descriptions aren’t localizable yet.

FTR, there is (basic) store support to set translated metadata (and also screenshots), although translated details are not yet exposed to clients. There is a discussion going on here, Getting translated snap metadata via snapd, and there is a session scheduled for next week too. It will be great to also have input from the snapcraft team on how translations would be ideally managed from the client side (and discuss how this could affect the task being discussed here).