GPL is the new BSD in Web 2.0, and why this matters
The Internet turns open-source licensing on its head. Copyleft is neither copyright nor copyleft anymore in the Web world. It's just copy, because distribution of a service over the Internet doesn't count as distribution in the archaic licensing language that plagues most open-source licenses.
It's a problem that the Free Software Foundation chose to ignore, and then beat on Tim O'Reilly to atone for its own failing. Tim, for his part, thinks that the open-source world is missing the boat, which is chugging along unmindful of antiquated things like software licenses when the real value is in data-centric applications whose value lies in network effects (architecture of participation).
I get this point, and he's probably right in the long run. My question for now, however, is: if the value in Web 2.0 is data, why can't Web 2.0 get over its own software fetish?
For it's not just the open-source crowd amongst non-Web Neanderthals that is stuck on software. It's also the very group that Tim praises for taking the argument to the next level--the Web 2.0 crowd--that insists on the value of its services while locking down the value of its software. Release the code if code no longer matters. Let others build on it. Lock us in through data. Fine. But release our software.
That's all we ask.
We have a long way to go before the world abandons software qua software. We're still muddling through green screens in large enterprises, after all. So software qua software matters and will continue to matter for a long time. In this world, open-source licensing is relevant and powerful.
Open source, however, is losing its grip on the Web because the Web has decided to play by different licensing rules and open source has not bothered to keep up. This is not the Web's fault. It's open source's for fetishing the past, as Tim indicates.
But this doesn't lead me to Tim's conclusion. Instead, it leads me to ask for an upgrade to open-source licenses so as to require the Web world to play by the same rules as the old software world. If you take my software, modify it, and redistribute it, you need to contribute back. It's really very simple.
Given that the Web is powered by data, not software, this shouldn't be a big problem for the Web 2.0 world. Contributing back into the common software fund should be an opportunity, not a problem. So why haven't Google et al. stepped up to the plate to give back their derivative works? Why do they treat the GPL as if it were the BSD license, requiring nothing in return for all the value given to them?
Because they can. Because open-source software licenses are irrelevant in the software-as-a-service world.
But given that they won't release the code, anyway, I guess it also means, as I noted above, that the Web 2.0 world is still essentially a software world after all, or thinks that it is.
Maybe we'll all wake up 20 years from now and laugh about our fetal focus on code. But for now, both Web companies and landlubber companies are still focused on software. While we're thinking about software, everyone should be held to the same open-source licensing rules, to the extent that we're dipping into the same pool of code. This means we need new open-source licenses in the mold of CPAL, Open Software License, etc.
Tim is probably right. Software probably is yesterday's discussion. But while the world continues to behave as if software matters, today, then it's important to live in that world. When all software is open source (and I think it's almost unquestionable that we will at least get to the point that every technology company will have a serious open-source bent to it within the next 10 years), we can focus on data and perhaps a Free Data Foundation (FDF) will spring up to ensure we keep it free.
For now, I just want the software to be open. I'm old-fashioned like that.
Matt Asay is general manager of the Americas and vice president of business development at Alfresco, and has nearly a decade of operational experience with commercial open source and regularly speaks and publishes on open-source business strategy. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.







> requiring nothing in return for all the value given to them?
The GPL *NEVER INSISTED* on "the community" (whatever that is)
getting anything in return.
It doesn't insist that for Web 2.0 software, and it never insisted
that for "normal" software either. You're quite at liberty to take
(for instance) GCC, alter it, and keep your alterations to yourself.
Or you can give your alterations to your friends, and all of you
can keep the changes to yourselves. Time and time again,
people trot out this nonsense about there being some
requirement for changes to be given back to the community, but
it's just not what the GPL is about and there's exactly no
language in the GPL to force such a situation.
The point of the GPL was simply to ensure that software that was
distributed could be altered by its end users and that those
altered versions could then be re-distributed under similar
terms. So, for instance, if your printer's software was GPL'd, and
it had a bug or needed some extra feature, you could fix it and
give the fixed version to anyone you knew who had the same
printer. But you *don't have to* give it away at all if you don't
want; it's your option.
The constant complaining about this only serves to show the
ignorance and hubris of the so-called "Open Source community",
much of which is centred around getting software for free rather
than actually working on it.
If MySpace were to open all of its code, how long do you think it would take before a deep pocket would launch MySpace 2.0, and begin to steal market share. How MySpace presents the data, and how the data is made accesible to the community is their strength. Yes, others can do the same thing (and have) but by having to develop their own software to due it, they are at a disadvantage in terms of time. That is MySpace's advantage by having gotten there first.
http://gplv3.fsf.org/agplv3-dd2.html
How could the Web exist if it wasn't for all the hardware machines and communication infrastructure, running software enabling client/server or P2P services so that my higher level uses actually let me access the data.
It could as easily have been said the print industry is powered by data, but without a huge service industry to enable it, no one is going to see the data.
One of the hardware restrictions noticeable here in Australia, is the up-link speed of the Internet. We have only 2 cables going across the Pacific, controlled by 2 companies who limit the speed we can send our data at an affordable price, such that International Web 2 services are limited in their effectiveness.
Just imagine that situation multiplied by all the other countries relying on the willingness of International cable owners to supply affordable up-link speeds. International Web 2 is not going to be effective for them either.
So I think the power has to be the infrastructure, which also includes the software that enables it.
As long as affordable 2 way communication speeds are low, the world will need resident application software, and because the speeds rely on International cabling, it is going to be a long time before Web 2 takes over.
So certain members of "the OSS community" who gets sulky when someone makes alterations to software where the INTERFACE is publically available do not have a leg to stand on as long as the "open"-license is not an EULA. There is no distribution going on. Well, except for any Javascript elements, but hey, you get the source when you access the page so no problems there either.