Showing entries 1 to 3
Displaying posts with tag: andrew lampitt (reset)
What is open core licensing (and what isn’t) UPDATED

This is an updated version of a post that was originally published in July 2009. It has been updated in response to ongoing confusion about open core licensing.

There has been a significant amount of interest in the open core licensing strategy since Andrew Lampitt articulated it and its benefits for combining open source and closed source licensing.

There remains considerable confusion about exactly what the open core licensing strategy is, however, which is strange since the term arrived fully packaged with a specific definition, courtesy of Andrew. Recently I have begun to wonder whether many of the people that use the term open core regularly have even read Andrew’s …

[Read more]
On the importance of copyright assignment

Some weeks ago Luke Kaines stated his observation that “requiring copyright attribution is a greater sin than providing commercial add-ons”.

His perspective was based on the theory that requiring copyright assignment restricts the developer community, a theory that was apparently repeated by Dave Neary during the recent OSBC event (I missed that session due to our CAOS client lunch).

Daniel Chalef of KnowledgeTree provided some evidence of Dave’s perspective and also the contrary view that the assignment of copyright is critical not just for vendor-dominated projects but also for community projects such as The Mozilla Foundation, The …

[Read more]
Andrew Lampitt defines Open-Core Licensing

JasperSoft’s business development director Andrew Lampitt has kicked off his new blog with an interesting post related to business models used by open source-related vendors.

In it he attempts to define the approach utilized by the likes of JasperSoft and SugarCRM, which offer open source products with core functionality, as well as commercial extensions. The approach is a twist on the dual licensing approach made famous by MySQL* where the vendor, as copyright holder, makes the code available under both the GNU GPL and a commercial license for customers that would rather avoid the GPL.

The approach taken by JasperSoft et al is not to segment by user base but by features. As Andrew explains, “the commercial license is a super-set of the open source product, i.e., it offers premium product features that you will not see in …

[Read more]
Showing entries 1 to 3