Quest for finding open-source sustainability with Github sponsors · thetutlage meta · Discussion #5

Hello folks 👋

Github sponsors are finally available in India, and I hope it will help me sustain working on AdonisJS full-time in the longer run. However, before I share my plans around Github sponsors, let's look at the current situation.

Sponsor me on Github

How do I currently sustain working on AdonisJS?

I now have a Patreon campaign from which I receive financial support to continue my work on AdonisJS. Also, I have received some grants from FOSS UNITED, and a significant chunk of the sponsorship amount comes from Cavai.

Overall, I am not broke, but neither in a situation where I can say that the framework is sustainable. If a couple of companies decide to stop sponsoring me, I will have to find a job.

Goodwill based open source does not scale

So far, the sponsorship I receive is based on Goodwill. However, some great individuals and companies decided to help me financially without asking anything back in return (directly).

This model cannot scale, meaning the number of people to put money on Goodwill will always be less, and the fear of them pulling out will always be there.

The dream of working full-time on open source can only come true if we can find a way to monetize it or raise money from venture capital. Raising money is not my cup of tea, so monetizing it is the only way to proceed.

What works great with developers is the paid content and paid packages. Everyone wants to learn new things, level up their game, and won't mind spending extra bucks on a paid package if it can save them some real-time.

Why am I excited for GitHub sponsors?

Fundamentally speaking, Github sponsors is just a platform like Patreon. The sustainability comes from the value I plan to deliver and not directly from the platform I use.

However, Github sponsors help streamline the value I plan to deliver.

• It is easier for individuals and companies to sponsor since most of them are on Github already. Whereas, with Patreon, it always felt like an additional account they have to manage.
• It is easier to authenticate users with Github and provide access to paid content only to the sponsors.
• Using Github packages registry to distribute paid packages only to the sponsors.
• Maybe, one day, Github will launch some badge to recognize sponsors as they open issues or start new discussions.

Paid content and paid packages

I have a bunch of content lined up for months and maybe years, for which I have not been able to find time and motivation.

Lining that up with sponsors seems like a great approach to me. If producing quality content results in more sponsors, motivation will automatically follow.

Adding learn section to the website

I will be adding a learn section to the AdonisJS website, which will have a mix of free and sponsors-only content, and my primary focus for the rest of the year will be producing as much content as possible.

After AdonisJS, I will do the same for Japa and Edge (Edge will have its website too).

Tiers and pricing

My sole focus is on producing content for the rest of the year, and therefore I am not creating any high dollar value tiers targeting advertisement space or partnerships.

The lowest tier will be $19 (with the option to pay more $29).

It will give you access to:

• All the paid content
• Paid packages
• Sponsorware (early access to open source packages)
• A special sponsor role on Discord

Ideas backlog

I have over 50 ideas in my backlog. But let me share the top 6 in which I have confidence and have done some research. They may get launched in any order.

• Rebuilding GitHub Discussions from scratch - GitHub discussions have a lot of hidden nuggets like nested threads, threads pagination, reactions, and upvotes. There is a lot to unpack and learn by building it from scratch.
• Email management done right - Email management has a lot of quirks, and I have seen products running in production doing it wrong. So this will be a mini-course in which I will try to mimic Netlify and Github styles of email management.
• File uploads - Again, taking some real-world scenarios and creating a robust system around File uploads.
• Route model binding (sponsorware) - Early access to an open-source package and walk-through videos on how to do Route model binding in AdonisJS. I almost thought that Route model binding is impossible given the constraints of TypeScript, but then a conversation with daniel coulbourne forced me re-think it.
• Beginners course - This will be a 101 course for anyone coming to AdonisJS for the first time who needs a helping hand to move around and understand the framework better.
• Persona - User management starter kit for your Next SAAS/Public app. https://twitter.com/AmanVirk1/status/1460191963723014145/photo/1

---

Sounds like a plan? Sponsor me on Github 🙌