Your stack rests on packages maintained by volunteers. That works right up until you hit a bug nobody else has hit, or a maintainer steps away, or you need a fix on a timeline an unpaid maintainer has no reason to meet.
I keep a retainer open for exactly that: triaging issues in your dependencies, writing and upstreaming patches, and maintaining a supported fork if upstream isn't moving. Where possible the fix goes upstream, so you stop carrying it.
Nonprofits and OSS maintainers get a standing discount โ just say so when you get in touch.
This is for you ifโฆ
- A critical dependency is unmaintained
- You need a fix on your timeline, not a volunteer's
- Procurement wants a support contract before approving a package
- You want to fund the OSS you use, usefully
Also available
Other ways to work together.
Django Consulting & Development
Senior Django help for the work your team keeps postponing.
Learn more โAI Workflow Engineering
Getting an LLM feature from a demo that works to something you can actually run.
Learn more โPython Deployments & Infrastructure
Getting your deploy process to the point where nobody dreads it.
Learn more โ