Technology

72686 readers

2879 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago

MODERATORS

L3s@lemmy.world

enu@lemmy.world

technopagan@lemmy.world

L4s@lemmy.world

L3s@hackingne.ws

L4s@hackingne.ws

thanks.dev – open source funding platform (thanks.dev)

submitted 7 months ago by cyrano@lemmy.dbzer0.com to c/technology@lemmy.world

2 comments fedilink hide all child comments

cross-posted from: https://lemmy.dbzer0.com/post/32935539

you are viewing a single comment's thread
view the rest of the comments

[–] conciselyverbose@sh.itjust.works 18 points 7 months ago* (last edited 7 months ago)

TLDR: You set a donation amount, it uses your GitHub account and the projects you use and distributes it through their dependencies and the dependencies of dependencies. You can also customize to exclude or boost specific things.

Might be over-simplified, but that looks like the basic idea.

Details

You log in with your GitHub or GitLab account and nominate how much you’d like to donate every month – could be as little as $2 or as much as $100k. thanks.dev then collates the dependency tree across all the repositories in all the organizations you have access to and trickles your donation across that tree 3 levels deep, up to 8 decimal places on the dollar. You can scale your donation per open source project via boosting, or alternatively, you can exclude projects you don’t want any money going to. Everything else is automated.

Why do we think this is a good approach?

thanks.dev solves the “Who should I donate to and how much should I give them?” component of supporting open source. We think the biggest side effect of this barrier is the unbalanced distribution of donations across the ecosystem, with popular projects receiving the lion’s share of donations. The motivated minority primarily donate to the handful of projects that are top of mind. For example, Webpack receives close to $200k in funding per year via OpenCollective but its direct dependencies receive minuscule amounts of funding, and there are 80+ of them.

Furthermore, thanks.dev makes it super easy for companies – especially larger organizations to support open source. How else could they manage the logistics of supporting the thousands of projects they depend on? There really is no way without significant effort.

Another benefit of thanks.dev’s approach is that deeply nested packages get supported via an accumulation of micro-donations, which should ameliorate the funding component of the recent log4j incident.

What are our ultimate goals for thanks.dev?

An open source ecosystem in which maintainers can focus on their projects full-time, be funded by the companies that depend on them, and for those companies to attain a competitive advantage via access to faster, cheaper & more sustainable execution.

https://thanks.dev/static/why

Might be over-simplified, but that looks like the basic idea.

::: spoiler Details
>You log in with your GitHub or GitLab account and nominate how much you’d like to donate every month – could be as little as $2 or as much as $100k. thanks.dev then collates the dependency tree across all the repositories in all the organizations you have access to and trickles your donation across that tree 3 levels deep, up to 8 decimal places on the dollar. You can scale your donation per open source project via boosting, or alternatively, you can exclude projects you don’t want any money going to. Everything else is automated.
>
>### Why do we think this is a good approach?
>
>thanks.dev solves the “Who should I donate to and how much should I give them?” component of supporting open source. We think the biggest side effect of this barrier is the unbalanced distribution of donations across the ecosystem, with popular projects receiving the lion’s share of donations. The motivated minority primarily donate to the handful of projects that are top of mind. For example, Webpack receives close to $200k in funding per year via OpenCollective but its direct dependencies receive minuscule amounts of funding, and there are 80+ of them.
>
>Furthermore, thanks.dev makes it super easy for companies – especially larger organizations to support open source. How else could they manage the logistics of supporting the thousands of projects they depend on? There really is no way without significant effort.
>
>Another benefit of thanks.dev’s approach is that deeply nested packages get supported via an accumulation of micro-donations, which should ameliorate the funding component of the recent log4j incident.
>
>### What are our ultimate goals for thanks.dev?
>
>An open source ecosystem in which **maintainers can focus on their projects full-time**, be **funded by the companies that depend on them**, and for those **companies to attain a competitive advantage** via access to faster, cheaper & more sustainable execution.

https://thanks.dev/static/why
:::