Discord roles status and changes

[bwhm]

Summary

There are currently 36 roles (not to be confused with on-chain roles) on the joystream discord. To somewhat improve the ease of reading, they are grouped in to one of:

• Honorary Roles, which in addition to some extra permissions gives the discord members in these group(s) some 'clout'.
• On-chain Roles, which are intended to verify the discord member as belonging to a specific on-chain role. This should make it easier to notify and tag them for questions, alerts, tech support etc. Much like the Honorary Roles, they also provide some extra permissions and clout. These should be in sync with the chain, courtesy of the joybot, but given it's limitations and issues are not.
• Bots, which are roles associated with a single discord bot, with tailored permissions.
• Others. The remaining discord roles. Whereas some of these could have been placed in one of the other groups (no longer serving that purpose), some were made for a easing communication (now defunct).

The order the roles are listed in is relevant, as permissions granted for a role also applies to all roles that are ordered below.

Role	Group	Order	Members	Current Status	Future
jsgenesis	Honorary Roles	1	13	Used	Keep
founding member	Honorary Roles	2	82	Used, but not synced	Update
Server Booster	Others	3	3	Not clear	Keep?
MEE6	Bots	4	1	Not clear	Not clear
bot	Others	5	2	Not used	Kill
participant	Honorary Roles	6	1860	Used	Keep
bounty-participant	Others	7	1	Not used	Kill
joystreamTestBot	Bots	8	1	Not used	Kill
joystream-media-bot	Bots	9	1	Not used	Kill
joystream-bot	Bots	10	1	Not used	Kill
Captcha.bot	Bots	11	1	Used	Keep
Role Role	Others	12	1	Not clear	Kill, but replace with similar
kpi-pin	Others	13	1	Not used	Kill
Statbot	Bots	14	1	Used	Keep
Council Member	On-chain Roles	15	5	Used, but not synced	Keep. Manual pending "Joybot" improvements
Content Lead	On-chain Roles	16	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Content Worker	On-chain Roles	17	7	Used, but not synced	Keep. Manual pending "Joybot" improvements
Storage Lead	On-chain Roles	18	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Storage Worker	On-chain Roles	19	10	Used, but not synced	Keep. Manual pending "Joybot" improvements
Distribution Lead	On-chain Roles	20	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Distribution Worker	On-chain Roles	21	8	Used, but not synced	Keep. Manual pending "Joybot" improvements
Builder Lead	On-chain Roles	22	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Builder Worker	On-chain Roles	23	6	Used, but not synced	Keep. Manual pending "Joybot" improvements
HR Lead	On-chain Roles	24	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
HR Worker	On-chain Roles	25	2	Used, but not synced	Keep. Manual pending "Joybot" improvements
Marketing Lead	On-chain Roles	26	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Marketing Worker	On-chain Roles	27	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
Forum Worker	On-chain Roles	28	1	Used, but not synced	Keep. Manual pending "Joybot" improvements
Forum Lead	On-chain Roles	29	0	Used, but not synced	Keep. Manual pending "Joybot" improvements
WidgetBot Emerald	Bots	30	1	Not clear	Not clear
atlas-tester	Others	31	18	Not used	Kill
on-chain identity verified	Honorary Roles	32	100	Used, but issues	Kill. Pending "Joybot" improvements
Joybot	Bots	33	1	Used, but issues	Kill. Decommission bot.
new role	Others	34	0	Not used	Kill
Atlas Dev	Honorary Roles	35	3	Not used	Kill
crew3	Bots	36	1	Not clear	Not clear

The main actions suggested for each group are outlined below.

Honorary Roles Keep:

• jsgenesis and participant.
• founding member. Needs to be synced manually (a one time thing), no point in adding bots.

Remove:

• Atlas Dev.
• joystream-media-bot and joystream-bot. None are active/working, and not clear who ran them.

Changes required (remove for now):

• on-chain identity verified. Quite a few issues that should be addressed. Both regarding functionality, and the ownership, maintaince and control of joystream specific bots.

On-chain Roles (all of them) The concept of "On-chain Roles" are really useful, but the Joybot managing (same as the on-chain identity verified) needs a few technical improvements if it is to be automatic and reliable, in addidtion to the lack of oversight (from both JSG and the community) currently. I suggest we remove the bot, and do it manually for now. Once the questions of oversight and control, in addition to the technical issues, are addressed, a/the bot is re-introduced.

Bots Keep:

• Captcha.bot. Needed and working.
• Statbot, crew3. Not done much research, but the former is used a bit, and the latter was recently added.

Remove:

• joystreamTestBot, joystream-media-bot and joystream-bot. None are active/working, and not clear who ran them.

Unclear:

• Joybot. Is a nice concept, but the issues above needs to be fixed. I suggest removing in the meantime.
• MEE6, WidgetBot Emerald. Not sure what these do, so I'm hesitant to remove before asking.

Others: Keep:

• Server Booster. Discord operated.

Remove:

• bot. Gathering of all bots in one role, not needed.
• new role. Test?
• atlas-tester, bounty-participant and kpi-pin. Made for some specific purpose, that it's no longer serving.

Unclear:

• Role Role. Used to create and manage the on-chain roles. Will be removed, but likely replaced by something similar, under council oversight.

---

Only putting the summary here. More information and background can be found in this gist.

[bedeho]

Why keep participant what is that? otherwise looks good.

so I'm hesitant to remove before asking.

nonono, kill it, then ask questions, if you ask for permission, we will never get done. Same with Statbot. I don't see why we need all these bots.

PS: Can I ask that we rename all roles which are plural? this makes it more natural to use these handles in conversation, I always got a bit tripped up about that. saying @council members is way more natural for what we are trying to use this role for.

PSS: What, if any, of these bots is actually managing membership of people in these roles? for on-chain stuff this is critical.

[chrlschwb]

As far as I know, the discord bots only pull query results from the QN. And they need manual signing from the user to verify that the discord user is, in fact, the owner of the joystream identity. The bots do not manage anything. They only automate giving discord roles and pasting on-chain events on discord channels.