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

OSS Leftovers

  • IRS Website Crash Reminder of HealthCare.gov Debacle as OMB Pushes Open Source
    OMB is increasingly pushing agencies to adopt open source solutions, and in 2016 launched a pilot project requiring at least 20 percent of custom developed code to be released as open source – partly to strengthen and help maintain it by tapping a community of developers. OMB memo M-16-21 further asks agencies to make any code they develop available throughout the federal government in order to encourage its reuse. “Open source solutions give agencies access to a broad community of developers and the latest advancements in technology, which can help alleviate the issues of stagnated or out-dated systems while increasing flexibility as agency missions evolve over time,” says Henry Sowell, chief information security officer at Hortonworks Federal. “Enterprise open source also allows government agencies to reduce the risk of vendor lock-in and the vulnerabilities of un-supported software,” he adds.
  • Migrations: the sole scalable fix to tech debt.

    Migrations are both essential and frustratingly frequent as your codebase ages and your business grows: most tools and processes only support about one order of magnitude of growth before becoming ineffective, so rapid growth makes them a way of life. This isn't because they're bad processes or poor tools, quite the opposite: the fact that something stops working at significantly increased scale is a sign that it was designed appropriately to the previous constraints rather than being over designed.

  • Gui development is broken

    Why is this so hard? I just want low-level access to write a simple graphical interface in a somewhat obscure language.

OpenBSD and NetBSD

Security: Twitter and Facebook

  • Twitter banned Kaspersky Lab from advertising in Jan
     

    Twitter has banned advertising from Russian security vendor Kaspersky Lab since January, the head of the firm, Eugene Kaspersky, has disclosed.  

  • When you go to a security conference, and its mobile app leaks your data
     

    A mobile application built by a third party for the RSA security conference in San Francisco this week was found to have a few security issues of its own—including hard-coded security keys and passwords that allowed a researcher to extract the conference's attendee list. The conference organizers acknowledged the vulnerability on Twitter, but they say that only the first and last names of 114 attendees were exposed.

  • The Security Risks of Logging in With Facebook
     

    In a yet-to-be peer-reviewed study published on Freedom To Tinker, a site hosted by Princeton's Center for Information Technology Policy, three researchers document how third-party tracking scripts have the capability to scoop up information from Facebook's login API without users knowing. The tracking scripts documented by Steven Englehardt, Gunes Acar, and Arvind Narayanan represent a small slice of the invisible tracking ecosystem that follows users around the web largely without their knowledge.

  • Facebook Login data hijacked by hidden JavaScript trackers
     

    If you login to websites through Facebook, we've got some bad news: hidden trackers can suck up more of your data than you'd intended to give away, potentially opening it up to abuse.

Beginner Friendly Gentoo Based Sabayon Linux Has a New Release

The team behind Sabayon Linux had issued a new release. Let’s take a quick look at what’s involved in this new release. Read more