Package naming convention

[RafaelVidaurre]

I feel like we need a better naming convention for our packages. What do you think about this as a first approach?

We prefix our packages with the app type and name The two kind of app types we currently make are web apps and bots:

Prefixes:

• app: a webapp, mobile app, etc
• bot: a bot

Examples:

• bot-referral-ranks
• bot-meme-cannon
• app-overmind-site

We also have shared packages that do not belong to any app:

Prefixes:

• shared: private shared code
• public: an open source package

Examples:

• shared-discord-js-command-manager
• shared-utils

We also have packages that are specific to an app, so we prefix their name with the app's name. Examples:

• bot-referral-ranks-landing
• bot-referral-ranks-score-calculator
• bot-referral-ranks-invites-wrapper

Note: we can probably also configure our repo to have app folders with all the related packages inside to have less visual noise

[monitz87]

The idea seems good, but what happens when we have a web app that is related to a bot? For example, the invite wrapper endpoint I’m currently working on. Would it be named bot-referral-ranks-app-invite-wrapper? Kind of verbose