Which extension is the official version?

[nicerobot]

Although this repository links to this extension: https://chromewebstore.google.com/detail/passwordmaker-org/fckpmekmkjglpmdcbfkchimdelcjiipd

The following extension was recently updated to the latest release that fixes recent bugs: https://chromewebstore.google.com/detail/passwordmaker-pro/lnhofcfhehhcbccpmdmdpjncdoihmkkh

Given the secure nature of this plugin, it should be noted somewhere about which is the official version and who is allowed to publish to the web-store. This should be cross-documented in the web-store and in the repository.

[miquelfire]

I'm pulling from my memory, so I may get some info wrong.

The second one you linked was the original version of the extension from this repository, but the author got too busy to do updates. Someone else came along to handle updates after that, hence why the first one you linked is the official version now. The first author recently came back to do more updates, and I'm assuming the one who is handling the official one hasn't had the time to publish a new version.

If the Chrome store allows you to make an organization where multiple people can submit updated versions, we should see about making one, so we can smoothly change who is allowed for publishing new versions.

At the very least, we should probably rename them so that it's "stable" and "beta".

[heavensrevenge]

Hello again @miquelfire, I believe it is possible to make a CWS group https://developer.chrome.com/docs/webstore/group-publishers/ would you like to create it?

[GitTom]

I'm the 'someone else' referred to above who created the 2nd Chrome store listing.

I agree that the current situation is not ideal, and I'm happy to transfer the listing to whatever Google account or group is agreed upon.

[heavensrevenge]

Any progress on this @miquelfire?

[miquelfire]

When I looked into it, each Google account is allowed 1 orig for the lifetime of the account. I won't be making the orig at this time.

[ericjung]

I'm the original creator of PasswordMaker as own the passwordmaker.org domain. As @miquelfire hints, the docs at https://developer.chrome.com/docs/webstore/group-publishers/ says: " Chrome Web Store developer account can only create one group publisher, ever. You cannot replenish this quota, even if you delete the group. Warning: Deleting the group publisher and the Google Group does not restore your lifetime quota of one group publisher activation."

Therefore, I think we should create a new Google account, something like passwordmaker@gmail.com, and use that to setup the group. Any volunteers?

[miquelfire]

I have set up a group to use for publishing. Just need to add people to the group (and set an admin so I'm not the only one in control)

[heavensrevenge]

Right on @miquelfire, I'll at least join the group however that is done. And should we agree upon a canonical Chrome Web Store extension name going forward as the (.org) is a bit messy/confusing?
It is interesting to note that I somehow still have over 800 users on my Chrome Web Store version... which I can direct towards more explicitly upon reaching an agreement here from you, @ericjung and @GitTom or whomever wants to chime in.

[miquelfire]

@ericjung and @GitTom, I need an email address to send the invite to. You can send me a PM on the forums.

[heavensrevenge]

Oh @miquelfire could you give @GitTom another invite to that publishing group? Apparently the original one expired so he can't transfer the (.org) extension into the group so hopefully I'll be able to do the updating atm.

[GitTom]

I've accepted the google group invitation and am now a member of
https://groups.google.com/g/passwordmaker

But in chrome web store dev dashboard, I select 'Transfer item to group publisher' for the listing (it looks like this), and the 'group publisher' dropdown that appears is greyed out. The same for "Group publisher memberships" for my account.

I think either

• I need to be an admin in the group.
• I need to wait for the effect of my group membership to work its way thru their system
• I still need to manually request the transfer here
  https://support.google.com/chrome_webstore/contact/one_stop_support

[heavensrevenge]

I believe @miquelfire will have to "Sync" the account manually upon your addition. Here @miquelfire https://developer.chrome.com/docs/webstore/group-publishers/#adding_developers_to_or_removing_them_from_the_group_publisher

Then you should be able to do it. I'd do it but I'm not an admin of the group.

[heavensrevenge]

Hey @miquelfire could you sync the group? Referenced https://developer.chrome.com/docs/webstore/group-publishers/#adding_developers_to_or_removing_them_from_the_group_publisher

Thanks!

[miquelfire]

I synced it.

BTW, Eric also has admin rights

[GitTom]

Yes, now I'm able to do the transfer. Done.

Very good, thanks for arranging this - this seems like a much better arrangement!

[heavensrevenge]

Alright @GitTom I'm able to update both. Now for a tricky question: do we want to rename the canonical extension to something other than what we have or should one of the extensions stop existing? I only updated mine since I had over 400 users even after mine was removed from the store and had to update them but now I'm at mid 800 as you'll be able to see the stats of my "Pro" version if you check it in the dev dashboard you have access to now. Your opinion on the matter would be appreciated.

[ericjung]

should one of the extensions stop existing?

I think you mean "Unpublish". From what I read online, that does not uninstall the extension in browsers that already have it installed. Effectively, you permanently lock them into the version they have installed - unless you decide to upload a new version of the "unpublished" extension.

So I'm not sure unpublishing is a good idea. i think it's better to just maintain both of them; use the same codebase for both but when there is a new version, update both listings. That's my opinion. I am in a similar situation with FoxyProxy. There is simply no way to "merge" listings.

[heavensrevenge]

Merging them would have been great if possible, but ATM since we can all publish both whenever required the hurdle is reduced by having the publishing group set up.
For the time being, if everyone prefers to keep updating both then alright.

The only problem is the discussion topic, will having both be available confuse people looking?

@nicerobot how confusing is it having 2 identical versions to pick from but with complete feature equivalence?

[nicerobot]

Thanks to all of you for getting this done.

I think adding a sentence or two with a link to the primary extension to explain will be good enough. I agree with #196 (comment), though, maybe instead of eventually removing/unpublishing the .org extension, it can eventually become a beta-release of the extension.

[jeremy-harnois]

Effectively, you permanently lock them into the version they have installed - unless you decide to upload a new version of the "unpublished" extension.

Does that republish the unpublished listing?

I think we should continue to update both while taking steps to "merge" the listings (and users).

1. Unpublish one (probably the .org one even though it has a higher rating 😉 the pro one has more users and screenshots)
2. Create some documentation somewhere about the situation; include steps to migrate from one to the other
3. Branch a version and add a notice with links to the documentation
4. Publish the branch to the unpublished listing
5. Publish master to the published listing

After a specified time, even if it's a year, or when the listing shows no users, delete the unpublished listing. Anyone who didn't migrate will go looking for the extension and find the published listing.