-
Notifications
You must be signed in to change notification settings - Fork 1
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
For fun: Ubiquity platform - Give THANKS to the developers #116
Comments
We need to research the big repositories first and then find the contributors. It's a limitation of the GitHub API. It is an interesting idea but we also would need to create an onboarding flow so that they create a wallet and claim. This is feasible! |
Potentially, we can start from the lists of projects compiled by others. Electric Capital about the Web3 projects Then add various rankings for the Web2 projects |
Rating of top crypto projects on github, watchers, commits, stars Also, we can manually collect GitHub repositories from websites of top-500 crypto projects. |
Taiko (and some other Web3 projects) appreciate specifically contributors on GitHub. |
Magic Eden Rewards |
Memecoins can be used to fund Open Source projects. Vitalik about memecoins |
Recently we discussed Ubiquity platform to stimulate contribution to Open Source.
The platform can have rich and customisable options to incentivise and reward contributors on GitHub.
We can use the airdrop to create hype, attract developers-contributors, and Open Source projects in the future.
A preliminary vision is to get all developers' accounts through GitHub API, and determine their contribution to large and medium-sized Open Source projects.
Our token can be distributed according to the past developers' contribution to any of these projects.
A developer will be able to claim the airdrop after confirming ownership of an eligible GitHub account using pull request to a dedicated repo.
The token for the airdrop can be called THANKS and motto could be
Give THANKS to the developers
The text was updated successfully, but these errors were encountered: