Gem.coop's namespaces are now in beta

Announcements
1

gem.coop maintainers announced beta for namespace support this week.

Have you ever come up with a really good gem name, only to discover that name has already been taken and you can’t push your gem? Ever been confused about if the gem aws-sdk-malware was really published by AWS?

Namespaces are the answer to these problems.

I already reserved my namespace, even though I’m not sure what I will do with it. Have you?

3 Likes
2

I didn’t realized publishing was an option there. Namespaces seems like a safe option for them to both be a rubygems.org mirror and allow publishing. But part of me is saddened that it has gone this way and there are now two public gem repositories that I may have to search instead of a single canonical one.

1 Like
3

I think publishing was not possible before this beta and even now you can only publish under the namespace (no “global” namespace publishing, this is still only synced from RubyGems).

4

I got my @jvrc-ca namespace too. I just need to create and publish a Gem now :slight_smile: … I think namespaces is a great addition to the gem server.

Although having a single canonical repository is “easier” or more practical in some scenarios, I think that having a de-centralized approach might be better for the ruby ecosystem in the long term. Bundler already supports the addition of private sources or install gems from git so it’s not a disruptive change from my point of view.