Friday, March 17, 2006

SCO Claims They Own Part of MySQL's Code?

So what is SCO up to? They partnered with MySQL some time ago, and are now trumpeting their latest brain-child SCAMP, an assault on LAMP. I can't imagine anyone actually buying their arguments that they are somehow adding value to LAMP by replacing the "L" and plunking the rest on top of their own OS. But this is odd, from this PDF doc on MySQL at SCO's site (my emphasis added):
9. OPEN SOURCE FREEDOM AND 24 X 7 SUPPORT Many corporations are hesitant to fully commit to open source software because they believe they can't get the type of support or professional service safety nets they currently rely on with proprietary software to ensure the overall success of their key applications. The questions of indemnification come up often as well. These worries can be put to rest with MySQL as complete around-the-clock support as well as indemnification is available through MySQL Network. MySQL is not a typical open source project as all the software is owned and supported by both SCO and MySQL AB, and because of this, a unique cost and support model are available that provides a unique combination of open source freedom and trusted software with support.
Ignore the non-sequitur about proprietary software support being somehow better than open source software support, this seems to pretty clearly state that SCO owns part of the MySQL code base. Anyone have a clue why they would say that? This is what Mysql's site says about the ownership of the MySQL code base:
The company was founded in Sweden by two Swedes and a Finn: David Axmark, Allan Larsson and Michael "Monty" Widenius who have worked together since the 80's. MySQL AB is the sole owner of the MySQL server source code, the MySQL trademark and the mysql.com domain worldwide.
They are right about MySQL offering indemnification, but MySQL offers this idependently of SCO. They should just take "SCO" out of the sentence in question, since it's MySQL giving support and owning the code, not SCO.

Technorati Tags: , ,

No comments: