Replies: 15 comments 6 replies
|
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". |
|
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? |
|
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. |
|
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? |
|
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) |
|
I've accepted the google group invitation and am now a member of 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 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. |
|
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! |
|
I synced it. BTW, Eric also has admin rights |
|
Yes, now I'm able to do the transfer. Done. Very good, thanks for arranging this - this seems like a much better arrangement! |
|
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. |
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. |
Does that republish the unpublished listing? I think we should continue to update both while taking steps to "merge" the listings (and users).
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. |
|
I have added a gentle dialog to show once on each browser session startup to the PasswordMaker(.org) extension to urge users to install the primary "Pro" version on the Chrome Web Store. I'll be interested to see the users, installs and uninstalls. Hopefully everyone will have migrated within 6 months but we will see. PasswordMaker Pro is the official version Passwordmaker.org is the one I am depreciating: |
Uh oh!
There was an error while loading. Please reload this page.
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.
All reactions