SYS-CON Media
 Register Now!
Save $200
Register before October 17th to SAVE! ... and also receive a FREE copy of the Best-Selling AJAX Book, a $119 Value!
Untitled Document
2008 East
Platinum Sponsor
Untitled Document
2008 East Gold Sponsors
Untitled Document
2008 East Exhibitors
Untitled Document
2008 East Media Sponsors
Untitled Document
2008 Association Sponsor
SYS-CON Media
2007 West Sponsors
Goingtomeet.com Conference Directory
SYS-CON Media
2007 East Sponsors
Untitled Document
2008 SYS-CON Events

Can't Miss RSS Feed
Subscribe to the AJAXWorld.com RSS Feed & Get All The Conference News As It Happens!

2008: Decision Year for RIAs - October 20-22, 2008 San Jose


Making Commercial Open Source Software
Delight customers and profit

I recently blogged about making open source software, and the high level steps for how to think about the process. We started with the need for software to seed the discussion, the need for clear motivation as to why to publish as open source software, and then the structural requirements to build a community (license choice, collaboration platform or forge, and governance considerations). Contributions are the life blood of any community, so lastly we talked about the need to build an onramp to encourage users that will hopefully become contributors, and the additional onramp needed to make it easy to contribute.

Rory MacDonald (@technocreative) challenged in the comments that there are substantial commercial motivations for a company to develop open source projects that go beyond a desire for collaboration, and provided a number of examples.  I completely agree, and I'd like to build on these ideas.

Why as a company (rather than as an individual) would you want to "make" open source?

Again we have two types of making to consider:

  • A company can contribute to an open source project that already exists.
  • A company can create a new open source project (either by publishing existing software or creating new).

If we consider a company making contributions to an "outside" project then we should do so from the perspective that this is an advanced case of collaboration where the open source project is being used in a product or service the company offers to customers for sale. Think Red Hat and using Linux to deliver Red Hat Advanced Server.  Otherwise, contributing to a project that is used strictly in-house pretty much looks like the discussion in the previous post -- it's about engineering economics and shared innovation and living on a fork gets expensive over time unless it can be balanced against the costs of maintaining a business advantage through secrecy (e.g. the way Google used Linux in the early days).

Participating in an external open source licensed project is a case of expanding traditional corporate thinking of "build" versus "buy" to include "borrow" and "share".  It's about time-to-solution if a company uses the project in-house and about time-to-market if the project is used to develop a product or provide a service to customers for sale.  One needs to remember as a company using open source licensed software in a product or service that the company exists to solve a problem and create a marketplace around the solution.  This is all about Levitt's observations about solving customer problems ("needing a 1/4 inch hole") over selling products ("the drill").  Red Hat wasn't "selling a Linux distro" but rather providing a professionally maintained and supported low cost PC-based server replacement for expensive proprietary UNIX systems on expensive proprietary hardware.

The interesting problems when using an externally developed open source project as a company are in understanding the flow of ownership of the intellectual property with respect to the software.  There are a couple of predominant concerns:

  • What legal risks are possible that need to be managed against a company's risk profile.  This should not be taken lightly.  Companies are more interesting legal targets than individuals.  Even if a company is using the software internally rather than in a product or service, there is still a risk profile to consider.  It's not that the risk is greater than purchasing a proprietary software solution from a vendor but one needs to feel comfortable that the externally run open source licensed project has appropriate IP management safeguards in place.
  • What intellectual property is being contributed to whom. Again, companies are often uncomfortable contributing their own hard won R&D investment to others (even partners) without crisply understanding the return.

As a company each of these legal concerns comes with additional legal responsibilities.  Open source software foundations provide solutions to these problems by providing neutral non-profit space in which companies can collaborate together, and backing the space with proper IP management practices. The Apache Software Foundation, the Eclipse Foundation, the Linux Foundation (né OSDL) and the Outercurve Foundation were all created to manage the risk around these software IP problems.

The discussion becomes interesting when a company considers creating its own open source licensed projects.  Rory's examples speak to benefits.  Let's start with the motivation again.  People are often very good at understanding their "gut" motivation for doing something.  The larger a company becomes the more thought and documentation needs to go into such decisions, especially once a company goes public.

If the project to be published under an open source license is "infrastructure" for the company, then the motivations are all based on shared innovation and distributed engineering economics. This is what we see with data centre-centric projects created by the likes of Amazon, Yahoo, Google, Twitter, Netflix, or the Facebook Open Hardware Initiative.  The company starting the project is sharing work in which they have invested time and energy in the hopes that others will join the project, use it in new ways thereby hardening the software and contributing at the very least bug reports, but also hopefully extending and evolving it.

When this is the motivation, all the discussion in the previous article comes into play around making open source.  Essentially, one needs:

  • Useful software as a base around which to build a community.
  • Motivation to share, credible expertise in the problem to be solved, and an understanding of the software structure to anchor the open source community.
  • The project needs to have the structural issues of license, forge, and governance decided, even if governance becomes an evolving discussion in a growing community.
  • The community needs to build a solid onramp to encourage use, and a second onramp for users to become contributors.  The sooner this happens in a project's life, the faster it can build a community.

The additional consideration to encourage corporate participation and contribution needs to be software ownership, legal risk, and IP management around the contributions.  This is where considering using existing open source software foundations comes into play.  Corporations are far more likely to contribute their software to a neutral non-profit for mutual benefit.

But as Rory points out, there are business motivations for creating open source projects as well.  A company's executives want to "increase business" but does that mean increase leads in the sales pipeline?  Or build a community of evangelists that firmly anchor the company's products and services while providing proof points and expertise to potential new leads.

Using free and open source software in a commercial setting doesn't change the nature of running a business. One needs to clearly understand that customers buy solutions to problems and what problem the company is solving. Geoffrey Moore demonstrated some time ago that companies offering the best "whole" solution win, i.e. a core product or service and all its complementing products and services around a more complete ecosystem. This has a lot to do with shaping a "complete" solution to account for the subtle differences that customers perceive they have around the problem space.  Successful companies essentially offer a portfolio of products and services and as long as the sum of the costs of delivering the portfolio is less than the sum of the revenues (spend less than you earn), the company is profitable. Taking a portfolio approach allows a company to play with their pricing models and differentiate themselves for customers against similar competitors.

Open source software can play a number of roles in such a portfolio approach.  A company can:

  • Sell support, upgrades, customization, training and "stability" to a product that is otherwise provided as an open source project. The best example is probably Red Hat "selling Linux" when it doesn't own the core IP.  The "product" isn't the software.  JBoss tried several of these approaches before their Red Hat acquisition.
  • Sell a core product (licensed as proprietary or open source) while encouraging an ecosystem of complements from partners around open source licensed projects.
  • Allow customers to try the "product" in its simplest form as a set of unsupported unwarranted binaries for "free", i.e. downloading the community/developer editions, to self-qualify themselves in the sales pipeline.  (This was very much how MySQL built both its businesses.)

These items all speak to the delivery of the product and the pipeline.  A company can also develop a community of users of the open source project that act as a source of expertise and experience for potential customers.

A community of developers and users is an essential piece of the whole solution. Some companies develop large successful communities without ever publishing their product software. IBM, Microsoft, Oracle, and SAP have all done this to great success. This is why community building is so important for your company and why community development is an essential ingredient in your solution pitch to customers. User and developer communities (regardless of open source):

  • Anchor customers both in an engaged relationship as well as from a technology perspective.
  • Create knowledge, expertise and experience necessary to provide a complete solution for the technology pitch to the customer.  These proof points are invaluable when potential customers are self-qualifying themselves and testing the strength of a solution's community.
  • Create advocates and evangelists to spread awareness about a solution.
  • Create enormous inertia in the status quo around a technology.

These variations all rely on remembering a couple of related "rules":

  • An open source licensed project is not a complete product solution for most people.
  • Project community users and developers are not solution customers.  Community members tend to have time to spend on a solution but no money while customers have money and are looking for time-to-solution and certain guarantees.

Creating an open source project can be as simple as publishing software using an open source license, and this gives customers insight into the workings of a solution.  But if you ignore community building activities, you're losing all the benefits that come from an engaged base of customers and users of your technology.

Clearly understanding the benefits of using open source licensed software for delivering time-to-market, providing a rich complement ecosystem, and enabling communities to anchor the ecosystem in place allows a company to set its motivations correctly.  One can discuss the investment in effort as a way to understand the motivation.  We can contrast the publication of the software as open source and the effort required to develop the community against the evolution of the commercial product in terms of investment and value returned.

This also allows a company to understand the problems with half measures.  Companies sometimes treat "open source" licensing as marketing pixie dust, instead of rightly understanding its place in the solution portfolio or the need to build genuine community that will lead to solving customer problems, and ultimately delighting said customers which can be measured in profitability.  They try to limit access and only approach community half-heartedly because ultimately they're unsure of the benefits.  Fully appreciating the benefits allows a company to fully engage with both community and customers to solve problems.

Rory also mentioned the use of open source projects to undermine a competitor's margins.  This is a level of competitive play by large complex companies in well-established markets that warrants its own blog post.  We save it for another day, and instead stay focused on the commercial positives of making open source software.

About Stephen Walli
Stephen Walli has worked in the IT industry since 1980 as both customer and vendor. He is presently the technical director for the Outercurve Foundation.

Prior to this, he consulted on software business development and open source strategy, often working with partners like Initmarketing and InteropSystems. He organized the agenda, speakers and sponsors for the inaugural Beijing Open Source Software Forum as part of the 2007 Software Innovation Summit in Beijing. The development of the Chinese software market is an area of deep interest for him. He is a board director at eBox, and an advisor at Bitrock, Continuent, Ohloh (acquired by SourceForge in 2009), and TargetSource (each of which represents unique opportunities in the FOSS world). He was also the open-source-strategist-in-residence for Open Tuesday in Finland.

Stephen was Vice-president, Open Source Development Strategy at Optaros, Inc. through its initial 19 months. Prior to that he was a business development manager in the Windows Platform team at Microsoft working on community development, standards, and intellectual property concerns.

Latest AJAXWorld RIA Stories
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicat...
In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even cod...
The question before companies today is not whether to become intelligent, it’s a question of how and how fast. The key is to adopt and deploy an intelligent application strategy while simultaneously preparing to scale that intelligence. In her session at 21st Cloud Expo, Sangeeta...
Bert Loomis was a visionary. This general session will highlight how Bert Loomis and people like him inspire us to build great things with small inventions. In their general session at 19th Cloud Expo, Harold Hannon, Architect at IBM Bluemix, and Michael O'Neill, Strategic Busin...
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the ...
Untitled Document

Call 201 802-3020 or Click Here to Save $200!

Register Today and
Save $200

Your registrations includes: Golden Pass Delegates will receive full conference access on October 20-22, 2008 including: Lunch and Coffee Breaks, Collectible Bag and Archives of all sessions on DVD. Includes access to all Conference Sessions including the Technical Sessions, Exhibits, Keynotes, Vendor Technology Presentations, and Power Panels.


Sponsorship Opportunities

AJAXWorld offers the undisputed best platform to position your company as a leading vendor in the fast-emerging marketplace for AJAX and Enterprise Web 2.0.


Please call
(201)802-3020


Who Should Attend?

 CTOs & VPs of Engineering
 Directors of Technology
 Sr. User Interface Architects
 Front-End Engineers
 VCs & Industry Analysts
 Directors of Business Development
 Software Engineers
 Senior Architects
 Application Programmers & Software Developers
 Project Managers
 Web Programmers & Designers
 Companies & Organizations that need to stay in
  front of the latest Web technology

AJAXWorld Security Bootcamp

Introducing at AJAXWorld RIA Conference 2008 West the world's first-ever full, one-day immersive "AJAX Security Bootcamp" - led by one of the world's foremost AJAX security experts and teachers, HP's Billy Hoffman.

View the full one-day schedule



AJAXWorld 2008 West - Tracks

Track 01: Enterprise RIAs
Track 02: Frameworks & Toolkits
Track 03: Web 2.0 & Mashups
Track 04: Hot Topics
Track 05: The Future of the Web
Track 06: iPhone Developer Summit



Brought To You By:

AJAXWorld Magazine is the pre-eminent independent vendor-neutral resource for the fastest growing new segment of the software business: entirely Web-based applications and experiences.

Download the Latest Issue!

AJAXWorld Webcasts



SYS-CON EVENTS


AJAXWorld Keynotes & Power Panels

2008 SYS-CON TV Keynotes: Can We Fix the Web? By Douglas Crockford - by Douglas Crockford
2008 SYS-CON TV Keynotes: 2008: The Year of the RIA - by Anthony Franco
2008 SYS-CON TV Power Panel: The Business Value of RIAs
2008 SYS-CON TV Power Panel: What Lies Beyond AJAX
2007 SYS-CON TV Keynotes: Why Web 2.0 for the Enterprise Is Far More Than Just a Facelift - by Ted Farrell
2007 SYS-CON TV Keynotes: Fueling the Next Generation Web: A Peek Behind the Green Curtain - by Bob Brewin
2007 SYS-CON TV Keynotes: AJAX in the Balance - by Joe Stagner

AJAXWorld Sessions on SYS-CON.TV

· Bill Scott - Yahoo! UI Library
· David Heinemeier Hansson - AJAX on Rails
· Jesse James Garrett - Elements of User Experience
· Dion Hinchcliffe - Real World AJAX
· Eric Miraglia - Open Source AJAX Development
· Paul Rademacher - Mashing Up Your Web Application
· Adam Sah - Google Gadgets
· Doug Crockford - An Introduction to JavaScript
· David Linthicum - Enterprise Web 2.0
· Patrick Grady - The Imagination & Experience Web

AJAXWorld...All The AJAX Rock Stars in One Spot!


Past Events Archive

SOAWorld Conference & Expo 2008 East
soa2008east.sys-con.com
Virtualization Conference & Expo 2008 East
virt2008east.sys-con.com
AJAXWorld 2008 Conference & Expo East
ajaxmar08.sys-con.com
SOAWorld Conference & Expo 2007 West
www.soaworld2007.com
Virtualization Conference & Expo 2007 West
virt2007west.sys-con.com
AJAXWorld 2007 Conference & Expo West
ajaxoct07.sys-con.com
SOAWorld Conference & Expo 2007 East
soa2007east.sys-con.com
Virtualization Conference & Expo 2007 East
virt2007east.sys-con.com
AJAXWorld 2007 Conference & Expo East
ajaxmarch07.sys-con.com
Other SYS-CON Events
events.sys-con.com

Join Over 10,000 Early AJAX Adopters
Who Have Attended AJAXWorld
• A&R Edelman
• Academic Enterprise
• Accoona Corp [2 delegates]
• Acxiom
• Adams Capital Management
• Adaptive Edge
• Adaptive Path
• Adobe Systems Incorporated [21 delegates]
• Adobe Systems Romania
• Ajax13
• All Risks, Ltd.
• alliance
• Alliance For Community Care
• AlphaDetail Inc
• Altera Corporation
• Amazon.com [6 delegates]
• Appeon Corporation [2 delegates]
• Apple Computer [5 delegates]
• Apress [3 delegates]
• Arkivio
• ASA
• Astute Solutions
• Avaya Inc [2 delegates]
• Avenda Systems
• Avenue A | Razorfish [3 delegates]
• Axcella, LLC [2 delegates]
• Aximsoft
• Azimyth
• Backbase USA Inc. [4 delegates]
• BAE Systems [2 delegates]
• Bank of America [2 delegates]
• Barkley Evergreen & Partners Interactive
• Bayview Financial [2 delegates]
• BEA Systems [3 delegates]
• Billeo
• BMC Software, Inc. [2 delegates]
• Borland Software Corporation
• Bradford Technologies, Inc [2 delegates]
• Brilliance
• Brocade Communications Systems, Inc. [2 delegates]
• Brookside Capital LLC
• Brulant
• Bungee Labs, Inc [6 delegates]
• Bureau of Labor Statistics
• BUZ Interactive
• Cadena Software
• Calix Networks
• Callidus Software [2 delegates]
• Cambia Security
• Carnegie Mellon West
• Cautella, Inc.
• CBSA
• Celequest [3 delegates]
• Change Vision, Inc.
• Charles E. Kenney, CPA
• Charles Schwab & Co., Inc. [8 delegates]

   read more...


ADVERTISE   |   MAGAZINE SUBSCRIPTIONS   |   FREE BREAKING-NEWSLETTERS!   |   SYS-CON.TV   |   BLOG-N-PLAY!   |   WEBCAST   |   EDUCATION   |   RESEARCH

.NET Developer's Journal - .NETDJ   |   ColdFusion Developer's Journal - CFDJ   |   Eclipse Developer's Journal - EDJ   |   Enterprise Open Source Magazine - EOS
Open Web Developer's Journal - OPEN WEB   |   iPhone Developer's Journal - iPHONE   |   Virtualization - Virtualization   |   Java Developer's Journal - JDJ   |   Linux.SYS-CON.com
PowerBuilder Developer's Journal - PBDJ   |   SEO / SEM Journal - SJ   |   SOAWorld Magazine - SOAWM   |   IT Solutions Guide - ITSG   |   Symbian Developer's Journal - SDJ
WebLogic Developer's Journal - WLDJ   |   WebSphere Journal - WJ   |   Wireless Business & Technology - WBT   |   XML-Journal - XMLJ   |   Internet Video - iTV
Flex Developer's Journal - Flex   |   AJAXWorld Magazine - AWM   |   Silverlight Developer's Journal - SLDJ   |   PHP.SYS-CON.com   |   Web 2.0 Journal - WEB2

SYS-CON MEDIA:   ABOUT US   |   CONTACT US   |   COMPANY NEWS   |   CAREERS   |   SITE MAP
SYS-CON EVENTS  |  AJAXWorld Conference & Expo  |  iPhone Developer Summit  |  OpenWeb Developer Summit  |  SOA World Conference & Expo  |  Virtualization Conference & Expo
INTERNATIONAL SITES:   India  |  U.K.  |  Canada  |  Germany  |  France  |  Australia  |  Italy  |  Spain  |  Netherlands  |  Brazil  |  Belgium
 Terms of Use & Our Privacy Statement     About Newsfeeds / Video Feeds
Copyright ©1994-2008 SYS-CON Publications, Inc. All Rights Reserved. All marks are trademarks of SYS-CON Media.
Reproduction in whole or in part in any form or medium without express written permission of SYS-CON Publications, Inc. is prohibited.