Language Selection

English French German Italian Portuguese Spanish

Change OSS Licenses to Make More Money?

Filed under
OSS

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.

Clearly, this is not in the spirit of open source: it puts restrictions on the code (even though the restrictions eventually lapse). Why does he propose this? He claims such a move would help young companies make more money from their investment of time and resources.

I disagree strongly.




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more