Discussion on "The Price You Pay As A Developer For Using Open Source Software - A Tech Lawyers View"

Tobias C. H. · 2022-09-26T18:55:28.093Z

A few months ago, a client of mine looked at me like I was an alien when I told him: "Nothing is for free, neither Open Source Software." Maybe you also think: "What the heck is he talking about?" Fair enough. You don't have to pay royalties for usi...

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. :)

Please share the link to your translated post here, if you've posted it on hashnode.

Tobias C. H.

Thank you for allowing translation. And I realized a small thing, your Twitter link is 404. I wrote that link right way in my translated version article. ;)

Here is the link

Hamthoven no prob!

Thanks for mentioning it! I just updated the link to my twitter profile. Should work now... :)

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!

Thank you so much!✌️

Yes, want to to publish more content about OSS and “good habits” for OSS compliance in the future. Hope you stay tuned 😉

It's really very unique and one of the most unseen content, regarding open source. Thanks for sharing the same.

Thank you very much - so nice to read that :)

What could happen if you violate the contract for example ?

Different things could happen depending on the nature of the breach and possibly the country where it happens. You can think of claims for damages, injunctive relief, recall claims, loss of license rights, etc.

Maybe that's a good one for a whole content series. It's getting really complex at this point.

Very interesting thanks for writing that article!

Thanks! Glad you enjoyed it

I am willing to read a billion contracts than use proprietary bs

I really share with you that passion for OSS :)

like wise brotherTobias C. H.

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!

Excited to write on Hashnode :)

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.

Glad you found it valuable 🙏

I totally agree. The nuances run deep. To establish OSS Compliance is a very complex topic.

Nice article - thx for sharing 🙏

Search Hashnode

The Price You Pay As A Developer For Using Open Source Software - A Tech Lawyers View

Responses11