In a recent article1, Monty Widenius, a primary author of MySQL, argues that typical open source licensing is a problem for entrepreneurs, and that a change is needed. He recommends something he calls “business source,” which essentially means code under a commercial license that automatically converts to an open source license after a defined period of time, such as three years. Each new version of the code triggers a new three-year license clock for that version.
Every department in a corporation has requirements and prerequisites to optimize performance. It is no different when assembling a team of individuals to manage open source use within an enterprise. This article briefly touches on the obvious characteristics, followed by a focus on the not-so-obvious characteristics a solid open source management team must possess.
I suppose it's not shocking or newsworthy (to most people) when an open source project changes its license. Some projects involve a small number of developers, making consensus around such changes easy; some projects have a contributor agreement whereby copyright is assigned to a single entity, averting the need for consensus.1 However, when an open source project has many contributors and no contributor agreement, then such a switch is indeed attention-grabbing. Why? Because to do so means obtaining the permission for the license change from each contributor—a task that is undoubtedly arduous and tedious, requiring an unswerving attention-to-detail and perseverance. But it can be done, as so proved by the efforts of Jean-Baptiste Kempf in switching VLC from GPLv2 to LGPLv2.1.
Shortly after announcing an update on mobile app open source compliance research, I presented on the broader topic of "Apps, App Store, and Open Source" at LinuxCon in San Diego. Judging from the number of people who attended the presentation and their engagement, this is still a topic many people are intrigued by. In this post, I'll provide an overview of the research and its potential implications.
As a developer I'm always keeping my eye out for new technologies that can help me do my job better or faster. There's a saying in this industry: "work smarter, not harder." If I can use a piece of existing code instead of writing it from scratch, I will, unless there's a good reason not to. And diving into a new language, library, framework, or database can be like wearing a brand new pair of jeans. The novelty is exciting.
Commercial source code scanning tools have become quite the hot topic for CIO’s, software development managers, in-house counsel, and enterprise architecture teams over the last eight to ten years. The emergence of these new technologies obviously has direct correlation to the maturity of open source software, which is now just as common as commercially-licensed software in medium to large enterprise data centers. Additionally, the distribution of open source into the consumer market is undeniable making source code scanning a critical risk mitigation measure for all companies that are buying or selling modern technology. Today’s article will briefly explain “noise reduction” and the process of using multiple matching techniques in a source code scanning tool.
I remember when I first stumbled upon the International Free and Open Source Software Law Review. The timing was such that the first issue had only recently been published and I was tickled pink to know that there was a "law review quality" journal dedicated to my area of law. Who are these wonderful people that made this happen? Little did I know then that I'd have the honor of being included on the editorial committee less than a few years later.
When most people think "open source database," the first name that comes to mind is MySQL. This relational database management system (RDBMS) has been around for 17 years, and in that time it has become intimately associated with the open source ecosystem, notably as a component of the LAMP stack used to build solid web platforms - the Linux operating system, Apache web server, MySQL database, and PHP. But MySQL also serves as the back end for prominent projects such as WordPress and MythTV, and it's used by enterprise customers such as Facebook, Sears, and BBC News.
This work is licensed under a Creative Commons Attribution 3.0 Unported License.
If you read a post on The Enterprise OSS Blog, please leave a comment. Let us know what you think, even if it's just a few words. Comments do not require approval, but they are moderated.OpenLogic reserves the right to remove any comments it deems inappropriate.