-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer CWS ownership to chrisaljoudi #57
Comments
I don't intend to transfer ownership of CWS, neither Opera store (which I will update soon). |
If you're abandoning/spending less time on this project why would you not want to let @chrisaljoudi provide updates and support for your current users? Most users are not going to uninstall your uBlock and switch to chrisaljoudi's version. Could you please explain why you don't want chrisaljoudi to provide updates to your uBlock? |
@eligrey are you trolling? |
@RandomAcronym I am not. @gorhill recently expressed that he would like chrisaljoudi to be the official "uBlock" and he renamed his old CWS entry to "uBlock Origin". gorhill himself is calling uBlock Origin a fork, so I think he should make a new entry for his Origin version and let chrisaljoudi control the official one (by using the account transfer form). gorhill already transferred ownership of the Firefox extension to Alex Vallat, so it's odd that he doesn't want to transfer ownership for both the Firefox and Chrome extensions. @gorhill My point is that uBlock Origin is not uBlock according to you, so why force previous uBlock users into using uBlock Origin instead of making a uBlock Origin entry of your own, and transferring the old entry to the new uBlock maintainer?
I already had uBlock installed. You changed it to uBlock Origin instead of making a new CWS entry. If a user has uBlock installed and wants to switch to uBlock Origin, then it makes sense to uninstall uBlock and install your Origin version. It doesn't make sense to automatically switch users to an opt-out fork, instead of making it opt-in. |
Yeah, unfortunately that's all he can do to transfer extensions (I wish you could just transfer a single extension). If he wants to keep updating µMatrix and HTTP Switchboard he would have to push an update that notifies users to install a new version before transferring account ownership. |
Even if I could transfer on a per-extension basis, I would not transfer it. I will keep maintaining my version just fine -- and these users can completely count on me to prevent uBlock Origin from working against their interests by becoming tainted with "cooperation" etc. with for-profit entities which is never going to be in users' interests. I still can not make sense of your rationale of why I should hand over the user base of uBlock Origin -- which is essentially what your request amount to. There is a bad vibe to this request. |
I'm a Firefox user and I had originally installed uBlock from the Mozilla repository; following these recent developments, I've had to switch to your GitHub releases (which, if I understand correctly, have the disadvantage of being unable to automatically update themselves). I thank you for your generous work, but I don't understand the difference in treatment: if you say we (the old user base) can count on you to not hand us over to other developers, then why did you do just that with the Firefox user base? N.B.: I'm not implying I mistrust the new developers: I just want to stick with the original developer, as I'm not particularly interested in innovative features. |
Yes I feel bad about this one. @Deathamns published the Firefox version in AMO -- I had no idea he would also leave the maintainership of Firefox. Then it became a matter of whether I can take care of uBlock in AMO: I am completely new to Firefox API, and it will take some time before I feel competent enough to be able to deal with any Firefox issue which may arise, so to be completely responsible of uBlock on AMO on my own wasn't going to work. It needed to be maintained by someone with experience with Firefox API, and @AlexVallat was clearly better placed than I am for this. I am currently porting uMatrix to Firefox, using uBlock's Firefox work as the foundation, and I will use this opportunity to learn about Firefox API. So eventually, if both uBlock versions are divergent enough and if there is a demand for it, I may publish my own version to AMO. But very unlikely this will happen in the short term. |
You do not have to make a new CWS entry to allow chrisaljoudi to provide future updates for uBlock on the Chrome Web Store. You can fill out this form you can transfer ownership of your CWS extensions: https://support.google.com/chrome_webstore/contact/dev_account_transfer
Also off-topic question: Don't you own the copyright to the original icon used in uBlock? Have you told Google this? It seems odd that they forced you to change the extension icon when you were the one who (I presume) owns the icon.
The text was updated successfully, but these errors were encountered: