GoR: monthly thematic focus with weekly workshops

[moul]

To effectively address our complex topics, I propose a structured monthly focus, with each month dedicated to a specific theme (e.g., January: Evaluation DAO, February: Governance, March: Documentation, etc.).

Weekly Breakdown:

1. First Week: Host a public workshop to explain the month's goal and conduct an AMA session. We'll then snapshot the discussed document for clarity.
2. Second Week: Set up a dedicated GitHub project board or a meta issue. Here, we'll propose our vision for subdividing the topic into subtasks/challenges and link existing issues/PRs to our plan.
3. Third Week: Focus on drafting code, such as interfaces, for one or more tasks. This allows community members who are proficient in development but less confident in architecture to contribute effectively.
4. Fourth Week: Devote our efforts to coding one of the tasks ourselves, demonstrating practical application.

Goals:

• Improve clarity and alignment on complex topics.
• Foster transparency and inspire others through our methods.
• Prioritize tasks for efficient review and progress.

I believe this approach will greatly enhance our collaborative efforts and ensure productive engagement on each topic.

[moul]

I can handle the first month alone, but I would like the @gnolang/devrels and @gnolang/tech-staff to adopt this new campaign system if it proves to be efficient.

cc @VT-Cosmos @michelleellen @waymobetta @leohhhn

[VT-Cosmos]

@moul - @MichaelFrazzy wanted to focus the first month on Evaluation DAO. One other point on this was to make it a Townhall rather than AMA. Maybe a townhall with AMA at the end.

[MichaelFrazzy]

@VT-Cosmos do you mean the idea we talked about to potentially have a monthly check-in with the community, to go over exact GoR tasks they may help with as we get more and more defined? Or just the general work being done on scoring/judging and GoR as a whole?

Both definitely connected, I just want to make sure I'm understanding this post correctly. I read it as presenting and subdividing internal tasks as kind of "decentralized/task specific working groups". Feel free to correct me!

[VT-Cosmos]

@MichaelFrazzy - I am referring to the monthly check-in with the community

[michelleellen]

Hi @moul @MichaelFrazzy @VT-Cosmos

What do you think about this for the first steps to the workshop:

• We build an internal Game of Realms presentation that we dog food internally with the team and turn that into the first workshop content to build on. (Public in March)

Why? I think it is important to set the stage and potentially position it like 'Game of Realms - road to mainnet' that way we can highlight that this is an important piece of having a seat at the table (DAO) while earning rewards and contributing. We did this similarly with Game of Stakes and Cosmos, validators contributed and participate in the incentivized testenet in order to earn a slot on the genesis validator set.

Also in this vain, we can identify key challenges in two or three buckets related to mainnet demands like data migration (Joeson example) and tutorials...etc.