Devlooped is all about accelerating your dev loop through sharper tools.
These tools span several domains, such as testing, AI, general-purpose CLI and build tools, application architecture, and more. Some are well established, others niche, some large and some small.
To support us, rather than per-project licensing (which can become costly or annoying to keep track of), we instead offer the Open Source Maintenance Fee, which covers all current and future libraries and tools from Devlooped.
If a particular software/package does NOT include the OSMF EULA, then you're not bound by it at all.
Open Source Software is free, but maintaining an Open Source Project is expensive. Think about:
- Triage issues
- Keep build scripts working
- Update software dependencies
- Track security reports
- Produce new releases
- Tackle spam in the discussion forums and issue trackers
- Maintain signing certificates
- And many, many other chores
The Open Source Maintenance Fee is a simple and sensible way to pay for the time and effort they spend sustaining a project.
We started using this approach to test if it can be a viable mechanism for ongoing sustainability (for example SmallSharp, Devlooped.WhatsApp and others.
If you're using a project with an Open Source Maintenance Fee EULA and you, your organization, or your project makes money, select the monthly payment tier that applies to the size of your organization. If not, a personal sponsorship of your chosen amount to support @kzu's favorite activity is also welcomed!
Since the Maintenance Fee is paid via GitHub Sponsors, it automatically covers any SponsorLink sponsoring requirements for projects using it.
Some fancy stats about our favorite activity (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 or interactive CLI 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 🙏.
If you are an oss author, you don't have to sponsor me unless you want to 🫶.
- 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 an implicit 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! This allows organizations to support projects their employees love and streamline invoicing.
Finally, if you are an open-source author or contributor yourself, chances are you are elegible for an implicit sponsorship I'll grant automatically! If your account shows up in the OSS Authors, you can just sync your implicit sponsorship and continue enjoying my projects with no additional sponsorship needed. Contributing your valuable time to other projects is great too.
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: