Discord Structure Changes

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
May 17, 2022
Meeting Notes
Type
Agreement
Last edited time
Jun 30, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
It has been decided that discord management / structure changes do not need to be official proposals.
Proposal
  • Tension:
    • The Discord has (again) lost a lot of its order and logic, ao because people have now too?) many permissions and can move a lot around.
    • With the creation of the GPC category + most of holdings moving into the DAO the ‘gitcoin core’ category has also become outdated
  • Proposal:
    • 1) To ratify the following order for the categories:
    • Townsquare*
    • DAO Community*
    • Public Goods
    • FDD
    • Moonshot Collective
    • DAO Ops
    • MMM
    • GPC
    • Hackathons & Events
    • DCompass
    • Govern Gitcoin
    • Support*
    • Gitcoin Local
    • Data
    • Archived
    •  
      *The categories Townsquare, DAO Community & Support: These are placed at respectively the beginning & the end because they have leveled access.
    • Townsquare & Support are accessible for everyone on Level 1
    • Why Townsquare at the start and not the end? Because it’s our townsquare (= our community), DAO Vibes also linked to this
    • DAO Community is accessible to various levels within the DAO, Applicants, DAO Contributors and Core Contributors
    • Rest is based on the order voted on by the core contributors during the Weekly WS call, where I mainly took into account the order of the workstreams.
    • Results of the vote for reference
       
      2) To delete the Gitcoin Core category and repurpose the role Gitcoin Core (rebranded to DAO Core) = anyone with a +20hr role
    • This role is manually assigned (for now), which can be done by anyone who has a ‘WS-lead’ role
    • What used to be “gitcoin core” is now moved mostly under GPC, access is given with the role ‘GPC contributors’ and/or GPC leads
    • Moving of remaining channels
      • Team general (rebranded to DAO Core) —> DAO Community
      • Holdings dao leadership (rebranded to CSDO Strategy) —> DAO Ops, access w/ role DAO Governance (=csdo)
      • Designer sync → MMM
      • Year in review → MMM
      • Hiring (rebranded to dao-people-ops) → DAO Ops, access with DAO Core role
      • Onboard to opolis —> archive (thread in people ops)
      • Treasury management → archive (duplicate with dao treasury diversification under daoops)
      • Gnosis-multisig → archive
       
      Note: planned evolution & order for DAO Ops (!) 👇
       
       
  • Clarifying Questions:
    • Sean - New folks who have joined recently haven’t been able to see some MMM channel, so they’ve been given the mmm-contributor role to gain access. Has there been any role changes w/ in the MMM workstream?
      • Kris - No, but Jonathan (CoachJ) has been in touch with Kris about all this
      • Sean - ok maybe this is an issue with people coming on not getting that role as part of onboarding - one example is azeez from PGF couldn't see content channel, gave him mmm contributor role but that's not ideal for our tracking
    • Chase - Do think we need to keep onboard to opolis? people are moving to the DAO still and will be important
      • Lindsey - that's one of the channels i want to follow-up on Chase
    • Tigress - if there were naming conventions for workstream-channels we could talk about them briefly here, otherwise, just do it
    • Joe - we found that we needed an FDD visitor role so we don't ping non-contributors who need to see FDD channels when we don't mean to
      • Kris - The gitcoin core role should fix this if they are core contributors
      • Kris - Sean: this actually also counts for what you mentioned
    • Kyle - Context setting for folks:
  • Reactions:
    • Kyle - Doesn’t need to be a proposal. If anyone disagrees, they should reach out to Kris specifically
    • Kris - OK, will start executing on this in the coming days
  • Amendments:
    • N/A
  • Objections?
    • N/A
  • Passed?
    • Yes / Not a proposal

Discord Structure Changes

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
May 17, 2022
Meeting Notes
Type
Agreement
Last edited time
Jun 30, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
It has been decided that discord management / structure changes do not need to be official proposals.
Proposal
  • Tension:
    • The Discord has (again) lost a lot of its order and logic, ao because people have now too?) many permissions and can move a lot around.
    • With the creation of the GPC category + most of holdings moving into the DAO the ‘gitcoin core’ category has also become outdated
  • Proposal:
    • 1) To ratify the following order for the categories:
    • Townsquare*
    • DAO Community*
    • Public Goods
    • FDD
    • Moonshot Collective
    • DAO Ops
    • MMM
    • GPC
    • Hackathons & Events
    • DCompass
    • Govern Gitcoin
    • Support*
    • Gitcoin Local
    • Data
    • Archived
    •  
      *The categories Townsquare, DAO Community & Support: These are placed at respectively the beginning & the end because they have leveled access.
    • Townsquare & Support are accessible for everyone on Level 1
    • Why Townsquare at the start and not the end? Because it’s our townsquare (= our community), DAO Vibes also linked to this
    • DAO Community is accessible to various levels within the DAO, Applicants, DAO Contributors and Core Contributors
    • Rest is based on the order voted on by the core contributors during the Weekly WS call, where I mainly took into account the order of the workstreams.
    • Results of the vote for reference
       
      2) To delete the Gitcoin Core category and repurpose the role Gitcoin Core (rebranded to DAO Core) = anyone with a +20hr role
    • This role is manually assigned (for now), which can be done by anyone who has a ‘WS-lead’ role
    • What used to be “gitcoin core” is now moved mostly under GPC, access is given with the role ‘GPC contributors’ and/or GPC leads
    • Moving of remaining channels
      • Team general (rebranded to DAO Core) —> DAO Community
      • Holdings dao leadership (rebranded to CSDO Strategy) —> DAO Ops, access w/ role DAO Governance (=csdo)
      • Designer sync → MMM
      • Year in review → MMM
      • Hiring (rebranded to dao-people-ops) → DAO Ops, access with DAO Core role
      • Onboard to opolis —> archive (thread in people ops)
      • Treasury management → archive (duplicate with dao treasury diversification under daoops)
      • Gnosis-multisig → archive
       
      Note: planned evolution & order for DAO Ops (!) 👇
       
       
  • Clarifying Questions:
    • Sean - New folks who have joined recently haven’t been able to see some MMM channel, so they’ve been given the mmm-contributor role to gain access. Has there been any role changes w/ in the MMM workstream?
      • Kris - No, but Jonathan (CoachJ) has been in touch with Kris about all this
      • Sean - ok maybe this is an issue with people coming on not getting that role as part of onboarding - one example is azeez from PGF couldn't see content channel, gave him mmm contributor role but that's not ideal for our tracking
    • Chase - Do think we need to keep onboard to opolis? people are moving to the DAO still and will be important
      • Lindsey - that's one of the channels i want to follow-up on Chase
    • Tigress - if there were naming conventions for workstream-channels we could talk about them briefly here, otherwise, just do it
    • Joe - we found that we needed an FDD visitor role so we don't ping non-contributors who need to see FDD channels when we don't mean to
      • Kris - The gitcoin core role should fix this if they are core contributors
      • Kris - Sean: this actually also counts for what you mentioned
    • Kyle - Context setting for folks:
  • Reactions:
    • Kyle - Doesn’t need to be a proposal. If anyone disagrees, they should reach out to Kris specifically
    • Kris - OK, will start executing on this in the coming days
  • Amendments:
    • N/A
  • Objections?
    • N/A
  • Passed?
    • Yes / Not a proposal