Hey Everyone,
We're considering renaming the Service APIs project to Gateway API and would love some feedback from the broader sig-network community. The Service APIs name came from before we had really decided on any resource names for the API and was meant to reflect a goal of the project to extend and build on top of Services. Now that we seem to have settled on names for our key resources, with Gateway as the most prominent one, a transition to the "Gateway API" name could make sense.
We're hoping this updated name could make the project both more discoverable and marketable. Initial users of this API have often naturally referred to it as the "Gateway API" already, and the current "Service APIs" name does not seem to have a clear connection to any of our resources.
We completely recognize that any name change should not be done lightly, so we want to make sure we have as much feedback as possible before making any decision here. I've added this to the agenda for the sig-network meeting on Feb 4 so we can discuss this further there. In the meantime, I'd appreciate any suggestions or feedback either in response to this thread or on the
corresponding issue.
Thanks!
Rob