Hello there! This is @kzu's (sounds like 'kah-zu' rather than 'kzoo' 😉) organization account where I publish projects I think might be useful to others and not just personal experiments.
This is also the organization account you can actually sponsor to support my ongoing opensource work.
Some fancy stats about my favorite hobby (coding on GitHub, of course!):
I created SponsorLink as a mechanism to remind users that they can sponsor my projects if they find them useful. It also allows attribution on the dev machine of a sponsorship to potentially unlock additional functionality (or just remove the reminder and thank instead!). SponsorLink never issues any messages outside of IDE usage, so it will never disrupt your CI/CD workflows or CLI builds.
If you arrived here from an IDE and are interested in sponsoring, the (one-time) steps are:
- Select your sponsor tier 🙏
- Install the sponsor dotnet global tool by running
dotnet tool install -g dotnet-sponsor
- Sync your sponsorship status by running
sponsor sync devlooped
Feel free to dive deeper into the technical details of how this works. You can also implement SponsorLink yourself with minimal effort for your own projects.
If you have ever sent a PR that was merged into any repository owned by @devlooped, you are considered a sponsor already! Contributing your time and code is the most awesome way to support a project 🫶.
If you belong to an organization that sponsors @devlooped, then you are an indirect sponsor too! This allows organizations to support projects their employees love and streamline invoicing.
Sponsorships are renewed monthly (even if paid anually), so your dev machine manifest needs monthly renewal too.
You can simplify this process by enabling autosync
so that the IDE tooling can automatically do this for you by checking at most once a day for expiration and running
the same command you'd have to run manually: sponsor sync devlooped.
Active SponsorLink sync usage by sponsorship kind:
