1

We've created a project where the bulk of it (70%) is proprietary code. The remaining is code that is public under MIT license. Can we still publish our codebase under a BSL (Business Source License) license?

3
  • 4
    What do you mean with 'BSL', is that Boost Software License or is it Business Source License? And how is the MIT-licensed code used in your project (directly copied, linked, as a dependency, ...)? Jan 20 at 7:16
  • @Martin_in_AUT FWIW, the bsl applied to the question refers to Boost Software License.
    – Mureinik
    Jan 20 at 11:19
  • 1
    You cannot change the license of the existing code, no matter if it is only 1% of your project code. However, in all likelihood, the MIT license is "compatible" with the BSL. Why? Because, the MIT license is a permissive license. It's hard to imagine a different license that would make it impossible to also comply with the MIT license for the portions of MIT code that you used in your project.
    – Brandin
    Jan 20 at 12:08

1 Answer 1

0

You can basically do whatever you want with the MIT-licensed code as long as you identify the code and the author properly as required by the MIT license.

The Business Source License can be considered as a proprietary license (source-available license) in the first years, until at the 4th anniversary the 'Change License' comes in place, which is usually GPL.

Copyright © yyyy,
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Source: MIT License

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.