I’ve spent my career deeply immersed in open source licensing issues. And before I was a lawyer, I was a software developer. So I’ve talked with many developers about what matters to them about the software they use, and how it is licensed.
Open source licensing can be a complex, sticky subject, and (ironically) open source works best when we can avoid diving into all of the minutiae.
Which is why we felt there was no time like the present to put together a guide designed for developers who are using open source code and want the basic information they need in order to successfully navigate the license landscape.
In the new Tidelift guide to working with open source licenses we cover:
Why you as a developer should care about open source licenses
The possible business impacts of not paying attention to how your open source components are licensed
3 common approaches organizations take to licensing (and pros and cons of each approach)
How to identify and resolve licensing issues and prevent new issues before they crop up
If you want the basic info you as a developer need to not get tripped up by problematic licenses, this guide is for you!