Building Out an Open Source Project? Your License Matters
It was only a few years ago when Red Hat CEO Jim Whitehurst made the prediction that open source software would soon become nearly pervasive in organizations of all sizes. That has essentially become true, and many businesses now use open source components without even knowing that they are doing so.
As businesses adopt open source platforms such as OpenStack and Hadoop, they are complementing them with their own open source projects.For these reasons and other ones, it is more important than ever to know your way around the world of laws and licenses that pertain to open source software. Leaders of new projects need to know how to navigate the complex world of licensing and the law, as do IT administrators. Here is our newly updated ollection of resources to help you navigate the world of open source laws and licenses.
We've rounded up some resources on open source, licenes and the law, as seen in this post, but the topic remains a moving target. Did you know that there is an official, free journal dedicated to open source law? It's the International Free and Open Source Software Law Review, and it's worth looking into.
Among topics covered by this journal, you'll find content related to copyright, license implementation, license interpretation, software patents, open standards, case law and statutory changes. Here are just a few example articles, and you can get all articles from the site in either PDF or HTML format:
If you're in search of the perfect license for your open source project, start at GitHub's Choosealicense.com site. It covers nearly every type of license and can even help if you're open source project isn't software.
As we noted in this post, the Software Freedom Law Center (SFLC) also has a set of very good resources on open source licensing and legal topics, as well as advice on copyrights. Legal issues are smart to anticipate up front. The SFLC authors are attorneys who were part of creating popular open source licenses.
The Open Source Definition is where every project leader should start when it comes to how open source projects should be distributed, and what actually qualifies as open source. It's also good to review Open Standards requirements.
For an easy to digest, plain language discussion of license types for open source projects, and which license will work best for your project, try FOSS License Wars. The discussion is broken up into chapters that you can skim as you see fit, and the information is solid. We have much more information on licenses available here, and the Free Software Foundation has a good primer. It's also an excellent idea to visit SourceForge, and review the many projects housed there, which types of licenses they have, how their communities work, and more. Should your project be housed there?
If you're stitching together open source code or deploying applications, Hewlett-Packard's free application Fossology is designed to analyze the source code for any project and report accurately on which licenses are being used. Meanwhile, opensource.com has a good reminder post on how open source licenses are shared resources, found here.
Finally, don't forget that OStatic itself is an excellent forum for getting questions answered. Type a question in at any time in our Member Questions area (see the Questions button on the home page) and you'll get answers from experts. You can also read some of OStatic's many interviews with open source project leaders, with a number of good examples found here.