SpringSource and Covalent Follow Up

Posted by Jim Jagielski on Friday, February 1. 2008 in Work

Ever since the announcement of the SpringSource acquisition of Covalent on Tuesday, I've been following along all the various blogs, articles, speculations and threads regarding What It All Means. Needless to say, I've also received quite a sizable number of Emails, IMs and calls about it as well. In general, the variety and range of thoughts and perceptions did not disappoint. Many people "got it", most people got "most of it", a few were completely off-base and others simply used the news as an opportunity to spread FUD about just about any topic they wanted to... It was all quite amusing. Now that things are settling down, I thought it would be a good time to clear up a couple of the most common and interesting misconceptions (as well as answer some of the most common questions) regarding this. As one would expect, this is mostly to address those familiar with Covalent (any myself), and looking at it from that point of view... First of all, both Covalent and SpringSource are very excited by this combined company. Although transactionally it was an acquisition, it really is closer to a merger and a marriage than anything else. The two companies combine to compliment each other, to grow together, not to grow one side at the expense of the other. To do otherwise would be pretty stupid. So this leads me to what has likely been the most common question (and misconception): "If I don't use Spring or even Java, is the combined company still interested in me?" Absolutely!! We understand and appreciate non-Java architectures; in addition to the Java-side, this has been a major strength of Covalent. With the combined company, this does not go away. In fact, we will now be able to grow it even more. So if, for example, you are a LAMP/SAMP environment (or potential partner/provider), SpringSource/Covalent is still uniquely qualified to provide support and services for you. And will always be. If your architecture is a blank page, then certainly we can provide valuable insight on how it should be designed. But if your architecture uses any of the codebases and software that we support, no matter what, you can be guaranteed that you will never feel like a second-class citizen, no matter what the technology it is. Another common question has been whether the combined company will continue Covalent's long-term support of the ASF. YES! SpringSource knows, understands and, even more importantly, appreciates the close relationship between the ASF and Covalent, as well as the "pure ASF work" done by Covalent employees. This will not change and, again, will even now be able to be expanded even more. But to be 100% clear, SpringSource knows and will always know that ASF projects are handled, controlled and directed by the ASF, not anyone else... Our involvement in the ASF will not change. You see, the combined company increases the breadth of technologies that are now supported, but with the same depth of expertise that both companies have been known for. Because of this, the company can grow faster combined, than either one could have separately, a point which some people missed completely. And not only can we grow the company, but we can also continue to grow the usage and uptake of open source! And anyone who knows me, knows how key that is to me. So I'm very excited by this opportunity. Without exception, the SpringSource folks have been nice, honest, smart and noble people, and I feel like the afterburners have just kicked in. It's going to be fun.

The author does not allow comments to this entry


Search for an entry in IMO:

Did not find what you were looking for? Post a comment for an entry or contact us via email!