MySQL Reverses Decision On Closed Source 157
krow writes "I am very happy to be announcing that MySQL will be forgoing close sourcing portions of the MySQL Server. Kaj has the official statement in his blog. No portion of the server will be closed source including backup, encryption, or any storage engines we ship. To quote Kaj 'The encryption and compression backup features will be open source.' This is a change from what was previously posted here on Slashdot. I've posted some additional thoughts on my own blog concerning how we keep open source from becoming crippleware. Word has it that we will also have a panel at this year's OSCON discussing this topic. Contrary to the previous Slashdot discussion, this shows Sun's continued commitment to Open Source."
Re:ZFS next to be open sourced? (Score:5, Informative)
Good day for all (Score:5, Informative)
Re:The whole thing was pointless anyway (Score:5, Informative)
Actually, that headline and this headline are completely inaccurate, because both mentioned a decision where none had been made.
MySQL had not decided to use a closed source license. They were considering many different licenses, including a closed source license -- but also including the GPL and other open source licenses. No decision had been made. This announcement is the first actual decision on the subject.
Re:Good day for all (Score:5, Informative)
Re:Lol Slashdot is too much (Score:4, Informative)
If anyone in the know had written the original article I doubt they would have put "Sun" in the title. It was pretty much a MySQL decision all along. The original article was not completely wrong, but it certainly was wrong on the Sun part.
Cheers,
-Brian
I don't see any problem with close sourcing (Score:4, Informative)
Re:Great to see? Want to make a bet? (Score:3, Informative)
* so will the MySQL Connectors, and
* so will the main storage engines we ship.
In addition:
* MySQL 6.0â(TM)s pending backup functionality will be open source,
* the MyISAM driver for MySQL Backup will be open source, and
* the encryption and compression backup features will be open source,
where the last item is a change of direction from what we were considering before.
The change comes from MySQL now being part of Sun Microsystems. Our initial plans were made for a company considering an IPO, but made less sense in the context of Sun, a large company with a whole family of complementary open source software and hardware products.
Re:ZFS next to be open sourced? (Score:4, Informative)
Re:I don't see any problem with close sourcing (Score:1, Informative)
Re:The whole thing was pointless anyway (Score:3, Informative)
The business decision on this was made by MySQL AB (by me as the then CEO)... [slashdot.org]
The decision was made and then was reversed.
Re:The whole thing was pointless anyway (Score:5, Informative)
The business decision on this was made by MySQL AB (by me as the then CEO)... [slashdot.org]
The decision was made and then was reversed.
Re:Now change the ZFS license SUN (Score:1, Informative)
Re:Alternate interpretation of events... (Score:4, Informative)
Actually Sun CEO Jonathan Schwartz has explained numerous times in his blog that opensourcing your products increases your revenue stream in the long term. I invite you to read in particular this 2-day old post [sun.com] where he answers the FAQ "Why don't you just stop giving your software away?" and gives precisely the example of MySQL.
Re:Now change the ZFS license SUN (Score:4, Informative)
Sun doesn't want the GPL anywhere near ZFS -- and for good reason. The GPL ought to be called the "Me Me Me PL". Let's say Sun did release ZFS under the GPL and it's adopted into Linux. Sun is shut out from any changes unless they release SunOS under the GPL as well. With the CDDL, anyone can use the code (without giving up rights to their own code) and Sun gets back any improvements (without affecting their other code). It's like the LGPL, but with much better granularity.
We see this attitude a lot with BSD/GPL conflicts. When BSD code is relicensed as GPL, the original code is denied access to any changes. Think about that for a minute. "We want you to share your code. So we won't share our changes to your code with you." Free as in "free room and board at gitmo".