Started a discussion in open-sauced/open-sauced around every techies' favorite topic, naming things! A dire conquest to stay as neutral as possible, while still keeping a small semblance of relevance and utility in remembering, not what it's doing, but what you wanted to do over there!

The key takeaways or TL;DR:

1. Some repositories are in dire need of some more sensible naming, the more platforms a repo can be available on, the simpler the naming should be:
- @open-sauced/release <- @open-sauced/semantic-release-conventional-config
- @open-sauced/commit <- @open-sauced/conventional-commit
- @open-sauced/check-engines

2. Some of the very old and very new repositories could have their brand or code name repurposed as deployment environments while keeping a very small relevance suffix, descriptive of the application type, like:
- -action
- -integration
- -api
- -bot

What do you think they should be called? Join the @open-sauced discussions on GitHub and help decide (spoiler alert), what the hot sauce ingredients should really be called! 🍕🍕🍕