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

Rename packages from graphql-server- to apollo-server- #465

Merged
merged 6 commits into from
Jul 17, 2017

Conversation

martijnwalraven
Copy link
Contributor

No description provided.

@martijnwalraven martijnwalraven changed the title Rename packages from graphql-server- to apollo-server- Rename packages from graphql-server- to apollo-server- Jul 17, 2017
@martijnwalraven martijnwalraven merged commit 300c0cd into master Jul 17, 2017
@martijnwalraven martijnwalraven deleted the apollo-server-rename branch July 17, 2017 23:29
@DxCx
Copy link
Contributor

DxCx commented Jul 18, 2017

Oh?
the packages where originally called apollo-server-* and there was a decision to rename to graphql-server-*
can you explain?

CC @stubailo @helfer

@helfer
Copy link
Contributor

helfer commented Jul 18, 2017

@DxCx I don't know and I'm curious to know the answer myself.

@stubailo
Copy link
Contributor

Hi @DxCx @helfer - we were trying to move quickly so that we could get @helfer's 1.0 announcement out there, I think in the future it will be better to wait a bit to get more feedback.

I think originally one of the reasons for the rename from Apollo Server was that we didn't want people to think that it only worked with Apollo Client, and the name reinforced that it's a generic GraphQL server.

Today, it doesn't seem like that association is a big problem anymore, and it looks like the name is not completely sticking - a lot of people we talk to these days are using graphql-server but refer to it as "Apollo Server". One nice thing is that people are very excited about the Apollo association - they understand that the two technologies are decoupled, but enjoy the fact that they can use them together and be sure that they are compatible.

When we were thinking about the naming long term, it seemed bad to have a package which is officially named one thing, but is always colloquially called something else, since that might make it harder to find and talk about.

The strategy we decided on is intended to minimize negative impact to stuff like download counts and SEO. Let's talk about it during contributor weekly if you can come. We're thinking it will be good to publish both sets of packages in parallel for a bit while people have time to get used to the new name, and then add a deprecation warning to the graphql-server-* packages in a few weeks. In the meanwhile we can try to track down some of the most important tutorials and examples and get them to switch.

@helfer
Copy link
Contributor

helfer commented Jul 20, 2017

Makes sense, thanks for clarifying!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants