Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Then after a period of time, typically 3-4 years, but not more than 5 years, the restrictions lapse, and the source code automatically converts to an Open Source license, in our case Apache 2.0.

I’m not familiar with this type of license. Any idea how/when this time frame is decided? Is it 3-5 years from software release?

I guess I’m confused by the use of “automatically converts” with a vague timeline. If it’s automatic why isn’t the time of “automatic” conversion more definitively known? What’s the event that triggers the change?



Good explanation here: https://perens.com/2017/02/14/bsl-1-1/

It’s from the day that the code is released under the license and the four years is the max under BSL (so that people know roughly what the “worst case scenario” it a BSL licensed software would be) but can be specified to be shorter by the one releasing code under it.


https://mariadb.com/bsl-faq-mariadb/

An individual instance of license will say "the covered code is usable under Foo license from Year-Month-Day"


Not sure if it's still the case but Ghostscript is or was like this - a licenseable current version possibly with extra commercially relevant features (e.g. PCL) plus an open source older version.

Edit: https://artifex.com/licensing/commercial/ notably this lets you avoid concerns about integrating GPL with your commercial offering.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: