Language Selection

English French German Italian Portuguese Spanish

These are not the sources we're looking for

A few comments I made a couple of weeks ago where brought to the fore again this week. The comments related to getting OpenSource applications used within a corporate environment, or lack thereof. A prime example of this happened just yesterday. I'm in the middle of documenting a few things for some work I've completed on a validated system. Following the old adage of a picture paints a thousand words I needed to insert a diagram. My desktop in the office is win2k, installed with the default SMS deployed desktop. Unfortunately there is a lack of diagram software and the process to get stuff installed is so convoluted, I'd be filling in requisition forms and trying to get the necessary access to use the ordering software till Christmas... 2010. I installed Dia, knocked out my diagram, export to jpeg, insert, job done. Or so I thought.

“This is a validated document,” says Mr Document Reviewer, “we need access to the original format”

Before I venture any further I have to point out that I am a contracted resource for company B. Company B is the outsourcing provider for company A. On my contracted days I work onsite at an office in company A. With me so far? Well, there are politics here, who pays for what, who is responsible for this, who's job is that. The usual corporate quagmire sucking in the productive time and spewing out endless, senseless debates about the most trivial things.

“Well”, I tell the reviewer, “the original diagram was done with Dia and it is available on the file server”

Immediately there are a flurry of emails being bantered around. Which is the approved tool for diagrams? Company B doesn't mind, a diagram is a diagram is a diagram and if they are footing the software bill then free is good. It is a completely different story from company A. “Visio is the tool that is used and you should only use this tool”. The diagrams should be embedded and not inserted as images. Post architect review they say that the application is very good, it would do everything they need, well put together but.... and this but is bigger than the rear end of a blue whale with an over-eating disorder. But... it may disappear from the scene and we'd be left with all our documents in that format with nothing to edit them with. At this point I threw in my tuppence worth. I remarked that by taking the source longevity was assured. The return argument reverted to cost support in that case. Hmmm, I reply, 70 odd quid a pop for Visio, times by what? 1000+ users? 70k? For this version, plus upgrades and maintenance? Now compare that to free and open with the benefit that you can tailor it to your specific needs, in a programming language in which most of your in-house developers are fluent? How can it disappear? Plus, if this was developed in-house you would support it till eternity, you have the source, same thing don't you think? The reply made me give up.

It's not Microsoft and our preferred supplier of this kind of software is Microsoft. It's the company standard.

Company standard indeed.

And that was for one application that works very well at its assigned job. More than capable.

It is going to be a long battle and a major uphill struggle to get OpenSource into the big corps no matter how polished the application is.

Instead I used my energies elsewhere, screaming at the TV screen as Russia scored the second and england were scattered after snatching defeat from the jaws of victory. I sat in dismay and waited the inevitable text message coming from my other half, visiting her parents in Moscow.

Look, feel the source.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: These are not the sources we're looking for

They prefer Microsoft? Makes some sense; paleontologists have suggested that many dinosaurs ran herds. Looks like they still do.

It's just the Peter principle

Thanks for your observations about "the corporate quagmire". I recently stormed out of a Foss project when the navel-gazing interfered repeatedly with progress in actually getting something done. Now that was a quagmire. The problem is not related to software, it's about human incompetence a.k.a the Peter principle.

More in Tux Machines

Linux and Graphics: AMD, Linux 4.14 LTS, Etnaviv Gallium3D

  • Linux 4.14 Ensures The "Core Performance Boost" Bit Gets Set For AMD Ryzen CPUs
    Recently making waves in our forums was talk of a kernel patch to address a case where the AMD CPB (Core Performance Boost) isn't being exposed by Ryzen processors. Here's more details on that and some benchmarks. Being talked about recently is f7f3dc0: "CPUID Fn8000_0007_EDX[CPB] is wrongly 0 on models up to B1. But they do support CPB (AMD's Core Performance Boosting cpufreq CPU feature), so fix that."
  • Linus Torvalds Is Confident That Linux Kernel 4.14 LTS Will Arrive on November 5
    Development of Linux 4.14, the next LTS (Long Term Support) kernel series, continues with the fifth RC (Release Candidate) milestone, which was announced by Linus Torvalds himself this past weekend. According to Linus Torvalds, things have finally starting to calm down for the development of the Linux 4.14 LTS kernel, and it looks like the RC5 snapshot is smaller than he would have expected, at least smaller than last week's RC4, which is a good thing, meaning that there won't be need for eight RCs during this cycle.
  • Etnaviv Gallium3D Is Almost To OpenGL 2.0 Compliance
    The Etnaviv Gallium3D driver that provides reverse-engineered, open-source graphics support for Vivante graphics hardware is almost to exposing OpenGL 2.0. Etnaviv contributor Christian Gmeiner today posted a set of patches for adding occlusion queries support to the driver. The code at just over one thousand lines of code is the last major feature needed for exposing desktop OpenGL 2.0 capabilities with this community-driven driver.
  • AMD Developers Begin Making Open-Source FreeSync/AdaptiveSync Plans
    While the AMDGPU DC code is expected to land for Linux 4.15 with goodies like Vega display support, HDMI/DP audio, and atomic mode-setting, one of the sought after display features won't be initially supported: FreeSync or the VESA-backed AdaptiveSync. As we've known for a while, while AMDGPU DC fills out the requirements for being able to support FreeSync, the last bits of the implementation are not present as the interfaces are basically yet to be decided among the open-source driver developers. While AMD can post their existing FreeSync code as found in AMDGPU-PRO hybrid driver, they are trying to come up with a more standardized interface that will satisfy the other upstream Linux driver developers too that might want to support AdaptiveSync.

Servers and Red Hat: Cloud Foundry, Docker, CRI-O 1.0, Alibaba and Elasticsearch

  • How to deploy multi-cloud serverless and Cloud Foundry APIs at scale
    Ken Parmelee, who leads the API gateway for IBM and Big Blue’s open source projects, has a few ideas about open-source methods for “attacking” the API and how to create micro-services and make them scale. “Micro-services and APIs are products and we need to be thinking about them that way,” Parmelee says. “As you start to put them up people rely on them as part of their business. That’s a key aspect of what you’re doing in this space.”
  • Docker Opens Up to Support Kubernetes Container Orchestration
    There's been a lot of adoption of Kubernetes in the last few years, and as of Oct. 17 the open-source container orchestration technology has one more supporter. Docker Inc. announced at its DockerCon EU conference here that it is expanding its Docker platform to support Kubernetes. Docker had been directly competing against Kubernetes with its Swarm container orchestration system since 2015. The plan now is to provide a seamless platform that supports a heterogenous deployment that can include both Swarm and Kubernetes clusters. "Docker adapts to you because it's open," Docker founder Solomon Hykes said during his keynote address at DockerCon.
  • Introducing CRI-O 1.0
    Last year, the Kubernetes project introduced its Container Runtime Interface (CRI) -- a plugin interface that gives kubelet (a cluster node agent used to create pods and start containers) the ability to use different OCI-compliant container runtimes, without needing to recompile Kubernetes. Building on that work, the CRI-O project (originally known as OCID) is ready to provide a lightweight runtime for Kubernetes.
  • Red Hat brings its open source solutions to Alibaba Cloud
    Alibaba Cloud has joined the Red Hat Certified Cloud and Service Provider program, with Red Hat solutions to become directly available to Alibaba Cloud customers in the coming months.
  • Elasticsearch now on Alibaba Cloud, eyes China market
    The Amsterdam-based company behind Elasticsearch and Elastic Stack said the new offering would be available to Alibaba Cloud customers as an add-on, giving them access to real-time search, logging, and data analytics capabilities.

Software: VirtualBox 5.1.30, Cockpit 153, GNOME Mutter 3.27.1, KDE Neon

  • Oracle Releases VirtualBox 5.1.30 to Patch Glibc 2.26 Compile Bug on Linux Hosts
    Oracle released VirtualBox 5.1.30, a minor maintenance update to the open-source and cross-platform virtualization software that addresses a few important issues reported by users from previous versions. Coming one month after the VirtualBox 5.1.28 release, which probably most of you out there use right now on your personal computers, VirtualBox 5.1.30 contains a fix for a Glibc 2.26 compilation bug for Linux hosts and a 3D-related crash for Windows guest that use the Windows Additions package.
  • Cockpit 153
    Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 153.
  • GNOME Mutter 3.27.1 Brings Hybrid GPU Support
    Mutter 3.27.1 has just been released as the first development release for the GNOME 3.28 cycle of this compositor / window manager. The change most interesting to us about Mutter 3.27.1 is support for hybrid GPU systems. The context for the hybrid GPU system support is explained via this bug report, "supporting systems with multiple GPUs connected to their own connectors. A common configuration is laptops with an integrated Intel GPU connected to the panel, and a dedicated Nvidia/AMD GPU connected to the HDMI ports."
  • #KDE #KDENEON Release bonanaza! Frameworks, Plasma, KmyMoney and Digikam

Intel Ads as 'Articles'