Yep, I read the privacy policy. I read the terms of service. I’m the guy who stumbles across software and immediately looks for the open source alternative.
Fortunately, I also get to work with a great team and an innovative open source platform in Baserow. (Looking for an open source alternative is actually how I came across Baserow in the first place.)
After some time building in the open, and living open source values, I’ve decided to share some non-technical takeaways about working in and contributing to open source.
Sharing is a core principle of open source. Without it, projects don’t survive. They need to shared. Their stories need to be told. Most of the time, open source projects start as solutions to personal problems.
Needless to say, these personal problems are not often personal. Instead, they’re problems shared by more people than we may initially think.
I created Reddit Account Manager out of a personal need. Then, I stumbled across one comment on Reddit saying that they wish they had some similar solution. Then, more comments piled in. It was easy to see the need beyond my own.
Even though this isn’t always evident at first, chances are there’s a market out there. How large that market is or will be is a different conversation.
Nevertheless, it’s important to share. Once it’s out there, you’d be surprised to find out how much someone else wants your solution, wants to contribute to it, and how much it’ll improve over time.
Open-source technology thrives on word of mouth. Personal recommendations carry more weight than an other form of marketing.
My closest friends—none of whom work in tech—learn about open source and decentralized software because of me. They don’t ask about open source software specifically, but they ask about things that open source software usually provides—like privacy, security, control over your information, customization, etc.
They ask about alternatives indirectly, know what they want in a platform, but not exactly knowing what open source is or why it matters.
Once I explain the benefits, necessity, and values, it becomes a lot easier to adopt to—and seek—open source software.
So tell your friends. Tell your family. Take the time to share.
Don’t worry about going viral online. Start with your circle.
I have 150+ contacts on Signal. Even though I’m often met with some resistance at first, once I explain how it benefits everyone to have open source and encrypted communications, the selling point becomes a lot easier.
And that’s the thing—it’s not a “selling” point in that I have something to gain from someone else, but rather we have all to gain and nothing to lose. It’s a win for all of us.
Because guess what? The same way you made a difference in your circle, they’ll likely make a difference in their cicle. How much of an impact they’ll have is a different story, but we can’t think in terms of all-or-nothing.
Remember: No raindrop thinks itself responsible for the flood.
Linux might thrive with little marketing, but that doesn’t mean open source in general doesn’t need marketing. In fact, I’d argue it needs more marketing, perhaps now more than ever as the modern internet continues to become enshittified.
Where it gets tricky is in how to market open source effectively. You see, the open source community is composed of knowledgeable, skeptical, and strongly-opinionated consumers.
They don’t want ads thrown in their face. They don’t want to be tracked. They don’t want to be targeted. They use uBlock Origin, VPNs, and other content blockers.
You can’t just buy ads and expect conversions. And even if you don’t buy ads and go the organic route, you can’t just be on Facebook, TikTok, and Snapchat. Because that’s not where they are.
Instead, they’re hanging out on Mastodon, Lemmy, PixelFed, Loops, and other places in the Fediverse. Because they don’t want ads. They care about privacy. They care about decentralization. They care about continuity, control, and other things that we don’t get with Big Tech.
So how do you market to people who don’t want to be marketed to, but also would probably be really interested in your open source project? I’ll leave that blog post for another time.
Open source developers are deeply passionate about their projects. Many aren’t paid, yet they continue because they care. One of the tenets of open source is that anyone can fork the code, modify it if needed/wanted, and keep the project running if something happens to the original project.
For most, it’s important that the project lives on beyond what the original developer(s) had in mind. Which is another great thing about open source—that passion transcends into meaning greater than any one individual.
Open-source taught me the value of small victories. In the early(er) days of Baserow, solving minor issues felt monumental. These small wins accumulate, helping you move forward, which keeps you going.
Even when I do something minor for one of my own projects, it’s a healthy reminder that what I’m doing matters because it’s not just for me.
Admittedly, I’m really bad at celebrating the small wins. My ambition’s constantly at war with my complacence, and I’m the first one to reach a huge milestone, then proceed to move the goalposts immediately because I expect even more from myself and look forward to the next challenge.
However, I’ve seen the impact of small wins both working solo and with teams.
The term “Ubuntu,” which relates to community and the interconnectedness of individuals and the humanity towards others, is one of the most widely-associated terms in tech because of Linux. Early on, it was the community that kept open source alive.
Even later, it’s still the community that keeps open source projects alive.
The best part about communities in open source is that they don’t need to be large, because community members are passionate. (See takeaway #4.)
Open source is about teamwork. While some projects rely on one developer, most thrive on collaboration. Working together eases the burden, prevents burnout, and brings talented people together. This collaborative spirit also fosters innovation, as diverse perspectives contribute to more creative solutions and improvements.
Open source projects benefit from a global community, allowing for around-the-clock development and support. This inclusivity not only enhances the quality of the software but also builds a sense of community and shared purpose among contributors.
We’ve all heard the old cliché: life is about the journey, and not the destination. As corny as it might sound, that’s the same for open source software as well.
Challenges are part of the journey and the fun. You can set the goalposts, but you’ll find more often than not that you’ll want to move the goalposts once you get to a certain spot (or at least I do).
The open-source community regularly faces challenges and grows from them. Don’t fight it, embrace it.
Open source projects succeed because their teams are tenacious. Is this the only reason they succeed? Of course not. But it’s still imperative.
You can’t overcome challenges without grit.
Everyone loves to root for the underdog. At it’s core, that’s a large part of what open source is.
Linux is the underdog against Windows and macOS. Firefox is the underdog to Chrome. Proton is the underdog to Google. Mastodon is the underdog to Twitter.
Embracing the underdog spirit brings pride and humility that very few other things can.