-
Notifications
You must be signed in to change notification settings - Fork 970
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
Change the name of gocd #128
Comments
I don't think this is feasible proposal, it happened and waste heavily cost on branding. i suggest focus on Usability,Feature, architecture |
Of course it's your decision to choose a name of your liking. There are many reasons for a name change, though:
You know, your experience right now is the same as my first experience with delivering FOSS. People always talk about stuff that you certainly didn't want to change, and they refuse to talk about things that might actually be important. :-) |
TL;DR - Most of the current committers would like to change the name too, just not sure how high priority it is, and it's a LOT of work. @erikb85 Many of us who were involved in some way with Go before it was converted to open source are in complete agreement around the issues with the name. Heck, the two GH issues filed on this were both filed by TW'ers, one of whom is a committer on the project. Most of the questions (again, not all) about the name now coming from outside of ThoughtWorks aren't actually users of the product, just reacting to the first time they are seeing the name. I think this is why many people seem to think it's a new product with a recently chosen name. What we really need to decide from the community of people actually using Go is this; where does this rank against all of the other things you would like the product to do? It really is a tremendous amount of work. Heck, there's still quite a bit of tech debt around from the name change 4 years ago. It's there because the users of the product told us loud and clear that they where more interested in new features. There's a high level list of the kind of things the current team thinks should be next at http://www.go.cd/contribute/roadmap.html. Of of that said, this truly is an open source project now. If the community of users feels strong enough about this that they believe it should be higher on the priority list and they are willing to contribute to making it happen, that's how things like this get done. |
I created #131 and Im a committer on Go. I know its excruciating amount of work to rename a product both on the dev side & the branding side having done one rename ourselves! I created it to gauge the interest in the community. I also wanted to explain why its a lot of work, which @kmugrage's reply is doing. I tried finding an existing issue for it din't find any so created one. Sorry for the confusion. |
I'd like to +1 this issue. Searching for Go-related topics is terrible. I always look for "gocd" (in quotes otherwise Google ignores it probably because there are too few results) but then not everyone uses this terminology (which may explain the too few results). When I talk about this product, I always refer to it as go-cd as well (gow-see-dee). What about re-branding it to "GoCD" would be sufficient so people can officially start referring to this tool in almost the same way as they were used to and having more letters as part of the official name would make it a better discriminator. Obviously, the documentation would have to be updated, as well as the logo, other text/UI elements of the app, etc. That being said, the internal variables names that are go-branded could stay unchanged (e.g., environment variables could be kept prefixed as This effort would make the branding change less disruptive. Also, because "Go" and "GoCD" are almost the same, the effort to change the name may be iterative meaning that not everything has to change at once -- if there are places where I see "Go" and others where I see "GoCD", meh, it's likely that I'll understand what you mean. Of course, documentation wise, it's better to be consistent but I'm less worried about this part, a find/replace will likely do most of the job. Packages available for download are branded as I think this could be a good intermediate approach. If this approach still isn't enough then maybe more thoughts and efforts can be put into finding a brand new name. |
I'm not (yet) a committer but a happy user and yesterday I created #843 The core of my point: this is not a matter of taste ("Go" is quite cool), the current name is a real productivity killer. |
#843 is quite persuasive , and I'm feeling the exactly same pain when I tried to google some puzzle with "go". As go-cd is open-sourced and been expected to be widely used, googlable is quite a matter for new users, mail-list is no longer a fashion, and Google or stackoverflow is, searching is. So keep using a a name which is consistent and easy to distinguish, is quite important. |
Slowly, it's organically changing to "GoCD". Closing this. |
Go is a really hard language to find and identify. We should change the name to something memorable, short and googlable.
The text was updated successfully, but these errors were encountered: