Not according to how ZDNet’s David Berlind understands “support”, if I understand him right.
While IBM is supportive of Eclipse RCP, it doesn’t support the platform, per se, but rather supports an implementation of some of the code embedded within its Workplace client
David says: “in my more than 15 years of tech journalism, the word “support” always carried with it the implication that the vendor in question would back up the functionality through its technical support”.
I haven’t decided yet whether this posting is intended as a reductio ad absurdum for David, or as a critique of IBM. What do you think?
IBM supports its own products, not the open source code they are based on, although obviously within WebSphere there is Apache componentry that IBM does support, by David’s definition.
Meanwhile IBM does a great job of benefiting from the open source halo effect, but I do think there is a tension in claiming it supports something.
Either IBM doesn’t “support” Eclipse, or Microsoft *is* going to “support” ODF through the plug-in.
Perhaps David needs to rethink his definitions for the open source age. Just what does it mean to support a project, as opposed to supporting a product?
We have new vendors such as Sourcelabs, SpikeSource and OpenLogic set up to deal with the fact that support is now increasingly decoupled from code. Thus I can purchase support for the LAMP stack, say.
Does Red Hat support Linux or does it only support Red Hat’s distribution?
To my mind support is possibly a question of making a contribution (which could be purely financial, why not?), rather than a limited traditional definition of technical support. With that in mind, I am tempted to say that actually IBM does support RCP, and Microsoft really does plan to support ODF.
There is another way of thinking about support. That is support through adoption. I would also like to know what Simon Phipps thinks.
If I use it I support it. This definition would say IBM definitely supports Eclipse RCP, while Microsoft doesn’t support ODF.
I would really like to know your thoughts.
Mark Cathcart says:
September 1, 2006 at 7:13 pm
Bang on James. If you get something from us that has support, we will support any open source components used as part of that product, but ONLY in conjunction with that product.
So, for example, if you install Workplace Client which pulls in Eclipse RCP, and you find the Eclipse RCP fails when using it from something else, or trying to modify something provided as part of the Eclipse RCP, then you are on your own, we won’t support it.
If you want support for the Eclipse RCP or other open source technology outside of an IBM Product, then thats a discussion to have with IBM Global Services or other service provider.
There are examples where an IBM Product pre-reqs an open source based technology, but that technology is not included. You are expected to source it yourself. In that case we won’t support the open source based technology either(usually). If our product breaks and in the problem is in the open source technology, then we have to fix the product or identify a solution in the open source technology. Thats not the same as supporting it.
You need to check the T&C’s as there may be exceptions I’m not aware of.
Glad you had a good three weeks off. Staying home is often better than the hassle of travelling and stress of dealing with new places etc. with a youngster!
Savio Rodrigues says:
September 1, 2006 at 10:23 pm
James, I believe that support has to be defined in a more encompassing way than David’s description. Like you said, supporting open source is totally about contributing new features, contributing defect fixes, providing hardware, providing $$$$, using in commercial products, providing technical support, providing training, etc. for the open source project/product.
For example, in the case of open source Apache Geronimo, IBM does actually provide support (by David’s definition) for the open source product. So, for example, customers can buy support subscriptions here: http://www.ibm.com/software/webservers/appserv/geronimo. In addition, IBM develops, and sells support for, WebSphere Application Server Community Edition, which is a free product based on open source Apache Geronimo. So, in the case of Apache Geronimo & WebSphere Application Server Community Edition, IBM ‘supports’ Apache Geronimo using most of the definitions you’ve discussed 😉
Also, AFAIK, even in examples where IBM uses open source code inside of a commercial product, defect fixes made by IBM to the open source code in question are contributed back to the community in question.
Just Nell says:
September 3, 2006 at 2:49 pm
It’s great to see such wisdom in someone so young James. I’m sure IBM would love to have you as part of their team.
Ian Skerrett says:
September 5, 2006 at 3:37 pm
James,
I think the challenge is that the term ‘support’ is overloaded. There a probably 3-4 different types of support:
1) Committer support. IBM does provide support for RCP by contributing developers to work on the project.
2) Technical support. I think this is what David is talking about. I don’t believe IBM provides ‘fee based’ RCP support but it does provide ‘free’ technical support via the open source community and rcp newsgroups.
3) Implementation support. Providing consultants and trainers to help customers implement. Not sure if IBM Globabl Services does this?
4) You could also include the adoption support and sales/marketing support. Both I think IBM is doing for RCP.
fel3232 says:
October 15, 2007 at 8:31 pm
IBM’s support for RCP is almost zero. It is a shame , afterall. Hope this will improve over time.