Skip to content
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

Question: Why The Name Change? #39

Closed
ghost opened this issue Apr 12, 2015 · 7 comments
Closed

Question: Why The Name Change? #39

ghost opened this issue Apr 12, 2015 · 7 comments

Comments

@ghost
Copy link

ghost commented Apr 12, 2015

Hi gorhill,

Sorry if this is mentioned somewhere, I didn't notice.

So why the change in name to uBlocko?

thank you

@Unrepentant-Atheist
Copy link

Reading is hard....

Because now this version is a fork of the previous repo, I needed to also change name for installation purpose, which means that with this release, uBlock₀ will no longer fetch settings from former uBlock, so it will install as if it was the first time.

https://github.com/gorhill/uBlock/releases

@ghost
Copy link
Author

ghost commented Apr 12, 2015

Reading is hard, LOL...

I saw the releases section but I don't see it come out and say WHY the name change.

Just because something is a fork of a previous repo, what does that have to do with anything?

Isn't this still the same developers, who also maintained the previous repo too?

Hmm

@Havokdan
Copy link

Hey, how projects had the same name, shared the same settings, because the folder where they were ended up being the same, with the division in the project, with time, there is the possibility of a project to have something that the other does not, eventually trigger incompatibilities, and another for the extensions have many name shop at the chrome browser, opera, firefox and others.

@jarodsteele
Copy link

I also like to know what about the add-on AMO (https://addons.mozilla.org/en-US/firefox/addon/ublock/).
Will it be updated by the new maintainer? I don't want to manually install new versions, I want to "set and forget" it... (using the Firefox auto updating mechanism).
Thanks.

@gorhill gorhill closed this as completed Apr 12, 2015
@gorhill
Copy link
Owner

gorhill commented Apr 12, 2015

Will it be updated by the new maintainer?

Yes.

@jarodsteele
Copy link

ok, thank you for clarification (also for creating ublock!)

@ghost
Copy link
Author

ghost commented Apr 14, 2015

To begin with, I'm not here to troll or give you gorhill or anyone a hard time, I'm just trying to come to an understanding here is all, it's a bit confusing. So please try to look at it from the end-users point of view.

From what I'm reading, Gorhill, you are the developer of uBlock, then from all I know at this point, you leave uBlock and start another one called uBlocko. In the world of computing a developer can certainly do what he/she wants, but from the perspective of Credibility in a Project, I feel this is not the way to go about it.

From the end-users point of view is, we now have 2 uBlocks we need to figure out which to always choose from, always confusing us, always having to follow both to see which is doing what. And then as an end-user, we just ask ourselves, why can't we just have one version, which is the best logic in our minds.

Again, I'm not here to troll or flame you gorhill, or anyone, because I'm well aware, that maybe this was done with things not going well and people not in happy situations, so if things somehow were bad in the past, then I'm sorry for whatever went wrong.

I've personally never witnessed a change like this in FOSS, so I find it quite odd, and in the long run, it's going to take time to see whether it hurts the project or not.

I personally also think that when you Fork you change the Name to something completly different, as a Stand Alone Project on it's on, only in Relation to the Past project, not the Present or Future Project.

It would of been better maybe to of called this New Fork instead as example; aBlock :)

geoffdutton pushed a commit to geoffdutton/uBlock that referenced this issue May 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants