Slashdot Mirror
Sun to release Solaris source code
According to this story on ZDNet, Sun has decided to release the Solaris Source code under their SCSL (Sun Community Source License). It seems Sun wants to copy the success story of Linux. What do you think about it?
The trouble is that a lot of people are going to mistake this for a real open source release. In some ways, it's the nightmare scenario that RMS has been trying to warn ESR of, though I don't think his methods for combating it are the most effective: most people out there still think "free software" means gratis, not libre.
So, how can we spread the word? How can we let people know:
This is a pretty complex message, and getting across even the simplest ones is difficult. How shall we tackle it?
--
Xenu loves you!
We could even explain it to NT people by comparing it to NT permissions of None, Change, Full Control, and Read, in that order. (For those unfamiliar, the main difference between change and full control is that the latter can change permissions/owners, the former can't)
--
Exigo spamos et dona ferentes
I'd like to make some points:
*) Sun's SCSL license is not open source, nor trying to be.
*) Not all the source code will be made available straight away. Like with their other stuff released under the SCSL, you'll only have to pay Sun money if you plan to make a profit on it yourself. Sun also require you to fully publish the specs for any new APIs you add, and are very hard on compatability - ie they don't want it corrupted/code forked. btw, you will need Sun's compilers to compile it, and they haven't (yet) made the compilers SCSL.
*) I don't think this is really aimed at the general public (of coders) - it's mostly aimed at commercial compains who currently want to liscence Solaris to make their own products, and there are a few, and also at developers who already use Solaris.
*) I think the two main advantages they hope to gain from this is more developer interest, and better quality software - by getting better feedback. The reliability of Solaris is very important to Sun - there are managers whose salary and bonus are tied to it's reliability.
*) This is part of Sun's relatively new, general attitude towards development - first with Java last year, some of their microprocessor designs, some high end software (Sun Cluster Tools 3), Star Office, new software (Jini and Jiro) and now Solaris. I've heard it said that Sun plan to make all their software available under the community source unless there is a good reason not to.
*) Sun have very good reasons to worry about protecting their software - Microsoft would love to damage Sun, like it did Netscape.
*) The descision to go with their "community source" lisence would not be new. Sun have very long lead times on development for Solaris, and because Solaris contains quite a lot of other people's IP (which they'd have to get a new lisence for, or do their own version) as well as tidy up the source for public release, they would have to make the descision very early in the product cycle. Solaris 8 (which will be the first to have some source code freed) went into alpha about 1 year ago, and has probably been in code freeze for about 3-6 months, and it'll be released in about 4-6 months. And Sun aren't even adding that many new features with Solaris 8. Co-incidentally (probably not), when Solaris first went into alpha, was about the time I first head Sun execs talking about making Solaris open source.
*) Some people have said that Sun might be worried about Linux, or Project Montetery wiping them out or something. Currently, as with the past few years, Sun has been having very stable and reliable growth (20-25% per year) and I haven't seen the slightest indication that they're "hurting" from Linux (the opposite in fact) and Monterey isn't even finished yet, and even at best won't take off for another 2 years.
Btw, what's new in Solaris 8 you might ask? Well, they're putting in their cluster tools software as standard (currently a seperate product), doing IPv6, including perl (perl 5.0005_03 to be precise) as well as some modules to access parts of Solaris, some bits for Java, new diagnostics tools and such. btw, Sun will support everything that comes with Solaris for 5 years after they stop selling it.
Yes, Sun is trying to profit off of the confusion between SCSL and a real open source license, as others have mentioned, and so we need to do some education to counteract that, pressure Sun to check their marketers a bit, and make sure people know that there are strings attached. Beyond that, I say more power to Sun! If I need to use Solaris, or Java, or StarOffice, for a project, I'd much rather have the source code than not.
As for those who say, "Sheesh, this is just a sneaky way for Sun to get us to fix their bugs for them, we better not let them," I think that if you work for a company that's going to use their products anyway, and you do find a bug, and you're a good enough debugger that you have a chance to fix it yourself rather than wait 6 months for Sun to do it, and if you can fix the bug on company time, then you're much better off fixing the bug, your company's better off, and so I'm glad that employees of companies which are already using Solaris have that option. In a sense this is no different than if you find a bug in Linux and fix it on company time, since you're getting paid either way, and either way you get the good feeling of knowing that you've helped made a critical piece of software is more reliable.
But, you might argue, "Well, if I help make Sun's software better, then they're going to make more money, and we can't have that now, can we?" You neglect the fact that Sun would've made just as much money and had just as many customers with or without your bug fix, and so the only real difference you've made is making life a little bit easier for the community of other users who are forced to deal with Solaris. And after all, that's why they call it a "community source license", because Sun really does want to make things better for their community of users, and hopefully in the end, with your bug fix, and thousands of others, they will have a slightly more reliable product and ultimately make slightly more money. And if that's a problem for you, then don't contribute! Some other Solaris user will likely find and fix the bug you would have fixed anyway.
But what if you go beyond fixing bugs and start adding new features to Solaris? Well, then, I can see some justification for being upset with the licensing terms. Suppose you add some better x86 hardware detection code to the Solaris installer and contribute it back to them. Then when Sun releases the next version of Solaris, they proudly point to their new WhizzyCoolInstall(tm) feature, and raise the price by $200. They sell a zillion copies of Solaris/x86 and cut into the Linux market a little. You're perceived as a sell-out, and nobody's happy, except Sun, and they stop being happy when everybody sees how you were treated and nobody else is foolish enough to add features to Solaris. What then?
In that case, I'd say, "don't do that then." If you have an idea for a great new feature, make it a loadable module. License it under whatever terms you want. With access to the Solaris code, you can easily make it work under Solaris, and you (or anyone else) can make it work under Linux too. If you were planning to release WhizzyCoolInstall under open source, then you weren't going to make any money off of it anyway, and this way, Sun can't turn around and use your new feature against Linux, because both OS's will have access to it. Everyone's happy, and the community of people who have to use Solaris, as well as the community of rabid Linux fan^H^H^Husers are both happy.
Honestly, I'm starting to think that /. has become physically incapable of seeing loaded issues like SCSL in their proper contexts. In the business world, most people are going to be thinking like me, so you might as well get used to it, and come up with some sort of realistic response, rather than "Sun must die." Especially since Sun's going to do it anyway, and their customers are going to be happy, and if you don't look at the issue from the POV I just gave, then you won't understand what happened.
--
Jake