2024 Roadmap + Sponsorship

[drwpow]

Hello! Wanted to post an update on the current project status and where it’s going.

Usage

Usage of both openapi-typescript and openapi-fetch has gone up month-over-month, and openapi-typescript is quickly approaching the 1M downloads/day milestone 🥳!

It’s relied on for infrastructure and accuracy at many major projects including Google Firestore, Nuxt, and many more. This is only possible because of community contributions and support.

Sponsorship

Some of you may have noticed a sponsorship button in the sidebar the last couple months, and there’ll be a new sponsor on the docs soon (Zuplo, the first company sponsor)!. Other companies like Speakeasy have also expressed sponsorship interest.

Naturally, taking money always raises questions about how it affects the project. So in the interest of transparency, hopefully these bullet points paint a clear picture of the situation:

• Though I’ve worked on many OSS projects where sponsorship is involved, this is the first time I’m managing it myself and I’m still learning. I want to be as transparent as possible (why I’m posting this), so please interpret any slip-ups as accidental!
• I’m taking on sponsors so this project continues to grow and doesn’t fall by the wayside. I’ll be using the $ to pay contributors and not taking it in directly.
• The actual payout mechanism / bounties are still TBD (if you have had a good experience with a process, 💬 leave a comment!), but will keep that transparent as I develop a plan. As of now I haven’t pocketed any money from sponsors.

Roadmap

Some may have noticed that 6.x updates have slowed, and 7.x has been looming for a while but hasn’t dropped. The current status of all of that is:

• 7.x is ready for stable release, but openapi-fetch needs some bigger updates that I need to release, so that they release in tandem (it results in breaking changes for openapi-fetch which will be published to 0.10.0).
• I have been pulled in other directions lately that keep [email protected] from being released
  • Sidenote: there’s not currently a 1.0 roadmap for openapi-fetch, which is also something I’d like help with
• The quickest course of action is for me to finish that and publish both; it’s just been a longer cycle than originally anticipated

So all that said, to keep the project growing and running smoothly in the future as I anticipate my available time on the project will be diminished even further in the future, I’d like to propose making openapi-typescript its own organization and inviting more community members to become core maintainers on the project.

I realize in hindsight some may have felt like it was still “my” project with my name attached to it, and that was really never the case. It was always just one of the many OSS projects I maintain, and was only under my personal GitHub account for expediency. But this project has outgrown me and I couldn’t be prouder of the community support that made that possible 🙂.

So look forward for a possible org creation just to leave room for more contributors. But that doesn’t mean this shift is caused by some sort of buyout, or it’s turning into a company, etc. etc. Still FOSS, still MIT licensed, and will be forever. I’d just like to invite other contributors to share the load in maintaining this project so everyone can benefit, and I won’t be the bottleneck moving forward 💙

[drwpow]

Update—this now lives at the github.com/openapi-ts GitHub organization (in fact, GitHub already redirected you here!). As discussed 👆, the project isn’t changing hands, and isn’t in cahoots with a business or corporation.

But it will create space for more people to get involved and move the project forward without me as the bottleneck. Stay tuned for more info on governance and sponsorship.

[drwpow]

Update 2: the Governance has been published, and we’re currently seeking contributors to join!

The Open Collective sponsorship page is also up, which will be the source of sponsorship moving forward. GitHub Sponsors got a trial run, but didn’t meet demands so that’s been removed. If you are a current GitHub Sponsor, you’re still credited as a sponsor, and can use it as long as you like, or move to Open Collective. New sponsors can only sign up on Open Collective.