Rename package

[necolas]

The name "h5bp" is vague and it feels confusing to have a server config package named after a software organization. I'd suggest that an alternative name (that's clearer) is used at some point in the future.

[ngryman]

I agree.
Perhaps we could wait a little that it becomes a little more mature, and ideas would come naturally?

[xonecas]

+1

Maybe the first step would be to actually define the core functionality of this module and create a name from that. Or we can just come up with something funny, yet descriptive.

If I had to choose Node's HTML5 tuxedo would be my choice (I'm trying to be funny)

[necolas]

bump

[ngryman]

Well, still at the same point :)
If I had to choose, I'll go for a simple h5bp-server:

[ngryman]

@arthurvr What do you think about this one? Should we? Or leave it.

[arthurvr]

We should change it IMHO.

[ngryman]

Let's go for h5bp-server ?

[arthurvr]

I think that's okay. Other options could be server-configs-node, or h5bp-server-configs. Not sure but I would prefer it to be consistent with apache-server-configs.

[ngryman]

So let's go for h5bp-server?

IMHO:

• no need to mention node in the name as it's on npm.
• it's not a config but a server, so configs in the name seems weird.
• mentioning h5bp is important as there is no context on npm.

Checklist:

• rename the repo.
• open PR for other projects mentioning it.
• unpublish h5bp.
• publish h5bp-server.

Also, I think I'm gonna sync it with:

• Bumping version to 1.0.0.
• Merging the bump-deps branch.