"I understand that I retain copyright ownership in this contribution and I am granting the project a copyright license to use, modify and distribute my contribution. The project may relicense my contribution under other OSI-approved licenses."
"In some cases the project may need to relicense your contribution under other OSI-approved open source licenses in order to maintain the Apache-based licensing. For example, if your contribution is affected by GPL v2 code, the project may dual-license your code under both Apache 2.0 and GPL v2 or LGPLv2.1. This satisfies the GPL requirements, while still allowing other users to make use of the code under Apache."
This seems totally reasonable to me. Note that BSD-style licenses are *not* OSI approved. Having a relatively unbiased 3rd party organization determine acceptable license choices seems like a reasonable approach.
The alternative of trying to keep track of every contributor so that permission can be asked when needed... seems like an administrative nightmare. I know some projects have done that, but I'd rather allow OSI to by my proxy in approving licenses than cause somebody to burn so much time on getting consensus of every individual contributor.