Discord Roles Migration

[Arlodotexe]

What we have

Our old backend purposely avoided syncing with Discord on some select things.

The project management system was designed to enable members to add/remove other members from their project autonomously.

This system used a hardcoded set of project roles that could be applied, and only loosely couples these project roles to their corresponding Discord role names.

While this allowed us to create new Discord roles without touching the backend or database, this meant we were requiring Discord roles to have strict names that can be captured by this loose coupling.

What we need

We need something better. Aspects of this that are unacceptable include:

• Lack of flexibility in role types that can be applied
• Hardcoded Discord role names (one per role type)
• Lack of automated tracking/cleanup of project-specific roles created in our Discord server.

SDK Roles

The roles in the SDK are not defined by the SDK beyond their ID, Name and Description.

When performing database migration, we'll be able to port the existing roles that are in-use, including:

• Owner
• Developer
• Beta tester
• Translator
• Advocate
• Lead
• Support
• Patreon

If any roles from the old codebase aren't being used by a project, they'll naturally be dropped as part of the migration process since role data now lives on the projects/users/publishers themselves.