Suggestion: change package name #3

Closed
karthik opened this Issue Oct 3, 2012 · 7 comments

Projects

None yet

4 participants

@karthik

to something like ggplot_themes or something else easier to remember and type. The camel case + your abbreviated name is really unwieldy.

@ramnathv

I would second that. I have never managed to load this package in less than three attempts, due to typos. My recommendation for the name would be something simpler like ggthemes.

@karthik
@jrnold
Owner

I'm fine with changing the name. I had originally named it as it is because I wasn't expecting other people to actually use it, and I just wanted to be clear that this was just some random stuff written for ggplot by me (in the spirit of Hmisc and gmisc). But now that a few people are using (or at least staring it), I guess a name change is in order. ggthemes sounds good. Some other likely alternatives are out, ggmisc wouldn't work because of gmisc and ggextras already exists (existed). ggstuff or ggetc are the only other natural alternatives I can think of. What do you prefer?

After that I'll make a new rep that is a fork of this, and change name of the package in DESCRIPTION.

@karthik

I'd vote for ggthemes since it succinctly captures the purpose of the package. There is no need to fork the repo. Just go into admin, change the name, change the name in the DESCRIPTION and update the documentation/checks one more time. That way you wont lose your followers (much like changing the name of a twitter handle) and people just have to run install_github with the new name (which they have to do for updates anyway.

@jknowles

I vote for ggthemes as well. This adds some much needed functionality to ggplot2, easy theme switching to some new base themes, and I think the name ggthemes makes it very clear what the package can be expected to do.

@jrnold
Owner

Okay, i'll change the package name to ggthemes. Thanks for the suggestions! That should happen in the next couple of days; I'm a little busy with a conference this weekend.

@karthikram Good point. The purpose of forking was simply to keep a working URL at the existing location, which would be lost when I change the name of the repo. But it makes more sense to change the name of repo, and then make a dummy repository at the old URL with just a README pointing people to the new location.

@jrnold jrnold closed this in 74de502 Oct 4, 2012
@jrnold
Owner

done thanks to a delayed flight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment