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 to strum? #16

Closed
shaunlebron opened this issue Aug 21, 2017 · 8 comments
Closed

Rename to strum? #16

shaunlebron opened this issue Aug 21, 2017 · 8 comments

Comments

@shaunlebron
Copy link
Contributor

STate manage for Rum?

@escherize was telling me about this library, and I thought Scrum was a confusing name :)

@roman01la
Copy link
Collaborator

I like this confusing name TBH :)
P.S.
SCRUM stands for "State Coordination for RUM"

@shaunlebron
Copy link
Contributor Author

I think a name should be more than clever, right? The acronym is clever, but confusing and I think that makes it bad. And since we both care about the ClojureScript experience, naming is a part of how we make the experience better (which is why I'm actually renaming Parinfer soon!)

In the context of how I heard it in conversation with Bryan:

Bryan: Have you heard of Scrum?

Me (internally): Yeah, it's that annoying standup thing I gotta do every morning that no one does correctly. :D

(🚲 🏚 )

@roman01la
Copy link
Collaborator

Ok, I'm all open to make it more accessible. Do you want to propose possible migration plan?

@roman01la roman01la reopened this Aug 22, 2017
@shaunlebron
Copy link
Contributor Author

Thanks for being open to this! Some thoughts on migrating:

Clojars

old: [org.roman01la/scrum "2.3.0-SNAPSHOT"]
new: [org.roman01la/strum "3.0.0"]
  1. Publish new package name: Some precedent here—om was renamed to org.omcljs/om some time ago, and both are still available, with only the latter receiving updates. Only publish updates to the new name, and leave the old as is.
  2. Increment major version: Since the namespace rename constitutes a breaking change, I'm thinking we have to increment the major version number.

Repos

  1. Renaming the github repo should be fine since all old urls will be redirected, of course.
  2. Rename/migrate scrum-ssr-example and migrate cljs-rum-realworld-example-app

Users

  1. Tell users to s/scrum/strum/g relevant files.
  2. Put a notice at the top of the repo readme, above the title.
  3. Post on clojurescript mailing list and twitter.
  4. Rename slack channel

If we want to be extra proactive (probably not necessary):

  1. Search org.roman01la/scrum on github and send PRs.
  2. For projects not on github, create a reasonably safe rename script for them?

@oakmac
Copy link

oakmac commented Aug 22, 2017

I would like to propose the name citrus for this library.

I am a big fan of Rum the library, as well as Rum the liquor. In almost every classic Rum-based cocktail, citrus is used as an ingredient to 1) pair with the sugar-based flavor of the Rum and 2) smooth the harshness of the alcohol flavor.

Wherever you find Rum, it is almost always accompanied with some form of citrus to control and balance the cocktail. I think it is very fitting for how this library pairs with Rum.

@roman01la
Copy link
Collaborator

@oakmac You just sold me this name 😀

@roman01la
Copy link
Collaborator

@shaunlebron Thank you very much for such detailed plan! I'll follow it when I'll have time to start migration process.

@roman01la roman01la mentioned this issue Aug 23, 2017
10 tasks
@roman01la
Copy link
Collaborator

most of the migration path is done, follow tracking issue here #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants