Skip to main content

IBM is its own open-source lab for social software



Jeff Schick, IBM

(Credit: Jeffrey Gluck, IBM)

Most vendors must guess what customers want to buy, and how they'll use it. For IBM, however, with about 400,000 employees, it has the potential to be its own best laboratory, one that becomes even more potent when mixed with active participation in open-source communities.


That potential, as I discovered in an interview on Friday with Jeff Schick, IBM's vice president of social software, isn't a "gimme," but is powerful if you can enable the right sort of corporate culture and processes.


For example, Schick mentioned that IBM has a technology adoption program for employees that spans the gamut of new products, add-ons and patches to existing products, and still-raw technologies direct from IBM's labs. While the invitation list and process is different for each particular item, IBM generally encourages its product groups to "experiment" upon each other. The earlier in the development process, the better.


At the heart of this open approach to technology adoption are open standards and open source. When I pressed Schick on the relative importance of both ("If you could only choose open standards or open source, which would it be?"), he responded:


Our products may include open-source components, and often do, but ultimately open standards are the most important consideration for customers. As customers integrate our products into their various enterprise systems, open standards are critical for ensuring they work.


Point taken, but it's impressive just how much open source influences IBM's product development. Gartner estimates that 80 percent of commercial applications will include open-source components by 2012. At IBM, the number may even be higher.


Despite IBM not releasing its core software products under open-source licenses, Schick noted just how integral open source is to IBM:


From a development perspective, as we build our social software products in Lotus, we're always looking at ways to improve quality and time-to-market. Open source often helps us with both areas.


For example, we were blogging within IBM for a long time before deciding to build the Lotus Connections product, which is fast approaching hundreds of millions of users. After some study, we decided to build the blogging piece of Lotus Connections using the Apache Roller project, an open-source Java blog software. We have become active contributors to the project since then.


But it's not just in Lotus Connections. As you look across nearly every capability across our social-software strategy, open source plays a critical role. Open source is an integral part of how we build products. Our engineers are very much in tune with the wide variety of open-source components that are available to them, and use and contribute to them. Regularly.


IBM seems to have figured out better than most how to marry the global open-source laboratory with a massive internal laboratory. Talking to Schick, there appears to be a very blurry line between "internal" development and "external" development, giving the company a significant advantage over proprietary (Microsoft) and open-source (Liferay, Open-Xchange) competitors alike.


Some competitors may be able to match IBM's scale, but few to none have managed to marry internal scale (employees) with the power of external scale (open-source communities) in the way that IBM has.



Follow me on Twitter @mjasay.



Comments

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…