🗃️
Contributor Access Bundle DBs
/
Limit moderator roles to taskforce only

Limit moderator roles to taskforce only

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Dec 7, 2021
Meeting Notes
Type
Community XP
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and moderator rights were limited to the taskforce (currently Kris, Alp, Dexter & Derek, with Kyle, Kevin, Kris, Scott, & Derek as Admins)
Proposal
Proposal 1: moderator rights
  • Tension: Right now we have 17 moderators.
    • This weekend we had our first bot social engineering its way in and @ everyone many channels. High security risk.
    • Not practical when many automations & uniformity being implemented (roles, channel naming & logic...)
  • Proposal: Limit moderator roles to taskforce only (atm Kris, Alp, Dexter & Derek - also Kyle, Kevin, Kris, Scott, Derek are Admins). Tackle the two main needs (creating channels & assigning roles) by giving these powers to the 'WS'-Ops role.
    • Would execute on this as soon as
      • ops roles powers have been reviewed/adjusted
      • moderators have all been notified
    • Next:
      • training community managers
      • hire part-time to fix possible issues, set up future automations
  • Clarifying Questions
    • Moderator on call? this is in the making
    • Power to add to channels? yes, this is role based
  • Reactions
    • Kyle: Highly in favor of locking down moderator access. Cleaned up, also other people who had mod access. We can take 24h to add a bot.
    • Annika: in support, before we yolo'd this
    • Sean: in support, we can do all the things we need to do
    • Kevin: Proposal
    • Joe: support
    • Philip: In support of this
  • Amend & Clarify:
    • You can create channels with the 'WS-Ops' channels but please don't abuse this power :)
  • Objections
    • no
  • Proposal passed?
    • Yes
🗃️
Contributor Access Bundle DBs
/
Limit moderator roles to taskforce only

Limit moderator roles to taskforce only

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Dec 7, 2021
Meeting Notes
Type
Community XP
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and moderator rights were limited to the taskforce (currently Kris, Alp, Dexter & Derek, with Kyle, Kevin, Kris, Scott, & Derek as Admins)
Proposal
Proposal 1: moderator rights
  • Tension: Right now we have 17 moderators.
    • This weekend we had our first bot social engineering its way in and @ everyone many channels. High security risk.
    • Not practical when many automations & uniformity being implemented (roles, channel naming & logic...)
  • Proposal: Limit moderator roles to taskforce only (atm Kris, Alp, Dexter & Derek - also Kyle, Kevin, Kris, Scott, Derek are Admins). Tackle the two main needs (creating channels & assigning roles) by giving these powers to the 'WS'-Ops role.
    • Would execute on this as soon as
      • ops roles powers have been reviewed/adjusted
      • moderators have all been notified
    • Next:
      • training community managers
      • hire part-time to fix possible issues, set up future automations
  • Clarifying Questions
    • Moderator on call? this is in the making
    • Power to add to channels? yes, this is role based
  • Reactions
    • Kyle: Highly in favor of locking down moderator access. Cleaned up, also other people who had mod access. We can take 24h to add a bot.
    • Annika: in support, before we yolo'd this
    • Sean: in support, we can do all the things we need to do
    • Kevin: Proposal
    • Joe: support
    • Philip: In support of this
  • Amend & Clarify:
    • You can create channels with the 'WS-Ops' channels but please don't abuse this power :)
  • Objections
    • no
  • Proposal passed?
    • Yes