| So, as an actual lawyer i actually think i disagree with you in practice. Imagine for a second that the US gets tough on GPL violators, and says "well, if you want to sell android devices in the US, you have to produce the GPL source code". Or something even simpler, along the lines of "products marketed in the US must comply with all licensing obligations of software that it contains". This one actually happens behind the scenes sometimes right now, though you don't see it. I believe they would not be allowed to do that under this provision. It clearly falls into:"1. No Party shall require the transfer of, or access to, source code of software owned by a person of another Party, as a condition for the import, distribution, sale or use of such software, or of products containing such software, in its territory." 3 is no exception: "3. Nothing in this Article shall preclude:
(a) the inclusion or implementation of terms and conditions related to the provision of source code in commercially negotiated contracts;" The GPL and other open source licenses are arguably not commercially negotiated contracts. So yeah, it doesn't stop private citizens or parties from doing whatever they want.
It may stop you from being able to create laws and enforce them at import/export time around actually complying with OSS licenses. Which is really not great, since it in practice means free reign. You will never get state supported companies in their own countries to comply with licenses. Generally, your only course of action is to try to enforce elsewhere, or ban import/export. Here, in the case of the US, you will not be allowed to ban import unless all of that open source software is completely US written. (since the provision limits requiring "source code of software owned by a person of another Party". Of course, what it means by "software owned by a person of another Party" is also up in the air, since most open source software has many copyright owners , so does it mean complete ownership, partial ownership, or what?) |
This is the key issue. It seems like a copyright license to code under GPL would be commercial, in the sense that the parties are exchanging a license for the recipient undertaking the GPL obligations. Whether it's "negotiated" seems like a more difficult question.
One interpretive guide could be to look to the reason for the provision. I suspect the purpose was to allow for source-code escrow agreements in things like enterprise software deals. It would be odd for the enforceability of those provisions to turn on the degree to which the parties "negotiated," so I suspect this will be a low bar.
Rather, I suspect the term "negotiated" is intended to block end-runs around the default rule. Otherwise, governments could obligate copyright holders to burden their code with GPL-like code, e.g., a reg saying you can only provide voting machines if they are based on a modified version of the Linux kernel.
So I think GPL source-code disclosure obligations remain enforceable, absent coercive acts by a government to force parties to undertake those obligations. But this is really speculative.