Discord/RfC 2

This RfC is built using information from User:Void/Discord (permanent link). Any user can add their own proposal, or propose additional amendments to an existing proposal. This RfC opened on 22:31, 21 February 2021 (UTC) and will remain open for at least a week, or at least a week from the date of the last added proposal/amendment. The latest proposal/amendment was added on 22:31, 21 February 2021 (UTC).

Proposal 1

 * All private spaces (particularly those requiring an NDA to access, or otherwise considered confidential) except those required for server moderation, and non-confidential conversation between special groups will be removed from the server. Any confidential discussion spaces should be created by these groups. Current confidential spaces will be deleted following the implementation of this RfC. If you have access to a confidential space on the Discord server, please copy out all information you will need. You will be given a minimum of 24 hours notice prior to the deletion of the channel.
 * Discord moderation abilities will not be delegated based on on-wiki permissions, but will require specific elections. Roles will still exist for on-wiki groups and other delegations, but themselves will not have any special permissions. Instead they will be purely cosmetic and for organizational purposes. Some roles may provide access to private, but not confidential chat venues. Any role requiring a confidential discussion space should instead create one for themselves.

Definitions

 * flavor group : A role on discord that provides a unique color, and possible sorting on the user list. It is used to differentiate between members of groups, but does not provide any moderation access. There may be private channels tied to a flavor group, but they are not confidential, and platform moderators will still have access.
 * private channel : A private channel contains information that is not public, but has no confidentiality requirement. Information from these channels should still not be disclosed without a valid reason.
 * confidential channel : A private channel that contains information that cannot be made public, and additionally requires that only specifically vetted persons have access or can access at all.

Roles

 * 1) Administrator - Discord administrator, has all permissions.
 * 2) Moderator - Discord moderator, has access only to required moderation tools.
 * 3) Board Member - "Flavor group" - provides no additional permissions.
 * 4) Stewards - "Flavor group"
 * 5) Site Reliability Engineers - "Flavor Group"
 * 6) System Administrators - "Flavor Group"
 * 7) CVT - "Flavor Group"
 * 8) Code of Conduct Commissioner - "Flavor Group"
 * 9) Interwiki Administrator - "Flavor Group"
 * 10) Former System Administrator - "Flavor Group"
 * 11) CSS/JS Support Volunteer - "Flavor Group"
 * 12) Nitro Booster - "Flavor Group"
 * 13) Bots - "Flavor"/organizational role
 * 14) Verified Wiki Users - "Flavor Group"
 * 15) *Assorted bot roles*
 * 16) Muted - Prevented from chatting
 * 17) @everyone

Moderator permissions
View Channels, Manage Channels, Manage Roles, View Audit Log, View Server Insights, Create Invite, Change Nickname, Manage Nicknames, Kick Members, Ban Members, Send Messages, Embed Links, Attach Files, Add Reactions, Use External Emoji, Mention all roles, Manage Messages, Read Message History, Send TTS, Connect, Speak, Video, Voice Activity, Priority Speaker, Mute Members, Deafen Members, Move Members.

Moderator membership
All current members of discord that have access to moderation powers as a result of their current role will be able to gain access to the proposed Moderator role. However, they will need to pass a confirmation vote with the same level of requirement as being appointed (see below).
 * n.b. Confirmation is an opt-in process. Current moderators who do not put forward a confirmation vote within a week of the closure of this RfC will be removed (unless superseded by ).

Appointment
Users may be nominated or nominate themselves by placing a request on the Community noticeboard. Whenever the nomination is accepted (if nominated by someone else, otherwise submitting the request is immediate acceptation), a request must stay open for at least seven (7) days. During this period anyone from the Community may comment on a candidate's request. This request will be listed in a dedicated channel on Discord for awareness.

A request will be deemed successful when closed by a Discord Administrator after having achieved a 70% support ratio.

Revocation
A moderator may lose their permissions if:


 * a request of no confidence in opened against the user and has a more than 50% support ratio, or
 * the user is inactive from the community for a period of 6 months.

Administrator membership
The initial Discord Administrators will consist of Void, SPF, and NDKilla. Any other Administrator must be appointed following the criteria below.

Appointment
Users may be nominated or nominate themselves by placing a request on the Community noticeboard. Whenever the nomination is accepted (if nominated by someone else, otherwise submitting the request is immediate acceptation), a request must stay open for at least seven (7) days. During this period anyone from the Community may comment on a candidate's request. This request will be listed in a dedicated channel on Discord for awareness.

A request will be deemed successful when closed by the server owner after having achieved a 70% support ratio.

Revocation
An administrator may lose their permissions if:


 * a request of no confidence in opened against the user and has a more than 50% support ratio, or
 * the user is inactive from the community for a period of 6 months.

Server Owner
The server owner may be selected at any time by the current owner from any of the current Discord Administrators. The community may retroactively overturn this, or elect a new server owner at any time, through a vote requiring the same appointment criteria as the Administrator position. A user must be an Administrator in order to become the server owner. If their Administrator role is revoked for any reason, then they must delegate server owner to one of the current Administrators.

The current server owner is SPF.

Support

 * 1) As proposer. We need a different system for Discord moderation, and I think this is how we get that started. --  Void  Whispers 22:31, 21 February 2021 (UTC)
 * 2) Strongly support per rationale and per the rationale I articulated on Discord, in  on IRC, and elsewhere. Dmehus (talk) 22:33, 21 February 2021 (UTC)

Oppose

 * 1) See . Give 'em a year. Firestar464 (talk) 07:16, 22 February 2021 (UTC)
 * Umm... do you even know why this proposal was created in the first place? 09:16, 22 February 2021 (UTC)

Amendments to Proposal 1
These amendments are independent of the proposal, but if they pass, they will alter the scope of the original proposal. Feel free to add any additional amendments, but be sure to point to what part of the proposal they alter.

Amendment #1
A user is only eligible to vote upon new Discord Moderators/Administrators if they have a verified Discord account. (Alters and )

Support

 * Strongly support per the nomination. Dmehus (talk) 22:35, 21 February 2021 (UTC)
 * Firestar464 (talk) 06:43, 22 February 2021 (UTC)

Comments
Makes sense, but we don't necessarily have a good way to verify wiki accounts to Discord accounts, but the reverse exists. (Correct me if I'm wrong). -- Void  Whispers 22:31, 21 February 2021 (UTC)
 * Void We have WikiAuthBot which verifies the wiki account to the Discord account. That satisfies me in terms of verifying whether the user is an active user of the Discord server. Dmehus (talk) 22:35, 21 February 2021 (UTC)
 * Ah, I had suspected it was possible, but had never used it in that context before. -- Void  Whispers 22:38, 21 February 2021 (UTC)

Amendment #2
Voting shall take place on Discord through a dedicated channel. (Alters and )

Support

 * Strongly support, as we want to ensure that those active on the Discord server are the ones voting for platform moderators. In keeping with local consensus-based decision-making on local wikis or other platforms, each official chat platform should elect their own platform moderators. Any users, can, of course, join the respective chat platform(s) and participate in the voting, but it wouldn't make a lot of sense to use another venue with no way of verifying whether the user is active in the Discord server. Dmehus (talk) 22:40, 21 February 2021 (UTC)

Comments
Not quite sure how this would be setup, if anyone has any ideas, let me know. This will need to be sorted prior to implementation. -- Void  Whispers 22:31, 21 February 2021 (UTC)
 * Void Discord offers voting icons, which could be reacted to. So, my understanding is we'd just setup a channel on the Discord server, state the nomination, have users react by voting, and then reply with their comments. Dmehus (talk) 22:40, 21 February 2021 (UTC)

Amendment #3
For the purposes of revocation, the inactivity period is reduced to 3 months instead of 6. (Alters and )

Support

 * Strongly support. Makes sense to me. Elected platform moderators should be active on the server they've been elected to moderate. Dmehus (talk) 22:42, 21 February 2021 (UTC)

Amendment #4
All current members of discord that have access to moderation powers as a result of their current role will be able to gain access to the proposed Moderator role through an opt in process. This process closes a week after the closure of this RfC, and any further moderators must be appointed. No confirmation vote will be required. (Alters )

Support

 * 1)  I most definitely support this proposal. DarkMatterMan4500 (talk) (contribs) 22:50, 21 February 2021 (UTC)
 * 2) Support. For greater clarity, the current lineup of existing platform moderators, notwithstanding myself who will resign as a platform moderator upon this RfC's closing, includes Void, NDKilla, Reception123, Southparkfan, Paladox, and MrJaroslavik. I'm happy with that lineup, and additional platform moderators can always be elected as needed. Dmehus (talk) 22:54, 21 February 2021 (UTC)

Comments
Procedural Comment: Amendment #4 was proposed prior to making my decision to resign from platform moderation responsibilities. So, for greater clarity, Amendment #4 should be read as, "All current members of discord, notwithstanding Dmehus, who has subsequently announced his intention to resign as a Discord platform moderator upon this RfC's closing, that have access to moderation powers as a result of their current role will be able to gain access to the proposed Moderator role. No confirmation vote will be required." Dmehus (talk) 22:44, 21 February 2021 (UTC)
 * To clarify the current language does not require that the current moderation-capable users migrate to the new group, but instead can opt in, or opt out. (This should perhaps be clarified better). -- Void  Whispers 22:54, 21 February 2021 (UTC)
 * Agreed that this should absolutely be clarified better. If it's opt-in, what's the timeframe for them opting in? If it's opt-out, that's fine, as they can always opt-out. For reasons of logistical simplicity, I think we should use an opt-out approach, with a timeline to advise a current platform administrator of whether they will be continuing after this RfC closes. Dmehus (talk) 22:57, 21 February 2021 (UTC)
 * This proposal has been clarified regarding the above. -- Void  Whispers 22:59, 21 February 2021 (UTC)

Amendment #5
The proposed Discord Administrators list will require a confirmation vote following the RFC. (Alters )

Support

 * 1) Strongly support. This makes sense as well. Discord server administrators have access to an additional toolkit, and we're proposing to revamp the current Discord administrators, so it makes sense that this initial crop of server administrators should require a reconfirmation vote on the platform following this RfC's closing. Dmehus (talk) 22:51, 21 February 2021 (UTC)

Amendment #6
For the purposes of the Revocation clause, community is defined as the Discord server. (Alters and )

Support

 * 1) Makes sense as a way to further separate the Discord server from the rest of the community, and so as to not have there be any confusion. --  Void  Whispers 22:31, 21 February 2021 (UTC)
 * 2) Strongly support per above, and because this is in keeping with local consensus-based decision-making. Local wiki communities, or other platforms, elect their teams, and established policies. As such, it's only fitting that members of the Discord server should elect their platform moderators and administrators. Dmehus (talk) 22:48, 21 February 2021 (UTC)