If you've spent much time in open source projects, you have probably seen the term "copyleft" used. While the term is quite commonly used, many people don't understand it.
A recent court case illustrates the importance of reading and understanding technical terms used in copyright licenses.
The bill would provide a tax credit of 20% of "expenses associated with the development of open source and free software."
As we continue to create new open source foundations, we need to be thoughtful in the how-and-why of such foundations.
Judges and lawyers need to understand what open source software is: not just software made available under a license, but software that has an accompanying ethos.
The first instance of a court in Germany (and perhaps anywhere) addressing GPLv3 occurred in a decision by the Regional Court of Halle in July 2015
Software licenses are the legal underpinning of open source projects, but companies don't always know how to manage them. Jeff Luszcz explains in this interview.
Mike Parks explains open source hardware today and why it's winning.
Get a sneak peek at GitHub Government Evangelist Ben Balter's OSCON talk, "Open source licensing on GitHub by the numbers."
The thrust of the US House Judiciary Committee hearing was pretty clear: Congress needs to act. And while the Supreme Court has taken some steps, it is not a substitute for legislative actions focused on the fundamental issues in the system that abusive patent litigants use to game the system.