Once a file has been distributed under both the (L)GPL and the MPL, recipients of that file can later distribute it solely under the terms of the (L)GPL, in accordance with the terms of that license. If a project wishes to do this, and not to allow others to use their version of this file under the MPL, the project can indicate its decision by deleting the MPL headers described in Exhibit A of the license and replacing them with the standard notice recommended by the (L)GPL. Copyright notices indicating authorship of the file should be retained.
... So you combine with GPL code, and then, say "I don't want to use the MPL."
Is this really so complicated? All updates to be done in the future are licensed under the GPL.
The only firm that benefits from the MPL here is Hashicorp, which is the company that the fork is being done against. Fork it and be done... It isn't like the MPL code can integrate with the BSL code.
Once a file has been distributed under both the (L)GPL and the MPL, recipients of that file can later distribute it solely under the terms of the (L)GPL, in accordance with the terms of that license. If a project wishes to do this, and not to allow others to use their version of this file under the MPL, the project can indicate its decision by deleting the MPL headers described in Exhibit A of the license and replacing them with the standard notice recommended by the (L)GPL. Copyright notices indicating authorship of the file should be retained.
... So you combine with GPL code, and then, say "I don't want to use the MPL."
Is this really so complicated? All updates to be done in the future are licensed under the GPL.
The only firm that benefits from the MPL here is Hashicorp, which is the company that the fork is being done against. Fork it and be done... It isn't like the MPL code can integrate with the BSL code.