The discussion also centered on some issues regarding open standards and how open is open enough for cloud computing? It may depend on who you ask, but I tend to think that the flexibility, interoperability and portability advantages of open source software will dictate its continued use and true openness in the cloud.

However, this is not always the case. When we consider openness in the mobile market, we see that while open source software is going into more and more smartphones and mobile devices, by the time it gets into the product and into the hands of consumers, it ends up closed. This is not necessarily a violation of open source license, either in rule or in spirit, but rather the use, incorporation and reliance on open source alongside proprietary products, strategies and companies, typically under a permissive license. Much of it also has to do with the need, both perceived and real, for control of code in these devices among hardware, software, wireless carrier and other players with a stake.

Another interesting perspective of what open source means, or doesn’t mean, in terms of cloud computing, standards and interoperability comes from the Xen community’s Simon Crosby of Citrix.

One of the most interesting things to watch when considering whether cloud computing gives back to open source is the AGPLv3 license, which is viewed in different ways as both a burden and a boon to network-based, distributed development by various parties. We continue to see vendors, such as mobile software player Funambol, as strong supporters of AGPL while others, such as Google, continue their resistence to it.

The AGPL also came up in the Linux Foundation Collaboration summit panel again, and while I don’t think the license currently serves as the answer to whether cloud computing gives back to open source, we do see some benefits to open source from cloud computing, both in terms of code, projects and communities and the commercial vendors leveraging open source software. In terms of code, large users of open source software projects, such Linux, MySQL, Hadoop, Cassandra, help to raise the profile and credibility of open source. Whether corporations or university campuses, these large users can also be among the most active community participants — driving features and shaking out bugs, and most prolific code contributors — creating features and extensions and enlarging the ecosystem. In terms of commercial open source vendors, cloud computing can also mitigate the challenges of balancing and differentiating free, community versions and separate, paid versions. If the vendor is able to offer support, services or even extensions with the cloud version of its software, it is easily separated from a free, community version that may be available for free, but not from the cloud.

Of course, there is more that cloud computing can do for open source and there is much more that has to be done to ensure true openness in cloud computing, particularly when some existing and emerging defacto standards are anything but open, but for all that open source is to cloud computing, cloud computing seems to be returning the favor to some degree already.

I believe the emerging trend away from GPL and toward more permissive, mixable licenses such as LGPL or Apache reflects the broadening out of open source software not only throughout the enterprise IT software stack, but also throughout uses beyond individual applications, frameworks and systems. More and more open source software vendors are pursuing opportunities in embedded use or OEM deals whereby open source software often must sit alongside or even inside of proprietary code and products. Similar to what we’ve seen in the mobile space — where open source software and development are more prominent than ever, but end products with accessible code are not — open source is broadening out, but it is doing so in many cases by integrating with proprietary code.

We also see some debate about the community and commercial ups and downs of GPL as organizations contemplate the balance of the two and the best way to achieve commercial success with open source software. As Matt highlights, we are seeing a choice of non-GPL licensing in order to more effectively foster community and third-party involvement, but we also continue to see GPL as a top choice to similarly build community.

While the debate about community versus commercial benefit may not necessarily be prompting movement away from GPL, I believe another recent action may indeed do so. The latest series of GPL lawsuits are aimed at raising awareness, profile and legitimacy for open source software. While those bringing the suits — primarily the Software Freedom Law Center — have exhibited a reasonable approach and settled with past lawsuit targets, these suits and publicity may still serve to steer organizations making the choice to other licenses, including the LGPL, BSD, Apache and the Eclipse Public License.

Another factor is the GPL thumping that took place during the SaveMySQL campaign as the European Commission contemplated Oracle’s proposed (and now closed) acquisition of Sun Microsystems and the open source MySQL. I voiced my concern that the SaveMySQL campaign might jeopardize or de-value open source software projects and pieces in M&A, but I believe I’m actually in agreement with SaveMySQL leader Monty Widenius that the deal and process may end up tarnishing the GPL and its reputation in the enterprise.

As stated above, much of the movement we’re seeing away from the GPL has to do with the desire and opportunity to place open source software alongside, within, on top of or otherwise with proprietary software. Non-GPL open source licenses are also more flexible in terms of integrating and bundling with other open source software licensed under other, non-GPL licenses.

We anticipated this fade of GPL as covered in our report, The Myth of Open Source License Proliferation. Given its clout, durability and continued popularity in commercial open source (and with help from continued growth of GPL-licensed Linux) we believe the GPL will endure as a top open source license. However, given their flexibility and the ability to combine with other code, we see a number of other challengers — Apache, BSD, EPL and LGPL — rising while GPL dominance wanes. We’re also watching to see whether the AGPLv3 for networked software will provide new life for GPL-style licensing and community building in emerging virtualized, SaaS and cloud computing environments.