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

GNOME News

  • GNOME's JavaScript Component Will Be Seeing More Improvements For 3.26
    GJS -- the GNOME JavaScript system that allows for GObject introspection and other capabilities via JavaScript on the desktop -- is planning for further improvements with GNOME 3.26.
  • Show desktop icon in Gnome 3 - Where and how
    Despite my recently found liking for Gnome 3, largely because of Fedora 24 and Fedora 25, plus some rigorous work with extensions like Dash to Dock, it is still a highly inefficient desktop environment. The unnecessary touch emphasis is there, regardless of what anyone says, and it makes things difficult. For instance, Show desktop. This is an action slash widget in pretty much every other desktop, and despite occasional setbacks and regressions, it's always been there, a loyal companion in the moment of need. Not so in Gnome 3. Not just hidden. Not there at all. And what if you want it? Far from trivial. Hence this tutorial.
  • There's a script that makes the GNOME launcher a bit more organised
    I follow a great many sources for news and one that popped up in my feed is the 'gnome-dash-fix' script. It sorts out the mess that is the GNOME application launcher.

Leftovers: KDE and Qt

  • KDE neon CMake Package Validation
    In KDE neon‘s constant quest of raising the quality bar of KDE software and neon itself, I added a new tool to our set of quality assurance tools. CMake Package QA is meant to ensure that find_package() calls on CMake packages provided by config files (e.g. FooConfig.cmake files) do actually work.
  • Aether Icon Theme
  • Krita 2017 Survey Results
    A bit later than planned, but here are the 2017 Krita Survey results! We wanted to know a lot of things, like, what kind of hardware and screen resolution are most common, what drawing tablets were most common, and which ones gave most trouble. We had more than 1000 responses! Here’s a short summary, for the full report, head to Krita User Survey Report.
  • Cutelyst 1.6.0 released, to infinity and beyond!
    Once 1.5.0 was release I thought the next release would be a small one, it started with a bunch of bug fixes, Simon Wilper made a contribution to Utils::Sql, basically when things get out to production you find bugs, so there were tons of fixes to WSGI module.
  • LaKademy 2017 just started!
    The Latin America KDE Summit, LaKademy, just started today in Belo Horizonte, Minas Gerais, Brazil. The country is in the middle of a general strike, which I’m supporting, but the LaKademy couldn’t stop. We’ve been organizing this meeting for a year.
  • KDE Connect from the eyes of a newbie... What sorcery is this?
    Of course, I inferred it was something to connect a phone and a PC in some way and enabling the swapping of files in between the two devices, but I really did not care much about it. After all, that is what bluetooth is for, right? Today, I decided to give it a try on PCLOS.
  • 9 months of Atelier project, almost time to launch(or not) =D
  • Nextcloud Plugin for QuickShare
    So after a long hiatus I chose the Plasma QuickShare applet (which is sort of the Plasma5 replacement for the old Pastebin Plasmoid) as my point of re-entry into KDE code work. There was after all a deal of itches there I wanted scratched. It’s been quite a bit of fun figuring out the various interesting frameworks QuickShare is connected to at the backend. Anyways, some days ago I got a rudimentary Nextcloud plugin past review and pushed it, which should mean it’ll soon be coming to a 5.10-powered desktop near you :)
  • QNX as a desktop operating system
    On his spare time, Elad Lahav (a kernel developer at BlackBerry) built an experimental Qt-based desktop environment to try and see if he could use QNX as a desktop operating system. And it works!
  • Performance regression testing of Qt Quick
    We recently added a new toy to The Qt Project, and I wanted to give an overview on what it is and how it can be used.
  • Qt World Summit 2017 Call for Presentations
  • Give us a proper mimetype name for OpenCL C files!
    KDevelop, your cross-platform IDE, since version 5.1 has initial OpenCL language support.

Oh Snap – to boldly package where no one has packaged before

One of the great disadvantages of the Linux desktop is its software distribution mechanism. While the overall concept of central software repos works great and has been adapted into powerful Stores in commercial products, deploying and using programs, delivered as packages, is a tricky business. It stems from the wider fragmentation of the distro ecospace, and it essence, it means that if you want to release your product, you must compile it 150 odd ways, not just for different distributions but also for different versions of the same distribution. Naturally, this model scares away the big game. Recently though, there have been several attempts to make Linux packages more cross-distro and minimize the gap between distributions. The name of the game: Snap, and we’ve tasted this app-container framework before. It is unto Linux what, well, Windows stuff is unto Windows, in a way. Not quite statically compiled stuff, but definitely independent. I had it tested again in Ubuntu 17.04, and it would appear that Snap is getting more and more traction. Let’s have another look. Read more

Kubuntu 17.04 - the next generation

As usual, Kubuntu 17.04 does not give you any surprises. It is stable and reliable. It is reasonably resource-hungry. There are no wonders in this new release. Just a well-rounded distribution for everyday use. Yes, there are small bugs or inconveniences here and there, but they are not huge and can be easily fixed, replaced or lived with. The biggest of them for me, of course, is the lack of multimedia codecs. You can heal that easily. Read more