How to Embed Open Source Contribution into Your Company's DNA

When I created BearStudio, our priorities were simple: find clients, deliver what they asked for, and somehow ship the fixed-price projects that had spiralled out of control. Open-source contributions stood far behind. With a young and shy team, no historical contributors, heavy reliance on JHipster, and limited resources, nothing seemed to naturally push us toward building an open-source culture.

Yet the core challenge quickly became clear: one person doing open source is not the same as a company doing open source. If that person leaves, the practice disappears. And unlike individuals, a company cannot rely on evenings and weekends. Contributions must happen on work time, employees cannot be forced to do them.

Still, the “why” remained undeniable. Our industry depends on open source. IT services companies earn revenue thanks to it. Contributing is both a responsibility and an opportunity: a way to give back, and a way to demonstrate expertise.

Our Contribution History

Over the years, this mindset has shaped our internal projects. In 2019 came Formiz and Start UI Web. In 2021, Start UI expanded to React Native, Figma, and a full CLI. In 2022, we released Start Repo. In 2023, FicusUI brought a Chakra-like experience to React Native. In 2025, Lunalink and ui-state added small but high-impact tools for our team and clients.

How We Built an Open-Source Culture

1. Engaging with Tech Communities

Open source is collaboration in the open. We encouraged teammates to attend conferences, volunteer, organize events, or speak on stage. Even non-developers. Meeting maintainers and seeing real projects behind the scenes lowers the barrier to contribution and strengthens confidence. Creating your own community is the next big step, if you can. I created Fork it! Community as a way to maintain this dynamic all over the world.

2. Contributing to Existing Projects

Starting is often the hardest part: impostor syndrome, choosing the right project, understanding contribution workflows. We focused on tools we already used, promoted no-code contributions (issues, testing, design, documentation), leveraged “good first issues”, and dedicated specific days or annual periods to contributions.

3. Creating Our Own Projects

A company project requires clear goals: for the business, for contributors, for clients, and for users. Our methods included preparing backlogs, running code retreats, using lunch breaks or inter-contract periods, practicing mob programming, and appointing a project leader treated like an internal product owner.

4. Maintaining and Growing the Project

Beyond the first release comes motivation, time management, and ROI questions. Marketing (stickers T-shirts, conference booths, documentation, landing pages, social media), creates momentum and credibility. Stars become an organic KPI. The real ROI appears in skills growth, improved efficiency, new business opportunities, and increased confidence.

To conclude: building an open-source culture is not about money. It is rooted in contribution, learning, visibility, and long-term value. But ignoring the financial reality would be naive. People invest time, companies dedicate work hours, and solo developers still need to make a living. Sustainable ecosystems rely on donations, sponsorship, and clear economic models; not to “profit from open source”, but to keep the work alive. Acknowledging this doesn’t weaken the spirit of open source; it protects it. With the right structure and genuine personal involvement, side projects can grow into company projects, and open source can naturally become part of a company’s identity.