Industry


Ads by TechWords

See your link here


What does it mean to open source the world?

Martin MC Brown had an interesting post today about applying the open source model to aspects of life other than software. He's having trouble with a replacement for his car, and made the point that only the manufacturer has the power to solve his problem. Such is the nature of proprietary systems, where a single entity controls the system/data/product/process. But if another entity was able to take over portions of the system, he might get a solution faster.

 

Why is this? Because the car manufacturer apparently has better things to do. Two months have passed, and still no solution has been forthcoming. It's clearly not a priority for them. But if the information necessary to fix the problem was available generally to the public, a smaller entity might find it worthwhile to step in and serve the niche market vexed by the problem.

 

Ok, so this is an interesting concept, but what does it really mean to open source something that isn't software? First, let's clarify some basic points. Two key aspects of the open source model are 1) the availability of the data that describes the system, and 2) the ability to use that data to modify the system. Will this ever be applied to car replacement parts?

 

I met Bob Waldie at the LinuxWorld Conference in Boston this year - a very interesting fellow who is busy exploring how to apply the open source model to computer hardware. Bob believes that a whole new wave of innovation will come out of the concept. His company, OpenGear, is involved with an open source project to provide KVM over IP. This includes management software and some open source KVM hardware reference designs. The idea is to provide hardware reference designs that can be adopted and modified by any interested parties. In other words, open source hardware.

 

What I like about this case is that the work they are doing at OpenGear is specific and tangible, but the implications are huge. It's a baby step toward a new arena of potential innovation. Software is not hardware, of course, so it will probably take a period of trial and error to work out the differences. Bob admits, for example, that they are still working out what the licensing really means.

 

As Bob told me recently, "Individuals and firms now see the abundance of commercial success that the open source model has delivered to many firms. It is responsible for refreshing the software industry and delivering real value to customers... and I foresee they will soon start to apply this model to a host of other domains, hardware being one."

What People Are Saying

I want more & datail

I want more & datail information about the "OPEN SOURCE SOFTWARE".Can you send it to me?

Beyond standards and

Beyond standards and protocols:

Michael correctly presents public communications protocols as the enablers of the internet. The basic internet protocols evolved as standards over the 70s and 80s, and the likes of FTP file transfer protocol is now mature and comprehensively captured in rfc 959. So everyone can freely communicate, confident that the FTP client will interoperate with the FTP server end, without having to have any knowledge of the software or the hardware actually running at each end. However open source has added another dimension to this protocol standards model.

The evolution of open source FTP client software like FileZilla and NcFTP enables people, not just to use FTP, but also to freely build their own custom applications that embody this FTP communication ability. They can even easily build this communications capability into their appliances, and they can do all this with confidence in the quality of the open source code they are using. And they can add new features and these are contributed back into the community, adding to the richness of the new open source dimension that sits beneath the FTP public communication protocol.

However we often forget that the key to such open source projects being of value is not that the source information is openly available, nor that the code is licensed for public use. These projects actually succeeded, because they built a community of developers. They removed the dependency on individual developers. And they built a community of users, allowing the project to evolve to deliver robust useful open source tools. So really notions like GPL only take on substance when a project succeeds in creating a "public"- and most open source projects fail in this regard.

When Opengear spawned the okvm project one of our first tasks was to invite other businesses in the infrastructure management world to participate. The okvm project is still less than a year old, but we do now have a number of companies contributing hardware and engineering resource support, so the project outlook is good. And we are well down the track to delivering products and technologies that we believe are rich enough to encourage a large community of users to grow. So the okvm project is now at the point where we need a simple license agreement to cover the new open hardware designs that have been developed. Help here would be appreciated.

Its interesting how "open

Its interesting how "open source" is in some ways just getting back to the values that enabled the entire internet to come into being in the first place. Take for example, the TCP/IP protocol. Using the same line of reasoning as OpenGear, you could think of an ethernet card as "open source" because thanks to an open standard pretty much any ethernet card will work in any computer, and actually communicate with all of the other cards.

The view from this middle-aged engineer is what OpenGear is creating is a public communication protocol, which is what allows one computer to communicate with another, and the concept is the same wether you're sending packets or key strokes or browser clicks back and forth. Which brings us to another huge open protocol success, HTTP. If Tim Berner's Lee hadn't made HTTP an open protocol there's no doubt none of us would be using a browser at this point.

The distinction bewteen a public communication protocol and open source is subtle, but very , very, important in the hardware world. For example, since HTTP is an open, published specification, anyone can write code in any language to that specification, knowing the protocol won't change to be incompatible. If instead, all you have is open source, you're dependent on the creator of that source for every code update, which may have little to do with your hardware. For example, having the source available doesn't mean a whole lot in the hardware world if you've got a bunch of devices in the field with the old version of the software that are suddently incompatible.