“Clearly, many organizations have already accepted the
open-source methodology. Apache remains a leading Web server
toolset, and Linux is popping up in many corporate networks in
utilitarian roles, such as DHCP resolution. In fact, Gartner
recommends that IS organizations reexamine any policy that flatly
excludes OSS projects.”
“So why are some organizations–and consequently IT pros–slow
to embrace OSS? Much of this apprehension is due to common
misconceptions about open-source development and support issues.
When evaluating the viability of adding OSS skills to your own
toolset, you may hear any of the following arguments against making
the move to OSS. Although all of these criticisms contain kernels
of truth, they are often overstated and should not present an
absolute barrier to tackling an enterprise project with an OSS
solution.
“Myth 1: Nobody controls development
…
Myth 2: Anyone can change the software, which eventually becomes
unstable
…
Myth 3: When the lead developer leaves, the project dies
…
Myth 4: There is no one to turn to for support
…
Myth 5: OSS projects will eventually splinter–like UNIX
…”
Complete Story [ Free registration required ]