Declare a license for software or risk losing participation and developers

The new software hygiene: Declare a license or risk losing participation

desire path
Image by :

I had the privilege of working with David Tilbrook almost 25 years ago. He was the first person with whom I ever worked that clearly articulated proper software construction discipline for collaborative endeavours and captured a summary of it under the title, Washing Behind Your Ears: Principles of Software Hygiene.

David articulated these practices pre-World Wide Web. We weren't yet living in a world where the Web had so completely removed the friction of time and space from sharing and collaborating on software that even the early Internet enabled.

The open source definition hadn't yet been coined. The forges hadn't yet been built.

The world has progressed and there's a new sort of software hygiene that's now required. I first learned back in May 2012 that one of the most popular software collaboration forges, Github, doesn't require a project creator to choose a license for their software. On September 17th, 2012, James Governor (@monkchips) reminded me of this madness when he tweeted:

younger devs today are about POSS - post open source software. f### the license and governance, just commit to github

I (@stephenrwalli) replied:

Governance implies community but promiscuous sharing w/out a license leads to software transmitted diseases

Pretty soon, a lively discussion was off and running with @nearyd, @mmilinkov, @webmink, @dberkholz, and @tieguy joining in.

Here's the problem: governments protect software creations using copyright law. Different governments have different views of how it applies and slightly different terminology. Some countries worry about author's moral rights. Others don't. Countries also have different opinions on what the public domain means and how it can (or can't) be applied with respect to software. Essentially, as with all things in the software legal space, it's a mess.

Disclaimer: This is probably a good time to remind the reader that I am not a lawyer.

Living in a proprietary software world, it was relatively "easy". Companies asserted their copyrights as protection for their software products. As software publication and collaboration became ubiquitous, we saw the rise of free and open source software licenses. These were used as statements of sharing intent and expectation by authors on their works. If a collaborative community arose around the project, these licenses were often the initial declaration of the social contract long before the community ever evolved to statements of governance and codes of conduct.

So here's the problem. If you share software on the Internet without using a license, the software is protected by your copyright and all rights revert to you. You have made no statement about how it might be used, or what you would agree to, now or in the future. If you share on a promiscuous site like Github, where forking is encouraged, and you make no such sharing statement, and start accepting change requests from other developers without licenses, then you're collectively creating a copyright mess that will eventually hurt people using your software.

By not caring, or naively believing it doesn't matter because you think "people can do whatever they want with my software," or worse using others' unlicensed software in your own means, you will eventually hit a point where you stifle the growth of your software.

It's not that you're necessarily creating a provenance mess where "dirty" IP will creep into the mix (although I'm sure some companies will try to provoke that fear to sell you things, or worse sell other people things to "protect them" from your software). It's very possible that you could create a "Software Transmitted Disease", but what you are definitely doing is limiting your project's growth.

Professional developers have a working understanding of software copyright. By professional, I mean developers more knowledgeable than you that can make your project better through contribution. When they see that there's no license on your pool of software, if you're lucky, they will ask you to declare one so they can know if they want to adopt and contribute. If you're not so lucky, then they will simply move on and you will have lost whatever contributions they may have brought to your party.

I'm not talking about Great Knowledgeable Developers who are going to join your project and stay. If you're lucky, you'll attract a few folks to your world that know a few things more about it and share them. That's ultimately the economic strength of a well run open source project. Collectively we're better. Neither am I talking about what you might need to do when Building a Big Community.

I'm simply talking about sharing your software brilliance. Because that's why you published on a site like Github, right? So you could share and learn. If you don't put a license on it, you risk losing knowledgeable participation.

So here are some bumper sticker banners to help remind you of the necessary software hygiene of the new millennium:

  • Github without licenses is like free sex without condoms.
  • Practice safe software on the Internet—use a license.
  • Practice good software hygiene—license your software.
  • Don't fork around without a license.

Collaborative development with liberal open source licenses is one of the best things that has come out of the World Wide Web phenomenon and helps sustain and grow it. Do it wisely.

Originally posted on the Outercurve Foudation Blog. Re-posted with permission.

About the author

Stephen R. Walli - I am a technical executive, a founder, a consultant, a writer, an international business person, a systems developer, a software construction geek, and a standards diplomat. I love to build teams and products that make customers ecstatic. I have worked in the IT industry since 1980 as both customer and vendor. I was a Distinguished Technologist at Hewlett Packard Enterprise. I am a consultant working for Docker.