[Doc] Acknowledge Shopify in the initial release

[koic]

Motivation and Context

The repository's "About" section currently states, "The official Ruby SDK for the Model Context Protocol. Maintained in collaboration with Shopify." However, now that MCP governance has been established, maintenance is handled by the MCP steering group.

Given this, it seems more accurate to remove the maintenance wording from the "About" section. That said, I think it would be good to preserve acknowledgment of Shopify, which originally developed and released the Ruby SDK.

There may be a more appropriate place for this, but at the very least, it could be recorded in the changelog as part of the project's history.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[koic]

Additionally, this may be a good time to update the ownership on RubyGems.
https://rubygems.org/gems/mcp

At the moment, among the Ruby SDK development team, the gem is owned only by @topherbullock. It may be worth considering adding @atesgoral, @jonathanhefner, and me (@koic) as owners as well.

This would help ensure that issues can be addressed promptly if they arise. From a governance perspective, it would likely be best to keep modelcontextprotocol as the only organization account and grant access to individuals as needed.

@topherbullock, would it be possible to move forward with this? If preferred, this can also be handled on my side.
Could my account (It uses the email on https://rubygems.org/profiles/koic_ito), be added as an owner of the mcp gem?

[koic]

@topherbullock When you have a chance, it would be appreciated if you could take a look at the comment above regarding gem release permissions.