Earlier quoted context omitted.
> 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. The treaty specifically states a party cannot compel the owner to reveal the source code. Arguably someone violating the GPL or similar license is not the actual owner of the code.
I'm not sure why you believe this. I quoted the actual text: "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." It does not say no party can compel an owner, it says no party can compel access to the source code owned…
TPP banning requirements to transfer or access to source code of software
111–120 of 162 posts
Re: TPP banning requirements to transfer or access to source code of software
#112Re: TPP banning requirements to transfer or access to source code of software
#113Re: TPP banning requirements to transfer or access to source code of software
#114Earlier quoted context omitted.
Expounding further - what government agency has the time or money to actually sift through mountains of source code? From a pure financial standpoint, there's no possible way that it isn't cheaper to just measure real emissions than attempt some kind of software analysis for every version of every vehicle on the market. Furthermore, an agency inspecting source code has absolutely no way to tell whether or not that th…
Just as a counterpoint: the Nevada Gaming Commission has plenty of time and money to sift through the source code of every gaming device that gets deployed in NV.
Similar restrictions would severely cripple innovation in cars. Just consider Tesla's autopilot software.
Re: TPP banning requirements to transfer or access to source code of software
#115Earlier quoted context omitted.
Just to agree with this point and elaborate: when the text uses the word "party" it refers to a nation signing the treaty, and not people. So when it says "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," Party refers to…
In a State where the GPL is enforceable would it be a violation of the TPP to require that a foreign company comply with the GPL and release the source code? I think that's the $1,000,000 question.
Re: TPP banning requirements to transfer or access to source code of software
#116Earlier quoted context omitted.
The TPP is actually supposed to exclude China and create a competing trade bloc. It was even called the "everybody but China deal" by some people. All part of Obama's "pivot to Asia"... supposedly. However, given the contents of the treaty, I don't think this exclusion is something that really bothers China. China wanted in on the WTO bad. Real bad. China doesn't really care about the TPP.
To quote Obama: > The TPP means that America will write the rules of the road in the 21st century. http://in.reuters.com/article/2015/11/05/trade-tpp-idINKCN0S... It very much sounds like they’re treating the rest of the world as colonies.
Re: TPP banning requirements to transfer or access to source code of software
#117Earlier quoted context omitted.
Playing the devil's advocate here, but you shouldn't need access to a car's source code to measure its emissions. The test is broken, not the software.
Expounding further - what government agency has the time or money to actually sift through mountains of source code? From a pure financial standpoint, there's no possible way that it isn't cheaper to just measure real emissions than attempt some kind of software analysis for every version of every vehicle on the market. Furthermore, an agency inspecting source code has absolutely no way to tell whether or not that th…
It's actually the same problem: an extremely complex object is being constructed, a critical failure within which could leave many people nearby injured or dead.
The solution is actually somewhat ingenious: License a small group of people to go analyze such things, let them organize themselves independently, but require them to sign off on the design. It turns out that with their license and livelihood on the line, enough people aren't willing to sign off on terrible, shoddy crap that the system mostly works.
Perhaps it's time that software grew up and became something closer to a real engineering discipline?
Re: TPP banning requirements to transfer or access to source code of software
#118I can only think of TPP/TIPP as Protectionism... how can this go well?
Re: TPP banning requirements to transfer or access to source code of software
#119These are rules for States. It has no bearing whatsoever on the GPL. This prevents a country from forcing somebody like Microsoft or Apple to give up their source code for "inspection" in order to access their market. It also helps to prevent States from demanding and acquiring encryption or other private keys (there's a separate section that also explicitly forbids mandating backdoors be added). Not everything in th…
Re: TPP banning requirements to transfer or access to source code of software
#120Would this prevent us from requiring VW make available it's source code? Not a lawyer.
Why would you want VW to make available its source code?