The Challenge Open Source Presents to CIOs, Part II: The Solution
“The important thing is to plan a strategy, to set guidelines on where and when open source products are to be used. IT shops are scrambling to set open source policies, but almost no one has implemented one with any teeth.”--Mark Driver, Gartner Group
In last week's posting, I discussed the challenge open source presents to CIOs. In it, I analyzed an interaction between Sun CEO Jonathan Schwartz and an unnamed CIO, who professed that no open source was used in her organization and then was surprised when Schwartz noted that 1300 downloads of MySQL had gone into the organization in the previous six months.
I went on to describe the risks this kind of invisible open source use presents. The most obvious -- and the one usually focused on -- is the legal risk: if you don't know you're using open source, how do you know whether you're complying with its license obligations? However, as I said, this is actually a smaller risk compared to the operational risk of having unknown software components inside the company's infrastructure: how do you offer SLAs, ensure proper support coverage, and develop appropriate employee skills when you don't even know what you're running?
I often hear from people that they don't understand why open source should be handled any differently than any other IP. Put another way, this question might be phrased, what about open source causes it to be different than proprietary software? After all, both proprietary and open source software are both copyrighted intellectual property distributed under a license, so they must be the same, right?
The reason open source requires implementing a new set of processes reflects the fact that existing processes are configured around the practices and assumptions of proprietary software, which are not present due to the unique licensing and availability of open source.
Consider the usual flow of obtaining proprietary software:
- Software engineer recognizes need for new software component
- Software engineer consults with manager
- Manager builds business case
- Manager consults with finance, legal, and procurement
- Manager obtains budget
- Procurement creates RFP
- Company obtains software
- Engineer implements solution
As you can see, there are many steps and many organizations involved in this process. While the process can require an extended period to execute, it provides the opportunity for the entire organization to become aware that new software is going to enter the company's infrastructure. In other words, this process ensures no surprises, because all affected parties are involved.
By contrast, consider the usual flow of obtaining open source software:
- Software engineer recognizes need for new software component
- Engineer downloads open source component
- Engineer implements solution
The ease of downloading open source addresses one of the major complaints about IT: everything takes too long. Using open source enables IT organizations to be far more nimble and creative. Unfortunately, if you compare this process with the proprietary-focused process, you can see what it lacks: the opportunity for other important groups to become aware that this new software is going to enter the company's infrastructure. That is to say, open source decisions never enter the established process because no permission, and, crucially, no budget is required to obtain it. Since the established processes are typically triggered by the budget process, open source use is essentially invisible to the organization.
Clearly, as the quote from Gartner VP Mark Driver indicates, IT organizations have to put policies in place to
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
