A note to founders out there working with a heavily open source influenced stack: take a few hours to read through and really understand the history of these li

A note to founders out there working with a heavily open source influenced stack: take a few hours to read through and really understand the history of these licenses and how they work. It's likely to come up in fundraising and m&a due diligence and can cause panic from others (even lawyers) involved in the process who don't understand the fine points and assume that your proprietary code is laden with all sorts of burdensome obligations inherited from open source components.