1.8.0 Governance Team Metadata v0.00 MVP

[trainfarb]

Create an initial set of metadata that will help people see the value of having a governance team and how to implement one in the quickest way.

[trainfarb]

2023 09 05 @ 1136cst Each issue is governed by the same gaming structure. That’s defined here

• [x] Brainstorm a set structure for all GitHub Issues created in a GitHub Organization - outline for the tutorials that’s engaging Each Issue (9.0) Default Protocol/Outline (1.8)

  gr18ourStory
  gr18v0chord: Governance Team: What team created the protocol for this Non-Fungible Tutorial (NFTut) game?
  gr18v1vision: Platform Canvas: What will someone create by completing this NFTut?
  gr18v2values: Tokenomics: What is the value exchange associated with completing this NFTut?
  gr18v3game: hempPaper: What are the rules for completing this NFTut?

  @ 1144 realized this is definitely the team associated with meetings again. I had moved it down to marketing for risk management meetings, but after completing this outline, this is the way to go

[trainfarb]

MERGED from https://github.com/trainfarb/trainfarb/issues/41

Intentions: Stacks Community Grants Pilot Program: Create Templates for others who join their ecosystem ourStory: Create templates for everything in GitHub and create documentation. TSOBTC: Use this as a basis of design for TSOBTC’s application process to form the DAES. hu3agency: Use this as basis of design for daoTeaching: Barstool Sports Casino tied to a Community Grants program for sponsorship program for education.

Reference document: Community Grants Pilot - Master Doc v1.00.02

https://arts.ca.gov/wp-content/uploads/2022/05/2022_CACreativeCorps_Guidelines_Revised.pdf

https://arts.ca.gov/wp-content/uploads/2022/01/RankingGuide.pdf

• Turn this document into a template that can be used with TSOBTC

Problem:

• Hard for web3 projects to attract and support artists
• Hard to define criteria for proposal submission process

Solution:

• Platform ecosystem that allows people from different backgrounds to connect

Product:

• Take HeroGamer twitter thread on onboarding as the source of this work for brainstorming of v0.00.00
• Reading through the document and add it to github as a record
• Allow the team to work in their own platforms and just keep a saving
• Lock down specification this month - simple - and the iterate on next round

Next Steps:

• Longstreet and Fred are in
• Keep application simple - vision of one pager from open sats
• Everyone review Open Sats one pager
• Simplest way to get off the ground is Open Sats website one pager fill out the form
• We need to come to consensus on what questions to put on the form
• Check collaborative word doc for the questions for the application form (ONBOARDING)
• Once we have the questions down, we can host it on a form block survey or web2 website
• Where will applications be displayed after they’re submitted?
  • Want this to be as transparent as possible
  • Why all of our docs are in the cloud
  • Members list is publicly declared
• Where can we host this? View on github
  • Maybe GitHub Pages so github can be a viewer, but interact like a website
  • This would be the onboarding website that we create
  • Can we use Partiful for this?
• Next steps: EVERYONE HELP VET THE APPLICATION QUESTIONS
  • Section 3 - should these questions be reduced or expanded to help efficiency of vetting?
  • Any future support for pre-post applications?
  • Finalize application forms next week?
  • How do we measure these grant

Community Grants Pilot Program Main Tasks by Streamer:

• How to launch a Community Grants Program

• Turn the Master Doc into a template for TSOBTC scholarship fund
• TSOBTC can act as a training program to help people better understand the Community Grants Pilot Program
• Course listed by Community Grants Program
• Act as a fly on the wall and create a representation for this in GitHub first and then Notion to recognize that they feel GitHub is too complicated (see below)
• Community members who help out a program
• Create an Open Source Platform Ecosystem case study for the Community Grants Pilot Program
  • Ecosystem Sponsor: Community Grants Program
  • Platform Provider: Notion (Portfolio) & GitHub (Wallet)

Categories: Put all items from document into here:

• Onboarding
• Training
• Governance
• Operations
• Product
• Design
• Storytelling
• Publication
• Portfolio

Project Name One Liner of what they want to build Project Descriptions If people want to add a video Describe impact for the stacks community Timeline and Milestones

Suggested Approach for

• Crowd source a standardized format of what we’d like to see from an applicant / learner
• Suggested using GitHub to help them present their project

Suggestions:

• In depth questions to source good ideas from applicants goodkitty:
• compare applications apples to apples
• using something like github is confusing for artists
• Block survey form where there’s a questions and answers that they can submit
• What’s the impact of the project and its importance to the community
• Who’s their team
• Why are they the right person to be a founder and build for the community
• Hiro gamer saying github is too complicated

HeroGame:

• Keep it simple
• GitHub is too complicated (problem)
• https://opensats.org/apply This is a good example for how the community grants program does onboarding
• No DAO structure for what we’re
• If we’re not a DAO, then we have no legal ties to entities - being a DAO would complicate things (Open Source Platform Ecosystem)

Juliet.btc

• Is this going to be a DAO, and if so, how will it work?
• Regulatory concerns with creating DAOs

Rapha:

• Having advice from professionals
• Having something simple and thought out criteria of what we want
• We want to attract the best builders onto stacks & bitcoin

Overlord:

• Good to have public spaces for asking questions

Natalie:

• @mClubDAO
• Experience reviewing a lot of grants
• Make it as simple as possible
• GitHub
• Open Sats
• Air Table
• Worked in Chicago
• Get to the nitty gritty of what we want and ask people
• Before grants go to review, good to have space where people can ask questions
• Will help give people space to help people flush out their ideas
• Filter processes for grants
• Not suggesting helping them for grants with potential conflict of interest
• A lot of people have great ideas but aren’t Devs, so it’s hard for them to connect
  • goodkitty agreed - how to involve people who aren’t tech minded
  • herogamer feels this is a similar concern with all grants programs
  • Can we present the 10 platforms to help us attract a broader range?
  • Help them share resources as they go through the program
  • Suggest a way for people to work on their own programs while working with others as a side project
  • Way to bring this to universities to onboard people through TSOBTC into the Stacks Community Grants Program

Brad:

• Wants to get clarity
• If we don’t have set criteria for what we’re looking for, we’ll waste time listening to things that fall outside of what qualifies

Office Hours:

• Rotating group of Stewards office hours for steward who’d be able to help

Does something like your idea already exist? / How will yours differentiate

• Two categories: projects that are similar and brand new projects

Resh: Page 24 & 25 for application structure

Mentorship

• They have the ability to ask from someone with certain expertise
• TSOBTC as a potential

ADVANCE to https://github.com/trainfarb/trainfarb/issues/49