-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
Name #8
Comments
sounds good. Apollo? |
I like Apollo but there's already few JS projects — https://github.com/toddmotto/apollo, https://github.com/apollostack, https://www.npmjs.com/package/apollo |
Some other suggestions: @kangax kinda suggested We also can continue the babel/babylon (there's also babylonia) theme would could do |
We should avoid a gender-specific name IMO. On Friday, 27 May 2016, Henry Zhu notifications@github.com wrote:
Sebastian McKenzie |
I agree with Sebastian. David is just not a good name (I was only brainstorming through "small" characters). I like something neutral and unique-ish like Pixie. Apollo is nice too since it's soooort of gender neutral. how҉ àb̸o҉ut̸ ͞ Zalgo? :D Sent from my iPhone
|
All free names:
|
Ooh I like babili On Sat, Jul 9, 2016, 12:36 AM Federico Brigante notifications@github.com
|
b, ba, bab, bbl, byob |
These are all fun (we were just discussing in a channel) but I'm afraid are too short to be properly searchable/recognizable/identifieable-from-other-abbreviations-like-stock-market and so on. I still like Babili the best. I think we should go with that. |
+1 babili On Mon, Aug 1, 2016 at 2:30 PM Juriy Zaytsev notifications@github.com
|
Ok, took the name on npm in case https://www.npmjs.com/package/babili |
babili it is! |
Rename the repo? |
Are we planning on keeping the
babel-minify
name? Might be better to have a distinct name for it so it can be marketed better. Being separate from the Babel brand, regardless of if it's in the org might be better too since Babel has historically had the stigma of trying to be everything at once.The text was updated successfully, but these errors were encountered: