Eating our own dog food in open source

Register or Login to like
Register or Login to like
open source button on keyboard

Last month, after nearly two decades of using free and open source software, I attended my first conference: SELF. I even gave a little talk there, a kind of high-level overview of open source tools available to those of us who produce creative work (you can watch it on SELF's YouTube channel if you have an hour to kill).

The point of the presentation was that it's absolutely possible to go from concept to a deliverable creative product using only open source tools... and it's been that way for a while. However, in the discussions I had with people at the conference, I was amazed by how many people who came up to me and said, "I had no idea the tools had come this far." Even more incredible was the fact that some of these people were graphic designers working for companies with a commitment to open source as part of their missions.

I started asking around, "What did you design that banner with? Your flyer? The graphics for your T-shirts?" It was a small survey, but of the people who could actually answer that question, greater than half referenced closed, proprietary tools running on closed, proprietary operating systems.

How can this be?

The knee-jerk response is that open source tools simply aren't as capable as their proprietary counterparts. But where that stance may have held water 10-15 years ago, it's worn pretty thin in a modern context. I've grown weary of the "Program A is completely unusable because it doesn't have this one feature." More often than not, that statement is merely code for "I don't want to learn a different way of accomplishing the same task."

There's nothing wrong with that position; I just wish people would state it that way rather than laying out inaccurate blanket statements about a program's viability. If such statements were true, the Blender Institute wouldn't have been able to produce six impressive-looking open movie projects (and one game) over the last 10 years. Libre Graphics Magazine wouldn't have all of its graphics and layout created. And a growing number of creatives like  Duffy, Bassam Kurdali, David Revoy, and (if I may be so bold) myself wouldn't have been able to put food on our (and our families') tables for the last 10+ years.

And, really, all software is inadequate. I don't think I know a single artist or designer who's 100% satisfied with the way his or her tools work. You pick the inadequacies that you're willing to live with or work around. The great thing about open source software is that we have recourse. The source is there. Shortcomings can be overcome with time and effort... and perhaps sweet-talking a developer or two for sufficiently complex issues.

Another common excuse is that it's too difficult to find creatives who are well-versed in open source tools. That right there is a festering pile of equine digestive remaindering. The short list of examples I gave a couple paragraphs ago isn't the sum total of creatives who use free and open source tools. We're not that rare. We're not that strange (well, no stranger than any other creative person). Furthermore, sites like the Blender Network are making great strides in connecting creatives with people and companies who need our skills.

Creatives—all creatives, not just those that use open source programs—are more than the tools that we use. We're malleable. We adapt. We learn. We have strong foundational skills that transcend and transfer across the tools we use to create our work. With a little bit of time and training, any competent creative content producer could transfer skills and knowledge to an open source tool chain.

So, is it really just an awareness thing? Do folks really just not know what's available to us in the open ecosystem of tools? Maybe it's the artists' fault. Most of us are trained on specific, closed tool chains and rarely on open ones. We get complacent, unwilling to look outside of the realm where we're already comfortable, training ourselves to believe that open source tools are mere second-rate clones of their proprietary counterparts rather than mature tools with their own unique ways of engaging in the process of creating art. And for those of us who are using open source software for our work, we rarely speak up since we're... well, busy working.

What's the solution, then, Mr. Smartypants?

There are no guaranteed solutions, of course, but there are smart things we can do. One of the biggest is "eating our own dog food." If you're putting on an open source conference, there's no reason you can't use open source software to create the flyers, video promos, banners, T-shirt graphics, and the myriad of other pieces of content to run and promote the show. If you're working for a company that ostensibly has a commitment to open source, ask if your marketing material is being produced with open source software. If it isn't, then ask why not. And if you happen to be a creative at one of these companies, why aren't you?

That's not all, though. If you are producing creative work with open source tools (hooray!), it's not sufficient to put your head down and keep working. You've got to share that fact. Better still, share how you're doing it. You don't necessarily have to do full-blown tutorials (of course, that's always nice and appreciated). You could also do time-lapse screencasts of your work process, screenshots of works in progress, process tips and tricks you discover while working. The sad truth is that if you don't say what you made your great work in, folks are likely to assume that it was done with some closed package.

So yeah... as with most everything in open source, the solutions start with people—with us. If we don't believe in our tools, why would anyone else?


This article is part of the Open Art column by Jason van Gumster. Do you have an idea for a story about an open source art tool or project? Submit your article idea.

Jason van Gumster mostly makes stuff up. He writes, animates, and occasionally teaches, all using open source tools. He's run a small, independent animation studio, wrote Blender For Dummies and GIMP Bible, and continues to blurt out his experiences during a [sometimes] weekly podcast, the Open Source Creative Podcast. Adventures (and lies) at @monsterjavaguns.


Eating one's own dog food is good but to do so exclusively is a bad idea. W$10 is a good example of this...3.8 GB iso files, glacial installation times compulsory updates,etc. These guys really needed to spend some time with modern Linux distros such as might have made 10 a better product. It is nice but no game-changer.

*Install* your own dogfood. Get someone who didn't work on it to do that, and watch. Fix the installability/configurability/usability bugs they discover. I wish more open source projects did that.

I couldn't agree with this article more. I've been struggling to spread the viability of gnu/linux to the mostly blind and visually impaired community. The response has nearly always been overwhelmingly hostile or disinterested. The politest response is usually something like "why would I want to use that when nvda and mush z work fine for me?" It gets worse from there. This isn't a rant comment. I'm just saying that I understand how hard it can be to get someone to look and think outside the box and acknowledge the possibility of a non proprietary solution. Although nvda and mush z are open source, they run only on a closed source OS. I'll keep working. To the person who wrote this article, I'm sorry I can't remember your name, but what can I do better to get more people to at least consider linux as an option? I run into a wall, flounder for a bit while I try to understand what linux isn't doing right, then burn out, try windows, dislike it, go back to linux and the process repeats itself all over again.

There are still closed source apps? That's only vaguely interesting to me as I've done everything with free software for at least five years now, probably ten. I'm running a very successful, all open source, business now.

“More often than not, that statement is merely code for "I don't want to learn a different way of accomplishing the same task."”

I think that underscores why I disagree with your premise. There is more to it than just “accomplishing a task.” Since we’re probably talking about Gimp vs. Adobe Photoshop, here is a performance car analogy. On paper, you could say a Corvette or a GT-R do everything a Porsche Carrera does, and more. And you‘d be tempted to accuse someone that passed on the Corvette or GT-R for a Porsche as “not wanting to learn a different way of accomplishing the same task.” Yet, for some, sitting in the drivers seat makes the difference.

Probably 15 years ago, I gave Gimp a try, hated it, and continued to use Photoshop. Just recently when Adobe started their asinine month to month licensing scheme, I vowed to not give Adobe another dollar. So I tried Gimp again. I will concede that Gimp is probably stacks up to Photoshop very well. But it doesn't feel comfortable and I wouldn’t get work done with it as quickly. It’s that simple. And it’s not for nothing that Photoshop became a verb. There are some open source applications that became the de-facto standard in for what they do, and it would be nuts to use anything else. But it is not that way with all open source software; I certainly wouldn't judge someone for passing on Gimp.

Except that isn't my premise. To [over?]extend your car metaphor, it's probably not a great idea to show up in the Carrera if it's your job to sell Corvettes.

And it's not a GIMP/Photoshop thing (though both of those programs could be included in this discussion). I'm talking about the *full* suite of open source creative tools. If you have a bit of time to kill, take a look at the talk that gave at the Southeast Linuxfest (SELF). It's linked at the top of the article. It's a rough overview that shows the completeness of the open source creative toolchain.

In reply to by imotor

Could not agree more. Btw, they are eating their own dog food at a nice conference called Libre Graphics Meeting that you must know about. And Actually it tastes better than dog food. ;)

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.