Enterprise Linux Online: Why Use a Roadmap When You Can Call a Taxi?
Oct 28, 2000, 22:16 (0 Talkback[s])
(Other stories by Russell C. Pavlicek)
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
"Only a fool would trust his business to software that doesn't
have a clear roadmap for the future."
"This statement seems to rear its head from time to time these
days. Most of the time, it appears as an objection to the intention
of employing open source software like Linux in a corporate
setting. The absence of someone in a suit who can describe the
long-term direction of an open source project is described by some
people as an insurmountable barrier to the adoption of open source
solutions. Not surprisingly, the people voicing this opinion are
often promoting solutions from commercial vendors which feature a
standard product roadmap. The fact that, in retrospect, these
commercial roadmaps often suffer from major flaws is
immaterial. Rather, it is claimed that the prudent commercial
customer must insist upon a traditional roadmap."
"But, is a roadmap really essential for software? Is software
with a clear roadmap always superior to software that boasts no
such detailed prognostication of the future?"
- Lotus.com: Open Source Projects Manage Themselves? Dream On(Sep 15, 2000)
- IBM developerWorks: Excerpt from "Open Source: The Unauthorized White Papers"(Sep 02, 2000)
- Wired: It'll Be an Open-Source World - Forrester(Aug 16, 2000)
- Steffen Evers: An Introduction To Open Source Software Development(Aug 06, 2000)
- TechWR-L: A Tech Writer's Guide to the Open Source Movement (Part 2)(Jul 30, 2000)
- TechWR-L: A Tech Writer's Guide to the Open Source Movement (Part 1)(Jul 30, 2000)
- Linux.com: Software Gates (Jul 13, 2000)
- Business 2.0: Open Source Policy(Jul 11, 2000)
- Upside: Can we marry the open source and commercial worlds?(Jun 28, 2000)
- Red Herring: Analyst View: Untangling the open-source explosion(May 15, 2000)