-
Notifications
You must be signed in to change notification settings - Fork 35.6k
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
Rebrand client to 'Bitcoin Core' #3203
Comments
Bitcoin-the-system has always been abbreviated as 'bc', not 'bt' - wouldn't 'bccore'* make more sense here? I think it would be better to keep Bitcoin-Qt and bitcoind more distinct. After all, someone may develop another GUI client sharing the same codebase someday as well. |
Well I found the fun thing about btcore that the first three letters are BTC. Apart from that, I don't really mind, bc, bt, even xbcore has been proposed. IMO if someone else wants to develop another GUI client sharing the same codebase let him/her think of their own name. This is our project. |
Due to the nature of the codebase right now, any other GUI would obviously need to share the same repository as B-Qt and bitcoind have been. On the other hand, "let them think of their own name" seems fine. I just think B-Qt and bitcoind should also have their own names ;) |
Perfect is the enemy of better, @luke-jr Someday maybe we'll have a libbtcore.a and separate projects for the GUI btcore and btcored/btcore-cli (and maybe there will be a gazillion other wallets that use libbtcore.a). Now is a good time to change names, lets do it. |
@AllThingsBitcoin We do not generally use the "assignment" feature in Github. The number of active participants here is small enough that software coordination of who is working on what isn't terribly helpful. |
I'm not sure if I like that new name, even |
@Diapolo we're open to suggestions, but mind that there have been many discussions about a new name and the time to shedpaint about is limited - at a certain point we should simply make a decision Edit: and I don't want to add -gui, at least not to the full name, a lot of users have no clue what "GUI" means and simply expect an "application" these days. |
|
That's only the executable name. Capitalization doesn't matter. Let's not discuss that but the user visible name in menus and dialogs. "Bitcoin Core" is cooler than "Bitcoin Reference Client" right? |
I agree on the rebranding. +1 what @laanwj said about doing this in one swift move instead of drawn out. I think the name is subjective. Perhaps we should go to the community about this to come up with a name everyone likes. |
To add my own shed paint:
(btcore sounds to me like it's a BitTorrent client) |
No strong opinions from me. This is okay and I don't think I've ever heard an alternative I would consider really fantastic. |
We're not in any danger of running out of letters, I'd prefer something explicit like the binary names being "bitcoin-core" or "bitcoin-core-daemon" because then it's immediately apparent what something is if you do a process listing on an unfamiliar box. However this is practically a Gaudi-inspired bike shed, so who cares :) |
I tend to agree with @mikehearn here. |
@mikehearn Disagree. I've had to type in bitcoind many many times. I think brevity is key. |
Building on Mike's idea:
(similar to transmission-cli and transmission-gtk) |
@sipa bitcoin-core-qt would probably be better in that case |
I officially have no opinion on this issue ;p |
I say let the community decide. I put together a little Google Form: Thoughts? |
I think the idea of letting the community have input on shedpainting like this is fine. But your form kinda sucks, since it doesn't provide any real options. B-Qt name: Bitcoin-Qt (no change), Bitcoin Core, Bitcoin Core GUI, Mercury, BitcoinPeer, CuteCoin, Hikaru, Bitcoin Basic, etc From those, it's pretty trivial to infer binary and bitcoin-cli names. |
Alright. I can agree. Give me some more guidance on how it should look then I think the idea of letting the community have input on shedpainting like B-Qt name: Bitcoin-Qt (no change), Bitcoin Core, Bitcoin Core GUI, Mercury, From those, it's pretty trivial to infer binary and bitcoin-cli names. — |
I'm tired of painting sheds. This is how it is gonna be: Branded name : executable name Who wants to do it? |
I always find these "a day ago" too late... Filename "bitcoin-core-gui" - really? Can we just have "bitcoin" (or "bitcoin.exe") again? See Bittorrent as an example of a protocol plus a reference client with the same name, and nobody seems overly confused Fictional but painfully real anecdote: Try giving tech support over the phone "you need to rename bitcoin dash core dash goo eee, spelled gee-you-eye", "Now I will have you type t-a-r space x-z-v-f space bitcoin dash core dash goo eee dot tar dot gz" ... "okay, 'can't open' likely means you typed it wrong"... |
…#3203) * Bump version to 0.14.0.4 * Run gen-manpages.sh to update versions * Prepare release notes for 0.14.0.4 * Add first draft of "Notable Changes" * Handle review comments
To remove the confusion between the Bitcoin network and the reference client implementation that we maintain in this repository, both confusingly named 'bitcoin', we'd like to rebrand the client.
This has been discussed a lot before, but the following is the proposal by @gavinandresen and I agree:
Renaming the executables is going to break some scripts, so we'd likely want to combine it with the bitcoind CLI deprecation to make sure the migration pain is short and swift instead of drawn out.
The text was updated successfully, but these errors were encountered: