Showing posts with label apache licence. Show all posts
Showing posts with label apache licence. Show all posts

28 July 2010

Will Adobe See the Light (of Day)?

The content management company Day Software may not be the world's most famous outfit making money from open source – perhaps a function of the fact that it is located in Basel, hardly known as a hotbed of hackers – but it's certainly an important one, particularly in the Apache part of the open source ecosystem.

On Open Enterprise blog.

27 July 2010

If Oracle Bought Every Open Source Company...

Recently, there was an interesting rumour circulating that Oracle had a war chest of some $70 billion, and was going on an acquisition spree. Despite the huge figure, it had a certain plausibility, because Oracle is a highly successful company with deep pockets and an aggressive management. The rumour was soon denied, but it got me wondering: supposing Oracle decided to spend, if not $70 billion, say $10 billion in an efficient way: how might it do that? And it occurred to me that one rather dramatic use of that money would be to buy up the leading open source companies – all of them.

On Open Enterprise blog.

29 May 2008

Er, Yes, and What About the AGPL?

Here's a post explaining Google's support for just seven open source licences:

The trend around licensing is obvious: GPLv2/GPLv3 represent 42.6% of the projects, and Apache is 25.8%. MIT, BSD, and LGPL are at about 8% each, Artistic at 3.5%, and MPL 1.1 at a mere 2.7%. This follows my own observation about how people license their projects. If they are advocates of Free Software, they will choose GPL; advocates of Open Source will choose Apache (a more modern and thorough permissive license, compared to BSD or MIT). And this is exactly what I recommend to people: choose GPLv3 or Apache v2 based on your personal philosophy.

Well, actually, there's another rather important trend that is conspicuous by its absence: adoption of the Affero GPL. To which Google seems strangely allergic....

26 November 2007

Here We Go Round the (Open) Mulberry Bush

Mulberry started off life as a software project that was really meant to help the author learn more about the internet and internet protocols used for email. However, it became much more than that and garnered support from a small (in internet terms) group of users and institutions many of whom relied on the product as their primary email tool.

Whilst it started as only an IMAP client and only on Mac OS, it has grown to cover not only other email protocols, but also calendaring and scheduling and is available on Mac OS X, Windows and Linux systems.

Not something I use myself, but good to see it going open source, not least because calendaring and scheduling is an area where free software offerings are still rather thin on the ground:

The full code for Mulberry (Mac OS X, Windows and Linux) is now available as open source under an Apache 2 License. Full details available on the wiki.

(Via heise online.)

13 November 2007

Android's Unity in Diversity

By choosing the relatively liberal Apache licence for its Android platform, Google runs the risk of fragmentation - something that the stricter GNU GPL tends to avoid. The company is evidently conscious of this:

a spokesperson for Google told ZDNet.co.uk on Monday that the OHA had foreseen these pitfalls. "All of the partners have signed a non-fragmentation agreement saying they won't modify [the code] in non-compatible ways," said the spokesperson. "That is not to say that a company that is not part of the OHA could not do so."

That's all fine and dandy, but it will interesting to see how it pans out in practice.

31 October 2007

Curling Up with Open Source

One of the heartening signs in the software industry is the continuing flow of donations to the free software commons. The latest to see the light is interesting because it's in a domain where open source code is fairly thin on the ground: Rich Internet Applications.


Curl, Inc. today announced its plans to release a significant body of code for the Curl Rich Internet Application (RIA) platform to the open source community. As the first step in its open source strategy, Curl will broaden its development platform and empower the Curl developer community by establishing a common repository of open source component libraries. As a result, developers will have all of the components required to support rapid development of enterprise-class RIAs. Curl's Open Source projects are provided under the Apache V2.0 License and hosted by SourceForge.

For tools like this, the benefits of open source are clear: people are able to try out your products much more easily, and the code can be freely passed around, growing the size of the user base for practically no cost. Indeed, the power of this kind of viral distribution is so great it's surprising there aren't more such releases. (Via 451 CAOS Theory.)