Open Source Services Come of Age
Rob writes "A new breed of solutions and services companies is bringing a more professional
approach to the deployment of open source software. A sure sign of a maturing market is
when vendors stop talking about products and start talking about services and 'solution
stacks'. It can be indicative that the marketing team have taken over from the engineers
in charge of presenting the company to the outside world, but also shows that customers
are demanding a more professional approach towards the deployment of the technology. This
is certainly the case in the open source software market, where a clutch of new solutions
and services companies have
recently sprung up to guide enterprise customers through the difficulties of open source
software deployment."
" A sure sign of a maturing market is when vendors stop talking about products and start talking about services and 'solution stacks'."
That kind of buzz word lingo is also a sure sign of bloat. It makes my skin crawl to hear words like "solution stack", not only because I don't know what the heck it means, but also because it doesn't mean anything. It's a fuzzy complicated way of saying, "a bunch of related software products that you'll find useful in your company".
I guess for OSS to join the mainstream, it will have to use the same insipid lingo that the big guns like IBM and Symantec are using.
Saskboy's blog is good. 9 out of 10 dentists agree.
The real OSS service I'm looking for is an industry of companies which specialize in their stable of OSS projects in which they are expert. So I can buy programmer support for an OSS app from any of a number of groups, none of which "own" the SW or the project. I'd like to do a DB query on a CVS repository, to check what code has been contributed by such orgs offering service. Not just as a consumer of the SW, but as a developer, when I want to include an OSS package in my own project, but not enough to gain the expertise.
That kind of service depends on the unique nature of OSS and its projects. It's a tremendous flexibility in available experience, with which proprietary source SW could never compete. And such an ecosystem also represents an extremely productive marketplace for new code shared by everyone. Produced by a "third party" with interest vested more in the quality of the public OSS package than in any tricks keeping it proprietary, despite the rules.
--
make install -not war