Rename Org from oauth-xx to ruby-oauth
9 views
Skip to first unread message
Peter Boling
Jun 27, 2025, 11:27:12β―AMJun 27
to Ruby OAuth
Original thread on my thoughts:
https://ruby.social/@galtzo/114755811319811334Post on dev.to:
Reprinted here:
Rename `oauth-xx` org Β to `ruby-oauth`?
Intent of current name was to be a home for oauth tools across many languages, but it never materialized that way. The vestigial -xx is awkward for many reasons, and I tihnk discoverability would improve with a ruby-* org name, and perhaps it could even bring in other oauth-related tools. I have a few thoughts about this, so π§΅
I'm very interested in others thoughts #Ruby #RubyFriends #OAuth #Authentication
π Break gemfiles that target the git repo directly
I can't think of any other downsides, and I don't think that this is simply a downside... as it has an (even bigger, IMO) upside.
Companies and projects need to fork a repo if they depend ths git version of it in automated build tooling, becuase then they control it. If you are not forking and depending on a repo you control you are walking on thin ice. No exceptions. β οΈ #SupplyChain
π Improved SEO
π Improved feels (x and xx have a negative connotations in society, not least of which is "death"), while Ruby is sprinkles and rainbows.
π Immediate comprehension of purpose from org-name alone
π Makes much more sense when fundraising, due to same clarity of purpose
IOW, the repo oauth-xx/oauth2 is not at all clearly related to ruby.
I believe the lack of ruby in the current org name is what influenced the name of the original project, oauth-ruby, to include ruby in the project name, thus creating a discrepancy between the project name on GitHub and the name of the gem, which is just oauth.
π Thus putting ruby into the org name will result in me feeling better about renaming the `oauth-ruby` project to simply `oauth`, mathcing the gem name.
Intent of current name was to be a home for oauth tools across many languages, but it never materialized that way. The vestigial -xx is awkward for many reasons, and I tihnk discoverability would improve with a ruby-* org name, and perhaps it could even bring in other oauth-related tools. I have a few thoughts about this, so π§΅
I'm very interested in others thoughts #Ruby #RubyFriends #OAuth #Authentication
π Break gemfiles that target the git repo directly
I can't think of any other downsides, and I don't think that this is simply a downside... as it has an (even bigger, IMO) upside.
Companies and projects need to fork a repo if they depend ths git version of it in automated build tooling, becuase then they control it. If you are not forking and depending on a repo you control you are walking on thin ice. No exceptions. β οΈ #SupplyChain
π Improved SEO
π Improved feels (x and xx have a negative connotations in society, not least of which is "death"), while Ruby is sprinkles and rainbows.
π Immediate comprehension of purpose from org-name alone
π Makes much more sense when fundraising, due to same clarity of purpose
IOW, the repo oauth-xx/oauth2 is not at all clearly related to ruby.
I believe the lack of ruby in the current org name is what influenced the name of the original project, oauth-ruby, to include ruby in the project name, thus creating a discrepancy between the project name on GitHub and the name of the gem, which is just oauth.
π Thus putting ruby into the org name will result in me feeling better about renaming the `oauth-ruby` project to simply `oauth`, mathcing the gem name.
Reply all
Reply to author
Forward
0 new messages