Today open-source is used in almost any software development cycle. We're able to deliver the best product to our customers faster than ever before. At the same time, nobody wants to sacrifice quality or the pace of production. We know a lot about software quality assurance, and we have tools to produce higher quality software. Could we use them to ensure the quality of the open-sourced solutions as well?A couple of years ago, I created a tool called Ossert. An experiment to asses the quality of every Ruby gem. While developing Ossert, I thought a lot about the quality of the open-source software.

In this talk, I'll talk about my experience in making the quality of OSS measurable: how could it correlate with project maturity stage? The patterns of its community behaviour? Finally, I'll share the set of practices I created to asses the quality of open-source development processes.