Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a community program #360

Open
0xZakk opened this issue Oct 12, 2023 · 1 comment
Open

Create a community program #360

0xZakk opened this issue Oct 12, 2023 · 1 comment

Comments

@0xZakk
Copy link
Contributor

0xZakk commented Oct 12, 2023

Problem

Summarize the raw idea, use case, or something you’ve seen that motivates us to work on this.

We want the application to work in a generalized way, per "community program." This means that there should be a way for someone to connect their wallet and create a program for their community (Gitcoin, Celo, Aztec, Arweave, etc).

Apetite

Select one of the following and delete the other. Add any nuance below. How much time are we willing to spend on this and how does that constrain the solution?

Small Batch: This is a project that a team of one designer and one or two programmers can build in one or two days. We batch these together into a six week cycle (more on that later).

Solution

The core elements you came up with, presented in a form that’s easy for people to understand. Drawings and doodles are very encouraged.

We need a way to create and represent a community program in the application. That means a program creation flow that creates a profile in the registry for that program and lets it create pools (which will act as separate seasonal funds).

Examples:

  • Kyle creates the Gitcoin community proposal program and adds Rena, Jon, Zakk, and Nate as program managers
  • Alexa create the Celo community proposal program

Behind the scenes, this should create a profile in the project registry for the community program. This profile will tie all the community funds together.

Graphic here

The community creation flow is effectively our onboarding flow. Each community program should be distinct, even though a community (i.e. Celo) might create multiple community programs (i.e. Climate Collective, Social Impact, DeFi, etc [read more]).

Rabbit Holes

What additional details about the solution are worth calling out? What things are we specifically trying to avoid?

Programs should be fairly lightweight and not include a ton of data about them. This data should be stored as JSON on IPFS as the metadata attached to a profile in the project registry. Some of the data collected in this creation flow should be informed by what gets displayed in the detail page (separate shape up).

Planning Docs

List or provide any other, related planning docs that will help someone grok the problem or solution

Copy link

linear bot commented Jul 25, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants