There is some disagreement over what exactly is "a work based on the Program", so those companies might simply use a different license and hope to win when and if they get sued by the Wordpress Foundation. Another possibility is to add some license key mechanism to the derived work and hope that most users won't bother hacking around it or getting it from someone who did. Another option is to sell a service contract together with the software.
The GPL only says that you have to give the full rights over the sourcecode to everyone whom you gave a copy of the software. That does not include people who just happen to have access to a server it's stored on. It might include people who work on the software itself (but I don't think so). In any case, most employment contracts would prohibit this anyway.
No. This is in fact the business model of many OSS-based companies, e.g. Github.
There is some disagreement over what exactly is "a work based on the Program", so those companies might simply use a different license and hope to win when and if they get sued by the Wordpress Foundation. Another possibility is to add some license key mechanism to the derived work and hope that most users won't bother hacking around it or getting it from someone who did. Another option is to sell a service contract together with the software.
The GPL only says that you have to give the full rights over the sourcecode to everyone whom you gave a copy of the software.
No. This is in fact the business model of many OSS-based companies, e.g. Github.
There is some disagreement over what exactly is "a work based on the Program", so those companies might simply use a different license and hope to win when and if they get sued by the Wordpress Foundation. Another possibility is to add some license key mechanism to the derived work and hope that most users won't bother hacking around it or getting it from someone who did. Another option is to sell a service contract together with the software.
The GPL only says that you have to give the full rights over the sourcecode to everyone whom you gave a copy of the software. That does not include people who just happen to have access to a server it's stored on. It might include people who work on the software itself (but I don't think so). In any case, most employment contracts would prohibit this anyway.
No. This is in fact the business model of many OSS-based companies, e.g. Github.
There is some disagreement over what exactly is "a work based on the Program", so those companies might simply use a different license and hope to win when and if they get sued by the Wordpress Foundation. Another possibility is to add some license key mechanism to the derived work and hope that most users won't bother hacking around it or getting it from someone who did. Another option is to sell a service contract together with the software.
The GPL only says that you have to give the full rights over the sourcecode to everyone whom you gave a copy of the software.
No. This is in fact the business model of many OSS-based companies, e.g. Github.