Honestly, just quickly looking through the two licenses to answer a simple question... GPLv3 [1].

From a legal perspective, "simpler" documents tend to be less clear, because a lot more of the interpretation will rely on common law jurisprudence [2], and the "common" here doesn't mean "everybody agrees"--it in fact means "every jurisdiction has its own set of rules that may or may not translate directly in other jurisdiction."

> And despite all the claims here, intent is going to matter. When you sue Linus and say the GPL doesn't mean what he and everyone else actually creating this code think it means, then he's going to say, this was our intent. And you are going to have a VERY tall mountain to climb.

Given that a software license is close to a take-it-or-leave-it contract, ambiguous interpretations are generally going to be interpreted in favor of the person who has the take-it-or-leave-it option--which in this case is not going to be Linus and co.

[1] The criteria I used: "how do patents interact with this license." From what I can tell, GPLv2 technically doesn't actually contain a clause where the licensor grants the licensee any and all necessary patents--it instead talks about what happens if the code violates a third party's patent. Admittedly, reading the GPLv2 to not include a patent license grant is somewhat of a malicious reading, but the GPLv3's verbiage here is pretty explicit: "Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version."

[2] I'm limiting my analysis here to US jurisdictions, because that's what I know.