I wonder if they perhaps would be better off doing something to what Microsoft did with vscode: put the core under an open source license, then create a new product that integrates it under a restricted license with all Microsoft branding and specifics and release that as a product. That way the original Microsoft content is not subject to the open source and the true open source definition can be applied to what is the most important, the core. It wouldn’t require any changes to the open source definition for example. It doesn’t fix all issues raised, but may be a bit of a middle ground? Thoughts?
I wonder if they perhaps would be better off doing something to what Microsoft did with vscode: put the core under an open source license, then create a new product that integrates it under a restricted license with all Microsoft branding and specifics and release that as a product. That way the original Microsoft content is not subject to the open source and the true open source definition can be applied to what is the most important, the core. It wouldn’t require any changes to the open source definition for example. It doesn’t fix all issues raised, but may be a bit of a middle ground? Thoughts?
Or just call it something other than “open source”, like “source available” or something.