Cargo thanks & fund tools


I think that it would be good to have two cargo tools:

  • cargo fund - that displays information about possible ways to financially support crate author(s)
  • cargo thanks - that allows to star GitHub repos

Similar tools are present in other package managers in different languages.

Recently I updated a crate that allows to star repos GitHub - woxtu/cargo-thank-you-stars: Give your dependencies stars on GitHub! , but unfortunatelly contact with crate author is difficult. Because of that I started to think that maybe it would be best to provide such tools directly on cargo level.

Please let me know what do you think about such possibility? If I would write such tools directly for cargo would such contribution be accepted?

Best regards, Michal

Issue about cargo fund Feature request : adding a funding field to manifest file format · Issue #8846 · rust-lang/cargo · GitHub

cargo fund already exists.


I think it uses good way to provide info about funding, but there are also other ways to provide info not just about GitHub - these ways require Cargo.toml modification. I was thinking about something like described here Feature request : adding a funding field to manifest file format · Issue #8846 · rust-lang/cargo · GitHub

Note that placing that information in Cargo.toml as the primary source would make it hard to change in old versions. IIRC, the Cargo defaults were updated to not include author names by default. Are you sure Cargo.toml would be the right place for such forward-looking information?


I don't know if it's the right thing from technical POV, Other package managers does that. Maybe they are all wrong? :wink:

I think that providing such information in cargo would be beneficial for crate authors. If X crate author would receive $1 donation per month from every company that is using his crate than world would be a better place. (At least in my opinion. And company for which I'm working at this moment wants to support developers)

Adding money to a system does have some potential negative effects.

  • Psychologically, it can turn a labor of love or fun hobby into underpaid work.
  • Also, if publishing packages looks like a way to profit, there's an incentive for people to produce more attractive-seeming packages of their own rather than to contribute improvements to existing packages.

Of course, the upside is that people get (some) compensation for (some) work. But, the most important thing for designing the system is: how good are the contents of, in the long run?


I understand your POV.

I would like to avoid this situation xkcd: Dependency

If someone wants to create and maintain great open source library/framework/etc for free it's great.

But I think it would be also good to have a better visibility that certain crate authors are accepting donations.