We contribute to Open Source

by Marks Bogdanovs, Owner

At Net service, we’ve always been strong believers in the power of open source. We use open source tools daily—from our application frameworks to our CI/CD pipelines—so it only feels fair to give something back.

While this isn’t technically our first time contributing (we’ve submitted our fair share of bug fixes and improvements before), but some time ago we understood that list of tools we could contribute is actually not so small. We decided to publish our Laravel Pint Docker container first—which we use in our CI/CD workflows. That led to setting up a proper GitHub organization and a GitLab group to better organize and share our contributions.

Open source has always been close to me personally. Whenever I see a chance to contribute—whether it’s a small fix or documentation tweak—I jump on it. That same spirit is now officially part of how we work at Net service.

We contribute to the tools we use the most. And those tools are Laravel, Docker, GitLab CI, GitHub Actions, and other DevOps-related technologies. Our team focuses on packages, bug fixes, and documentation improvements—things that might seem small but make a real difference over time.

To support this initiative, we’ve also made open source part of our work culture. Our team members are allowed (and encouraged) to contribute during work hours, especially to the tools we rely on daily. If there’s nothing relevant on the list, they’re free to support other projects they’re passionate about. As long as the work gets done, we trust our people to make a positive impact however they choose. And it is something I believe as a company owner and developer myself.

Our philosophy is simple: solve your own problem first. If it’s a challenge for you, chances are it’s a challenge for someone else too. That’s how we approach the projects we publish—we use them ourselves, and we improve them as we go.

We’re not actively seeking contributors, but we’re more than happy to welcome anyone who finds our tools useful and wants to get involved. The more, the merrier.

So, if you or your team is using some of the tools we have published or are maintaining—say "hi", it is always nice to know that tool you are supporting is used by someone else except yourself

Tell us about your project