Page MenuHomePhabricator

Maintain consistency between Firefox and Chrome extension repositories
Closed, ResolvedPublicBUG REPORT

Description

What is the problem?

Between the WWT extension entry in Firefox Add-Ons and Chrome Store I have noticed some inconsistency, particularly in the descriptions of the extension.

See below for list.

Proposal:

  1. As much as possible, make the Firefox and Chrome versions consistent.
  2. Investigate tools and/or processes that maintain consistency in the future if, for example, we decide to change description/name/links/etc.

This is complicated by the fact the Firefox Add-Ons repo supports HTML (for example, you can have links in the description), but Chrome Store does not.

Also, I don't know how this relates to translations.

Inconsistencies
  1. Extension description:

As it appears in Chrome Store and in chrome://extensions: Explore Wikipedia authorship information. Powered by WikiWho. This is the BETA version, intended for testing only.
As it appears in Firefox Add-Ons and about:addons: Explore authorship and revision information visually and directly in Wikipedia articles. Powered by WikiWho.

  1. Rest of the extension text.

As it appears on Chrome Store:

Explore authorship and revision information visually and directly in Wikipedia articles. Powered by WikiWho.

This is the BETA version, intended for testing only and likely to contain bugs. The production version is not yet available.

As it appears on Firefox Add-Ons and about:addons:

Who Wrote That? is a tool for viewing articles' authorship information in Wikipedia. It is powered by WikiWho.

This is the BETA version, intended for testing only and likely to contain bugs. The production version is not yet available. If you find any issues, please report them on our Phabricator board.
Screenshots (if applicable):

WWT entry as it appears in Firefox Add-Ons repository:

firefox_addons.png (606×1 px, 60 KB)

After installing WWT, how it appears in about:addons:

firefox_about.png (857×711 px, 56 KB)

Event Timeline

Hey @Samwilson, I'm tagging you so can check this out. Thanks!

I will bring all languages on both stores up to date with the latest (short) descriptions from the current i18n files. This will make the store descriptions match what's seen in the extension lists after installation.

I've also asked about other ways of doing this. The other issue with automating this is that when we upload a new version, we have to supply the source code, and there is currently no way to do that via the API.

ifried claimed this task.

I think the stores look good in their current form. The next stage is to remove the beta tags, which I have outlined in T243302. For this reason, I'm marking this ticket as Resolved. Thanks!