Role Proposal
Role Tables • Hierarchy • Core Roles • Bonus Roles • Implementation
This proposal is aimed at improving the over all quality of life on the Discord server and the Red organization by providing clarity, direction, and understanding to the user base. There are major changes in this proposal that may be viewed as aggressive. However, the purpose of this document is not to minimize any specific individual or groups on the server. It is only meant to act as a set of guidelines to better serve the community.
Roles are tools not jewels and should be treated as such. If someone is no longer able to continue the duties and responsibilities of that role, then they should be put into an inactive status. The project is too large for users to be occupying critical roles they do not use. Users who lose their roles but wish to come back can be reinstated if needed. This gives not only our user base a better understanding of the who and what, but gives those in charge a better understanding of where critical manning shortfalls exist.
Direction should flow down, and issues should propagate up via the appropriate channels. A detailed section of what each role is responsible for should be posted on the docs.
| Role | Responsibilities | Color |
|---|---|---|
| Core Developer | Responsible for the creation and maintenance of the project source. | #30acec |
| Moderator | Bans, kicks, chat moderation, server tasks. | #d41d2f |
| QA | Tests assigned PRs, review cog creator applicants. | #1bd49f |
| Community Manager | Liaison between core developers and user base. | #14f008 |
| Cog Creator | Approved third-party developer group. | #81049e |
| Support Staff | Dedicated to helping with support questions. | #aada0b |
| Patreon | Patreon subscribers | #f5e97c |
| Role | Description | Color |
|---|---|---|
| Contributor | Has made a number of approved pull requests. | #aa7aa0 |
| Translator | Approved translator for Red Core. | #ee87e5 |
| Data Ops | Analytics and data engineering. | None |
| Linux | Access to Linux support channel. | None |
| Mac | Access to Mac support channel. | None |
| Junior Cog Creator | Entry level cog creator. | None |
| Subscriber | Subscribes to news, events, and exclusives. | None |
| Retired | Given to users who are unable to fulfill their prior duties. | #ff8f00 |
A core developer's primary focus should be the development of Red. While administrative and moderator type duties can be granted to some developers, the burden of these tasks should fall upon the server moderators. Core developers should not 'sit' in this role without continual contributions to the project. The further someone is away from the source, the more difficult it is to make meaningful decisions.
In addition, core developers should assign QA members to test their PRs. While a PR may be tested by anyone, this provides some dedicated support and feedback between the developer and someone who understands the architecture.
Moderators are set below core developers, but are tasked with maintaining civility in the server. Kicks, bans, punishments, warnings, and other moderation tasks should be dealt with by moderators. Users should feel like mods are approachable, friendly, and always watching. A user in this role may also be in charge of some administrative project details, like policing issues/prs from maliciousness.
QA (Quality Assurance) sits below Moderators and Core Developers. They are charged with the task of testing PRs for Core Developers and reviewing applicants to the Cog Creators program. QA can be assigned by Core Devs to test specific tasks and report their findings.
Community managers are responsible for promoting the project and foster good will with the user base. CMs should act as a liaison between the core developers and the user base. Interviews, news, delays, promotions, community announcements, and spotlights make up the bulk of their responsibilities.
Cog creators are verified third party developers for Red bot. They have been selected by the QA team to be exceptional content creators. Cog Creators should have an open line of communication with the core developers so that they are able to continue delivering content to the community. CC's should also be helping to mentor junior developers through collaborations, pair programming, or advisement.
Support staff should be who new users look to for help. There is a lot of good information that gets muffled by too many people trying to answer the same question. With a designated role, users can make a better decision, get better feedback, and overall have a better experience.
While every member of the Red Bot community is important, our Patreon subscribers go above and beyond to support the project. We should be giving more to the folks who keep the machine turning. Patreon's could get early access features, behind the scenes sneak-peaks, and more. The patreon subscriber page should also have a list of funding goals for certain parts of the project. Patreons should have some idea where the money they contribute is going. While not within the scope of this proposal, proto-typing merchandise, upgrading services, and paying for a legit Red mascot would be some good money sinks.
Some roles can be granted to designated some additional responsibilities, merit, or ability. Only contributor, translator, and retired will change the color of the user (unless they are already basic AF, then slight grey) and should be given out as appropriate.
Contributors are those who have made meaningful contributions to the Red Bot project.
Translators are those who have made significant contributions in translating Red. In addition, a flag of their language could be added as a "role" as well.
Additional role given to an administrator or higher as a designation. Responsible for data and analytics.
A ping-able role for Linux related issues.
A ping-able role for Mac related issues.
Entry level cog creator who has demonstrated that they can contribute meaningfully to the development of third-party cog system, but are still learning.
A 'sign-up' role to subscribe to news, spotlights, and announcements.
A role for those who have made significant contributions to the project and have once held a core role. They have been given this role due to their inactive status, and their previous role can be reinstated if their activity improves.
Phase I
-
Notify all users with significant roles that they will be revoked within 30 days, as per the guidelines in this proposal if they are inactive. In addition, many roles will undergo changes, but many responsibilities will remain in place.
-
Create all roles that have not yet been created for the change over.
-
Select members who will be placed in specific roles and those who will be retired.
Phase II
-
Retire those who have are inactive
-
Add members to the respective roles