Living with open source responsibility

It is straightforward to open source a piece of code and call it a library. It is effortless to maintain it when you are the only user, but what happens when you reach the first hundred or thousand downloads.

Semantic versioning, changelog, stable release, backward compatibility, continuous integration, code coverage probably would be some of the buzzwords that would pop up into your head.

Let's go through the process of being responsible open-source developer and maintainer.

Mario Blazek flag

Mario Blazek

Senior Backend Developer @ Q Agency