An organization is considering changing the license of an OSS repo on GitHub. For the purposes of this question, assume that organization has the legal rights to change the license.
It is currently licensed under MPL 2.0, and we need the extra freedom of Apache 2.0.
One proposal is to dual license the code (assuming all contributors agree) as "MPL 2 || Apache 2.0".
I have suggested simply relicensing as Apache 2.0 and dropping MPL 2
I see no value in the proposed dual license, as I would expect most people to opt for the Apache license terms.
Can anyone see an advantage to dual licensing MPL/Apache vs simply relicensing?