Hi Tobias. Thank you for the article, I enjoyed reading it. It gave me something new to consider. This actually might help narrow down decisions regarding what tools to use, as noncompliance could consequences you're not willing to risk facing. I hope you put out more content like this. I'd be especially interested in how best to approach using OSS for younger/smaller companies, getting the right habits down early rather than accumulating OSS compliance debt. Thanks again!
It's really very unique and one of the most unseen content, regarding open source. Thanks for sharing the same.
I am willing to read a billion contracts than use proprietary bs
This is amazing and something to always keep track of. Thanks for sharing ♥️
This is something we don't see very often, thanks for sharing your perspective!
This is an important article. OSS licenses have so many vague and confusing terms e.g. GPLs "make available" or Suns added "classpath exception". The nuances run deep.
Hamthoven
Korean, Student, Humankind.
Hello, I am Hamthoven, a Korean developer. I read the article interestingly. I want to translate this article into Korean and post it on my hash node blog. Of course, I will add the fact that the text I will write is a translation, the original text link, and the author of original contents. If possible, please let me know. :)