Change org/repo to: libhamster/hamster.gem

[krainboltgreene]

So I've recently been using {name}.gem to denote gem repositories, both for human searching an machine searching improvement.

In addition I've realized that some of these libraries transcend the original language, like Hamster.

I'd like to propose renaming the organization and repository. This means:

• Renaming the organization
• Renaming the repository
• Updating travis-ci
• Updating codeclimate
• Updating gemnasium

In addition we will need to update our own remote uri.

Anyone object?

[dubek]

Why not follow the scheme used by other popular gems:

• https://github.com/sinatra/sinatra
• https://github.com/rack/rack
• https://github.com/bundler/bundler

Can you give examples of repos using the {name}.gem scheme?

[dubek]

(and add to the checklist: modify the github path in hamster.gemspec)

[krainboltgreene]

Because "hamster" is a really general term, and we don't need to be taking
that namespace for a collection library.

As for the {name}.gem, all of mine quite a few in plus
https://github.com/search?utf8=%E2%9C%93&q=.gem&type=Repositories&ref=searchresults
.

On Tue Nov 04 2014 at 7:06:32 PM Dov Murik [email protected] wrote:

(and add to the checklist: modify the github path in hamster.gemspec)

—
Reply to this email directly or view it on GitHub
#157 (comment).

[dubek]

OK I don't mind either way.

[krainboltgreene]

@hamstergem/contributors Any thoughts on just changing the name in general from hamster?

[alexdowad]

It's fine either way. People who use the gem are affected more by the gem name, not the GH organization and repo name.

[krainboltgreene]

Sorry I meant to something more symbolic of the situation, like: "immutable_collection" or similar.

[alexdowad]

@krainboltgreene I have a fork of this gem going called immutable-ruby, repo is here: https://github.com/immutable-ruby/immutable-ruby. Not sure if it will garner much attention. If you want to work on it, just say the word and I will give you commit rights.

[krainboltgreene]

@alexdowad We could just redirect hamster to immutable-ruby.

[alexdowad]

But hamster already has existing users, and we don't want to break things for them.

[plexus]

I prefer a memorable and marketable name like Hamster over something descriptive but bland. Hamster already has some mindshare, so my vote is on keeping the name.

[dubek]

I'm against changing the repo name. There are already 7 non-related github repos called "hamster". I don't see any reason we should clear this already-crowded space.

As for the org name, I'm indifferent: hamstergem / libhamster / ruby-immutable -- all work OK for me as the github org name. So I have no problem leaving it as-is (which is the least work).