Clarify distinction between gem.coop (the service) and Gem Cooperative (the group) and gem-coop (GitHub organization)

[duckinator]

We were frequently using gem.coop to refer to service, the GitHub organization, and the cooperative itself.

In an attempt to avoid confusion, I did my best to clarify the distinction between:

• gem.coop (the service/website)
• Gem Cooperative (the group)
• gem-coop (the GitHub organization)

[deivid-rodriguez]

Nice!

[martinemde]

Much less confusing, thank you!

[wwahammy]

As an external supporter, would you all be open to having more different names for the various entities? I think of what happened with RubyGems and part of the issue is that the names are confusing for people.

Either way, I'm all on board with what you folks are doing and I'm excited to help in any way I can. 😄

[simi]

As an external supporter, would you all be open to having more different names for the various entities? I think of what happened with RubyGems and part of the issue is that the names are confusing for people.

Either way, I'm all on board with what you folks are doing and I'm excited to help in any way I can. 😄

Thanks for the feedback, it is really valid point. I'm constantly explaining the difference in between RubyGems, RubyGems.org (code) and RubyGems.org (running service).

[indirect]

I think it's a big concern when the parts with the same name are separate, but I feel like it is probably ok when the parts are not separate? Like, the Gem Cooperative is the owner of the GitHub org gem-coop, and is the creator and owner and operator and maintainer of the gem.coop service. But maybe we should use another domain name for the service to make it clear it's not the same as the coop?