Thinking about new name

[Alexmitter]

As @lucaswerkmeister gave the idea, lets discuss the idea of changing the name, giving the fork a clear identity as a successor.

First idea came from @lucaswerkmeister as: "For now I’ve kept the Corebird name, but if @baedert would prefer a different name I’m sure we can find something. (Personally, I’ve always liked the “Iceweasel” joke. What would be the opposite of Corebird – Crustpenguin?)"

As correctly mentioned, changing the name is not needed as long as @baedert does not request it, but thinking about it is defiantly not wrong.

[freecicero]

There's always the imaginative "Corebird2." Maybe it would help in brainstorming to consider where "Corebird" came from in the first place. I understand the "bird" but where did "core" come from?

[lucaswerkmeister]

To be clear, personally I would prefer to keep the name unless we have to change it. That way it’s much easier to discover this fork.

[Alexmitter]

@lucaswerkmeister as you choose. It is your fork.

[lucaswerkmeister]

Well, ideally it wouldn’t just be me working on this but some other people as well :)

[Alexmitter]

@lucaswerkmeister Thats clear. I already tried to get some attention to this project but most of the Linux world seems to be not so Twitter friendly. Idk maybe a introduction on reddit would help here. As i said, i would like to try to do the deb packaging but it seems you are quite fixed on flatpak.

[lucaswerkmeister]

To give a bit more context – when I wrote my earlier comment, I had changed a grand total of one line in Corebird, to replace the constant 45 with 120 (bfc738d7529da9b52090b199bf475fe1f0b6dec1). So while the argument of “it’s easier to discover this fork” was part of the reason I wasn’t keen on a rename (and that argument is still valid), another reason was that I didn’t feel the changes were “significant enough” for a rename, so to speak.

However, in #9 @TingPing argued that not renaming/rebranding could also lead to user confusion, and might even be dishonest or disrespectful. I’m not sure I agree with that yet, but if enough people feel that way, then it doesn’t really matter what I think: if keeping the name is widely perceived as disrespectful, the rename should be done, period.

Also, for the Flatpak submission I’ve already had to change some hundreds of lines in order to change the package identifier from org.baedert.corebird to de.lucaswerkmeister.corebird, and at this point I feel like we might as well go all the way, and change the corebird part as well.

So while I’d like to think about this a bit more before making a final decision, at this point a rename is starting to look more likely.

I’m still not keen on the “Crustpenguin” though, and I’m not sure “Corebird2” is sufficiently non-dishonest…

[pizzadude]

How about CorebirdFork?

...or...

Corebird-NG?

Corebird-Reloaded?

[lucaswerkmeister]

I think I’d spell it without a hyphen, but CorebirdNG sounds okay.

Or perhaps NextBird? (Nextbird?)

[freecicero]

argh I am on Mx17 and the new builds want gstreamer 1.0-gtk3 which I don't seem to have, so I am locked out for the moment. BUT I wanted to say that the name Nextbird sounds cool to me! And it actually makes more sense than "Corebird" does because I never figured out where that "core" came from!

[lucaswerkmeister]

I just realized that a rename should probably include a logo change, as well. Any volunteers for that? (Though I don’t think it needs to block the rename.)

I quite like the “Nextbird” name, too, so unless I hear any objections I’ll probably go ahead with that in the next few days. I’ll probably bump the version number to 2.0.0 then, to make a clean break between Corebird history (1.x) and Nextbird history (2.x).

One final question: how important is it to y’all that Nextbird will be able to import Corebird’s application data? Because setting that up would probably be difficult (depending on distribution mechanism), and personally I’m quite tempted to avoid that problem by not supporting this: after all, Corebird has few settings of its own (except for snippets, I guess?), and the process to add an account to it is very straightforward.

[pizzadude]

I just realized that a rename should probably include a logo change, as well. Any volunteers for that?

I would try, but I'm not an expert graphic designer. Most of my drawings are crude. Examples: https://i.imgur.com/z5lluJD.jpg https://i.imgur.com/9LokLdE.png

how important is it to y’all that Nextbird will be able to import Corebird’s application data?

Not very important.

Also, Nextbird sounds like a cool name.

[Alexmitter]

I like Nextbird, its a sweet name.

About the logo, should we base it on the old one, what kind of theme should be in focus if we go away from the open brain bird. If we have a concept i can ask for help at some places.

Edit: @lucaswerkmeister not important, as it is basically only 5 settings and the login.

[pizzadude]

How about a robotic bird? Or a superhero bird?

[TingPing]

The GNOME designers are mid icon refresh and seem open to helping with app icons.

[lucaswerkmeister]

Hold on, hold on, let’s make that a dedicated issue :) see #11.

[freecicero]

1 - importing Corebird data is of no consequence to me at all 2 - if the bird were a superhero design an "N" on its chest would be logical

[lucaswerkmeister]

I’ve moved the repository and implemented the rename in #12 – feel free to review! This is the first tweet made from the new “Nextbird” app (though I’m not sure if you can see that easily anywhere).

[Alexmitter]

@lucaswerkmeister did you find any problems with it since you compiled it for yourself? If no, i guess its time to merge.