Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
The term "warning" was already revised to "reminder" (https://github.com/gitcoinco/web/issues/2758), which was a positive step.
There is still a problem:
* The frequency of the reminders is too high (example: https://github.com/NethermindEth/nethermind/issues/334 )
One may say "but founders can snooze".
Yes, they can, but practice shows that they don't do this always, and that gitcoin does not automatically adjust (so it keeps spamming the issues every 3 days).
## Possible Solutions
* Funders can immediately reduce or even "snooze" the bot, by setting the auto-reminder interval to "3 days" "weekly", "bi-weekly", "monthly" or "none" (for those who prefer manual interventions, as e.g. I would as a funder). Defaults should be possibly "week" (3 days is too low, its a weekend + 1 day).
* The bot does not repeat reminders without "escalation"