Kai Cataldo • January 6, 2020
The beginning is always the hardest part.
I've been mulling over what I want to say in this, my first blog post and official announcement of my new career trajectory, for a little while now. There's so much I want to talk about that it's been difficult to know where to start.
So let me begin by sharing the exciting news. After months of self-reflection and many discussions with friends and colleagues, I have decided to pursue working on open source software full-time! I'll be splitting my time as a core maintainer between two amazing projects - ESLint and Babel - and am particularly excited about improving the integrations between them.
For those unfamiliar with these projects, here's a quick summary:
I have a few overarching goals in pursuing full-time open source work:
- Both ESLint and Babel are important tools that make the web a better place for us all, and they deserve dedicated maintainers and support from the community. I want to help make both tools and their respective communities the best they can be.
- We as a community need to figure out how we're going to support the open source projects that serve as the infrastructure we build the web on. The current model of volunteer-based maintainership is detrimental to the well-being of maintainers and it puts the future of these integral projects at risk. I've found myself in the unique position of being able to explore this, and I want to do so not only for my own growth, but also to add to the body of knowledge around sustainable open source software.
- I want to champion for more welcoming and inclusive open source communities. The more people want to be involved and the more diversity of thought we can draw upon, the better and more resilient our software will become.
I also have some concrete goals that I am focusing on immediately (in addition to regular maintenance responsibilities like issue triage, PR review, and meetings):
- Figure out a better maintenance strategy for babel-eslint
- Work on the ESLint v7 release
- Find ways to lower the barrier for contribution to both projects
- Improve the ESLint website
I'm currently planning to be funded entirely through GitHub Sponsors and ESLint and Babel's Open Collectives. I'm starting out at roughly 60% of my target monthly goal (which is amazing!) and am confident that, with the support of the community, I'll be able to reach it.
Thank You, Thank You, Thank You
I'm so grateful for my dedicated, supportive colleagues on both the ESLint and Babel teams. I don't take lightly the trust you have placed in me, and I'm humbled by this opportunity. I also want to thank the folks working on tools like Open Collective and GitHub Sponsors. Your work has enabled me to pursue something that, even just a year ago, felt unattainable. Last but not least, thank you to the community for all the generous support that has allowed me to take this leap of faith by sponsoring ESLint and Babel. This is only possible because of you.