I'm the author of a small-fish webmail package called IlohaMail, and I've been wondering if there were licenses like GPL that applied better to PHP-based applications that don't have binary distributions. Personally, I think deployment of web-apps is more or less analogous to distributing binaries (they're both acts of making software available for use by others), however, under the GPL, we're not offered the same kind of protection.

For example, my app has a link to the project website in the login page, and it's the only place where there's any branding in the whole interface. One thing I've noticed is that some organizations deploy my software without the link that goes back to the project website, which I think is a lot like redistributing software under a different brand (after all, for all the users know, what they're using isn't IlohaMail, but a software their organization wrote). Under the GPL, a vendor who redistributes a rebranded product is required to make the altered source code available, however, an organization that deploys modified web-apps is not required to make the source code available.

Furthermore, I think there are actually real damages to us because of this. If organizations that deploy modified versions of web-apps were required to make their source code available to the public, I think there's a good chance that some of them would prefer to pay for an alternative license that exhempts them from this requirement. In other words, because PHP-based scripts really aren't covered by the GPL, we're losing a potential revenue source.

What do others think about this? Is it just me, or does it concern anyone else? Is there a better license out there, or perhaps one could be created?

    If by "like GPL" you're suggesting an Open Source license, then there are a selection listed here.

      Well, you could go to http://www.opensource.org and take a look at the licenses listed there.

      For programs or scripts that are interpreted, the machine-readable source code is effectively the executable.

      Is it certain then, that the GPL doesnt cover PHP scripts?

      I believe it still does.

        Originally posted by laserlight
        Is it certain then, that the GPL doesnt cover PHP scripts?

        It's not that none of it applies, but a lot of it doesn't. If I understand correctly, the difference between GPL and a BSD style license are mainly in re-distribution of binaries, which doesn't apply to PHP scripts.

        My point is, I believe deployment of PHP scripts to be identical to distribution of compiled software, and I think a modified license is required that covers deployment.

          If organizations that deploy modified versions of web-apps were required to make their source code available to the public, I think there's a good chance that some of them would prefer to pay for an alternative license that exhempts them from this requirement. In other words, because PHP-based scripts really aren't covered by the GPL, we're losing a potential revenue source.

          If that is your worry, why not just use a proprietary license, say your own license?

          Actually, since branding is your concern, not the potential for more rapid development of your scripts, I think that you should simply make it proprietary.

          / I have no legal training, so dont take my word for professional consultation /

          I think the crux of the matter is this:
          Assuming they have modified your script, your clients are required by the GPL to "cause the modified files to carry prominent notices stating that (they) changed the files and the date of any change", and "cause any work that (they) distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of (the GPL)".
          This means that if they want to sell the script, or make it available for download in some form, it would have your "brand", or rather copyright notice, on it.

          The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program).

          On the other hand, those who use the script (in the sense that they are served files from the webserver that have been parsed by PHP due to your script) have not received a copy of the script, modified or in original form. What they have received is the output from the script. As such, your clients are not required to distribute the source code to them. They have the option, but no obligation.

            I think I found what I was looking for in the Open Software License. It has a stipulation that says deployment should be considered equivalent to distribution for software inteded for use over a computer network (which I think is that case with PHP scripts).

            Originally posted by laserlight
            On the other hand, those who use the script (in the sense that they are served files from the webserver that have been parsed by PHP due to your script) have not received a copy of the script, modified or in original form. What they have received is the output from the script.

            People have pointed that out to me, but I don't follow the logic. People who deploy my software aren't the users. How could untarring a package on a hard drive (which the installation process is) be considered "using"? It's the end users who interact with the script who are using the code I wrote. They're the ones that are making requests that cause the servers to actually execute the code. All the original admin did was to make the code available for use by others, which sounds a lot like distribution to me.

              Question: Did you specifically release your php scripts under the GPL? If so then the GPL applies plain and simple.

              However, I got the impression that you might think that php scripts are somehow automatically covered under GPL. This is certainly not the case.

                Originally posted by ahundiak
                Question: Did you specifically release your php scripts under the GPL? If so then the GPL applies plain and simple.

                However, I got the impression that you might think that php scripts are somehow automatically covered under GPL. This is certainly not the case.

                I did release my package under GPL. What I'm saying that all the clauses that apply to distribution of binaries don't apply to PHP-scripts, which means a lot of it doesn't really apply.

                Or let me put it this way. The GPL wasn't written with scripts in mind, and it assumes that all software have binary and source forms.

                  Write a Reply...