🗃️
Contributor Access Bundle DBs
/
Consolidate Moonshot Collective & Builderband

Consolidate Moonshot Collective & Builderband

Proposed By
Essential Intent
DAO Organization
Outcome
PASSED
Proposal Date
May 24, 2022
Meeting Notes
Type
Community XP
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and the Moonshot Collective & Builderband communities will merge into one community. This will be announced in the forum, and the builderband channels in the discord will be archived. Builderband builders will be given the opportunity to opt into the merge.
Proposal
  • Tensions: There are currently three builder communities within GitcoinDAO, all having many overlapping tasks, efforts and missions.
  • Proposal: We plan to consolidate two of them (moonshot and builderband) while aiding in increased participation in third (events and hackathons) Here
    • Post the above doc to the gov forum, announcing the merge of moonshot with builder band and make the proposed changes to discord.
      • Archive builderband, builder-general and builder ops channels
      • Allow the opportunity for builder band + builders to opt in to a new permission
  • Clarifying Questions:
    • Loie - Does it change the theme of what type of builder group it is? I know MC was the prototyping hub, I wonder if this remains, merges with builderband, or changes in general? Is it still prototype focused?
      • Emu - Same thing, they are merging because their intents became similar. MC contributors were looking for full-time jobs but had none to offer, same issue appeared in builderband. Didn’t want to string people along
    • Kris - Will you just migrate everyone in builderband to MC or give them the opportunity to join?
      • Emu - I think the latter, I’m trying to be strategic about thinking & knowing about these people. Don’t want to force any changes
    • Sean - Don’t feel like the document outlined what the community was trying to do. Would be great to more tangibly quantify how the community exists (emails, discord). Want to quantify relative sizes of these circles to determine the relative purpose.
      • Emu - Builderband is only about 100 people, large overlap between what they want to do at builderband and what they want to do at MC. This is what spurred the ideation of merging. Want to bring together the community to promote engagement
  • Reactions:
    • Thumbs Up
      • Jodi - On the surface, no objections. I think it would be helpful to think through exactly how / solicit feedback from the community (forum post). Supportive of MC testing this out
      • Loie - Supportive, reduces double work + love partnerships. Brings up a curiosity around the efforts we’ve put into education. I have always been an advocate that web3 orgs should be educational hubs but in bear market times we gotta look at essential intent & making sure we prioritize Grants 2.0 and token utility with our energy/resource expenditure
      • Sean - Support. On the fence on whether it should be a proposal or not, but definitely not opposed. Aligning resources + focusing in
      • Annika - Supportive, these two communities were stood up with very different purposes and have scaled over time. I would suggest adding the context to the gov post. Other reaction is budget stuff, I assume that’s been thought through but calling out the implications here
      • Tigress - Supportive, like the idea of organizing teams. It’s important to align priorities and to really make the move optional for the contributors
      • Simona - Supportive, it’s important to make it an optional thing and also have that conversation with builderband to see what the alignment/overlap is. Want to get a sense of their sentiment, don’t want this to seem like a takeover.
    • Thumbs Down
  • Amendments:
    • Emu - No amendments, just refining the government post for additional context / clarification
  • Objections?
    • None
  • Passed
    • Yes
🗃️
Contributor Access Bundle DBs
/
Consolidate Moonshot Collective & Builderband

Consolidate Moonshot Collective & Builderband

Proposed By
Essential Intent
DAO Organization
Outcome
PASSED
Proposal Date
May 24, 2022
Meeting Notes
Type
Community XP
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and the Moonshot Collective & Builderband communities will merge into one community. This will be announced in the forum, and the builderband channels in the discord will be archived. Builderband builders will be given the opportunity to opt into the merge.
Proposal
  • Tensions: There are currently three builder communities within GitcoinDAO, all having many overlapping tasks, efforts and missions.
  • Proposal: We plan to consolidate two of them (moonshot and builderband) while aiding in increased participation in third (events and hackathons) Here
    • Post the above doc to the gov forum, announcing the merge of moonshot with builder band and make the proposed changes to discord.
      • Archive builderband, builder-general and builder ops channels
      • Allow the opportunity for builder band + builders to opt in to a new permission
  • Clarifying Questions:
    • Loie - Does it change the theme of what type of builder group it is? I know MC was the prototyping hub, I wonder if this remains, merges with builderband, or changes in general? Is it still prototype focused?
      • Emu - Same thing, they are merging because their intents became similar. MC contributors were looking for full-time jobs but had none to offer, same issue appeared in builderband. Didn’t want to string people along
    • Kris - Will you just migrate everyone in builderband to MC or give them the opportunity to join?
      • Emu - I think the latter, I’m trying to be strategic about thinking & knowing about these people. Don’t want to force any changes
    • Sean - Don’t feel like the document outlined what the community was trying to do. Would be great to more tangibly quantify how the community exists (emails, discord). Want to quantify relative sizes of these circles to determine the relative purpose.
      • Emu - Builderband is only about 100 people, large overlap between what they want to do at builderband and what they want to do at MC. This is what spurred the ideation of merging. Want to bring together the community to promote engagement
  • Reactions:
    • Thumbs Up
      • Jodi - On the surface, no objections. I think it would be helpful to think through exactly how / solicit feedback from the community (forum post). Supportive of MC testing this out
      • Loie - Supportive, reduces double work + love partnerships. Brings up a curiosity around the efforts we’ve put into education. I have always been an advocate that web3 orgs should be educational hubs but in bear market times we gotta look at essential intent & making sure we prioritize Grants 2.0 and token utility with our energy/resource expenditure
      • Sean - Support. On the fence on whether it should be a proposal or not, but definitely not opposed. Aligning resources + focusing in
      • Annika - Supportive, these two communities were stood up with very different purposes and have scaled over time. I would suggest adding the context to the gov post. Other reaction is budget stuff, I assume that’s been thought through but calling out the implications here
      • Tigress - Supportive, like the idea of organizing teams. It’s important to align priorities and to really make the move optional for the contributors
      • Simona - Supportive, it’s important to make it an optional thing and also have that conversation with builderband to see what the alignment/overlap is. Want to get a sense of their sentiment, don’t want this to seem like a takeover.
    • Thumbs Down
  • Amendments:
    • Emu - No amendments, just refining the government post for additional context / clarification
  • Objections?
    • None
  • Passed
    • Yes