ethereum-org-website
ethereum-org-website copied to clipboard
Add public goods funding page
This use-case page explains how Ethereum can help improve public goods funding and reduce coordination failures.
Description
The page walks the reader through the following concepts:
- What are public goods?
- Why are public goods important?
- What is the problem with funding public goods?
- How can blockchains improve public goods funding?
Fixes: https://github.com/ethereum/ethereum-org-website/issues/6330
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated |
---|---|---|---|
ethereum-org-website | ❌ Failed (Inspect) | Sep 7, 2022 at 3:18PM (UTC) |
Hi - this seems to be a blank page - assume it is in progress? Please convert to draft so it doesn't ping us for review.
:white_check_mark: ethereum-org-website-dev deploy preview ready
- Deploy preview
- Build logs · 16m build time
Hi - this seems to be a blank page - assume it is in progress? Please convert to draft so it doesn't ping us for review.
I was trying to create a file in my fork of the repository earlier, which was why you saw a blank page (I've added the content now). I want to add a new file (a screenshot), so I can add a relative link to it in the article. Any idea how I can do that?
I'd add the screenshot to src/assets
and then use the relative path to link from your page.
I'd add the screenshot to
src/assets
and then use the relative path to link from your page.
Alright, thanks. I just pushed a new commit to make the change. Let me know if it works.
Love to see this @emmanuel-awosika!
I don't see any page in the preview deploy (cc @jmcook1186 @minimalsm am I missing something?). I suspect it's because there's spaces in the filename (that's not allowed). I think updating it from src/content/public goods funding.md
to src/content/public-goods-funding.md
would do the trick (we always use kebab case for filenames) - that would create this corresponding page:
https://ethereumorgwebsitedev01-emmanuelawosikaethereumor46991.gtsb.io/en/public-goods-funding.
Tagging this issue: https://github.com/ethereum/ethereum-org-website/issues/6330 - seems this PR would solve this!
Love to see this @emmanuel-awosika!
I don't see any page in the preview deploy (cc @jmcook1186 @minimalsm am I missing something?). I suspect it's because there's spaces in the filename (that's not allowed). I think updating it from
src/content/public goods funding.md
tosrc/content/public-goods-funding.md
would do the trick (we always use kebab case for filenames) - that would create this corresponding page: https://ethereumorgwebsitedev01-emmanuelawosikaethereumor46991.gtsb.io/en/public-goods-funding.
Just renamed the file per your suggestion. That said, the preview functionality hasn't worked for me in a while for some reason. This happens even when editing pages already on the site (which are properly named).
Hey @emmanuel-awosika.
Just wanted to follow up and update you on where we are at.
Last week (Feb 6) we discussed this at GitHub grooming, and decided we needed to workshop this content structure of this a bit. We had a workshopping call Feb 9 to workshop ideas for this page, and I'm working on taking our discussion on this and creating a new content structure. Once I have done that this week, ill follow up with this new structure. After that, the intent is to take as much of what you have written here and bring it into this new structure.
I wanted to apologize for how long this PR has been sitting, but I hope this update will help provide some clarity on where we are at with this, and that we are working to get this across the finish line.
Hey @emmanuel-awosika.
Just wanted to follow up and update you on where we are at.
Last week (Feb 6) we discussed this at GitHub grooming, and decided we needed to workshop this content structure of this a bit. We had a workshopping call Feb 9 to workshop ideas for this page, and I'm working on taking our discussion on this and creating a new content structure. Once I have done that this week, ill follow up with this new structure. After that, the intent is to take as much of what you have written here and bring it into this new structure.
I wanted to apologize for how long this PR has been sitting, but I hope this update will help provide some clarity on where we are at with this, and that we are working to get this across the finish line.
Hey @corwintines, thanks for providing an update. Sure, I'll be happy to help rework the page once the new content structure is ready.
Hey @corwintines & @wackerow. Any new information on how we might get this over line? I know a new ReFi page (which has some ideas related to public goods funding and regenerative cryptoeconomics) has been added to the website. But I'm wondering if we'd still benefit from a comprehensive resource on public goods funding.
@corwintines mentioned wanting to make the page more reader-friendly, and I'm in support. For starters, we could have some more concrete info about the impact of retroactive public goods funding using stats from Optimism's RetroPGF. This is just an idea at the moment, but I'll leave it to the team to decide the best approach to revamping the content.
@corwintines: Resurfacing this PR + sharing some of the newer ideas I have around the content:
- I believe @samajammin gave a talk at Devcon on “education as a public good”? I can’t remember if that’s the title—but I thought we could include a link to the talk (if it’s available) to the learning resources section.
- Now that @publicgoodsnetwork is on mainnet, is there a way we can include some content about the project in the page? For starters, this could just be adding a link to the project’s website in the Funding public goods with Ethereum section. But given its status (and novelty) as an L2 network specifically dedicated to funding public goods, we could consider giving it more attention in the content.
- Is there a chance we could revamp the content and publish in Q4 2024? An idea I have is to include more specific examples of positive impact by public goods funding initiatives—for example, statistics from Optimism’s RetroPGF, past Gitcoin Grants rounds, MolochDAO project funding, Protocol Guild distributions, etc. Another thought was that we could also highlight the value of public goods funding in the context of Ethereum.org itself—for example, saying one or two things about the planned donation round for Ethereum.org contributors at GG19 (eg. we could link out to a recap blog--if there's one planned).
- IIRC you said the team was still in talks over the best way to structure the page. Perhaps @konopkja has some insights from the UX research side that could help with that? Also, what do you think about getting some feedback on the content from folks from the Gitcoin’s Grants and/or Optimism’s RetroPGF team on the content? (My thought is they could provide some feedback on some of the concepts that we highlight in the page).
Deploy Preview for ethereumorg ready!
Name | Link |
---|---|
Latest commit | 21cc1749fa3af95fdbf12a1d9373c0fb35e0a43d |
Latest deploy log | https://app.netlify.com/sites/ethereumorg/deploys/65fdf4e0d9c2b7000757a6c4 |
Deploy Preview | https://deploy-preview-7732--ethereumorg.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Hey @emmanuel-awosika!
Thanks for the work done on this. We have had a lot of discussion as a team on the public goods funding page, both in the content written here, and the concept/goal of the page.
Where we landed is a need to reframe this page. We noticed a trend through reading and talking about this page that a lot of the discussion for the use case is around funding/voting. While these can be used for public goods funding, they are the core use case in this. I still think we can tie in how they can be used for public goods, but reframing this page around the use case, and then discussing an application like public goods seems like a better approach.
A structure we agreed on, but would like input is something like:
- Funding mechanisms (some ideas of funding mechanisms here, would need to be flushed out more and happy to help with this)
- Quadratic voting/funding
- RPGF
- Programmable money / donations
- Intro to DAO’s (point to DAO page)
- Unique properties that Ethereum brings to the table to enable
- Transparency
- Immutable
- Consensus
- Auto-executing (smart contracts)
- Privacy?
- Intro of what public goods are and tie in Ethereum’s role
- Simple intro, get rid of all the game theory. Introduce the concept, but don’t need to get into specifics with examples.
- Applications
- How quadratic funding can benefit public goods funding
I think there is certainly content written in the current state which will apply to this new structure, but a reframing here to be use cases first, and then an application like public goods funding would suit the content for ethereum.org better.
Let me know if you are interested in working on this pivot. Apologies for the pivot as well, but I think reframing this page will go a long way.
Hey @emmanuel-awosika!
Thanks for the work done on this. We have had a lot of discussion as a team on the public goods funding page, both in the content written here, and the concept/goal of the page.
Where we landed is a need to reframe this page. We noticed a trend through reading and talking about this page that a lot of the discussion for the use case is around funding/voting. While these can be used for public goods funding, they are the core use case in this. I still think we can tie in how they can be used for public goods, but reframing this page around the use case, and then discussing an application like public goods seems like a better approach.
A structure we agreed on, but would like input is something like:
Funding mechanisms (some ideas of funding mechanisms here, would need to be flushed out more and happy to help with this)
- Quadratic voting/funding
- RPGF
- Programmable money / donations
- Intro to DAO’s (point to DAO page)
Unique properties that Ethereum brings to the table to enable
- Transparency
- Immutable
- Consensus
- Auto-executing (smart contracts)
- Privacy?
Intro of what public goods are and tie in Ethereum’s role
- Simple intro, get rid of all the game theory. Introduce the concept, but don’t need to get into specifics with examples.
- Applications
- How quadratic funding can benefit public goods funding
I think there is certainly content written in the current state which will apply to this new structure, but a reframing here to be use cases first, and then an application like public goods funding would suit the content for ethereum.org better.
Let me know if you are interested in working on this pivot. Apologies for the pivot as well, but I think reframing this page will go a long way.
Hey @corwintines. The proposed content structure looks good to me. I'll reach out on Discord with details related to work on this page shortly.
[!IMPORTANT]
Auto Review Skipped
Draft detected.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yaml
file in this repository.To trigger a single review, invoke the
@coderabbitai review
command.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
-
I pushed a fix in commit <commit_id>.
-
Generate unit-tests for this file.
-
Open a follow-up GitHub issue for this discussion.
-
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitai
in a new review comment at the desired location with your query. Examples:-
@coderabbitai generate unit tests for this file.
-
@coderabbitai modularize this function.
-
- PR comments: Tag
@coderabbitai
in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:-
@coderabbitai generate interesting stats about this repository and render them as a table.
-
@coderabbitai show all the console.log statements in this repository.
-
@coderabbitai read src/utils.ts and generate unit tests.
-
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
-
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (invoked as PR comments)
-
@coderabbitai pause
to pause the reviews on a PR. -
@coderabbitai resume
to resume the paused reviews. -
@coderabbitai review
to trigger a review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai resolve
resolve all the CodeRabbit review comments. -
@coderabbitai help
to get help.
Additionally, you can add @coderabbitai ignore
anywhere in the PR description to prevent this PR from being reviewed.
CodeRabbit Configration File (.coderabbit.yaml
)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yaml
file to the root of your repository. - The JSON schema for the configuration file is available here.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json
CodeRabbit Discord Community
Join our Discord Community to get help, request features, and share feedback.
Noticed the build/preview was failing... updated this with latest from dev
and patched the image paths that would prevent it from building. Lastly removed the now-unused image. Will check back to see if this preview is at least working.
With the change of direction around the content of this page, im going to close this out in favor of a funding page in the future. I do appreciate all the work done here @emmanuel-awosika, and when it comes time to touch on public goods in content around the site I will certainly be coming back to this PR to pull from. It certainly will not go to waste!