Post a Comment
It doesn't matter if this is licensed under the GPL. The fact that this is now free software means that we have the liberty to study the logic of that code. This means that we can write our own code that implements the same logic and we can release our (hypothetical) software under any license that we have chosen.
Umm... it's NOT free sofware. It's NOT open source.
If anything, it's a kind of "shared source".
http://en.wikipedia.org/wiki/Shared_source
Umm... it's NOT free sofware. It's NOT open source.
If anything, it's a kind of "shared source".
Nonsense.
They allow everyone to look at the code, download it, compile it, change it, share it with their peers or keep it to themselves, heck, they can even make a distribution and put that online - they are just not allowed to sell it.
Thom, frankly, do you think they would carefully avoid calling it "open source" or "free sofware" if it qualified as that? I won't remind you the OSD or the FSF definition of Free Sofware. So, again, it's NOT Free Sofware, it's NOT Open Source (maybe the caps help to clarify?) and if you disagree, just Google it. You seem to have been deceived by their announcement, just like they planned.
Oh, and it would help you think more clearly if you avoided buying into their speaking about "selling" the sofware or "commercial deployment". That's very confusing and they know it. They try to blur the distinction between making a derivative under a proprietary license, and setting up a project to distribute sofware and provide support for profit, which are two VERY different things. Software is either free or proprietary. Free software can be deployed commercially (as Red Hat and other do). You can use Free Software at home and in the office, and you can set up your business around Free Sofware, without fears that anyone will charge you for making "commercial" use of said sofware.
I think their primary revenue has been support, not the actual sale of their software. If this is true, going open source makes perfect sense. The company benefits by having the open source community (hypothetically) contributing to the OS relatively cost-free, and the community benefits by learning their numerous engineering accomplishments in the realm of real-time computation.
The "open source for non commercial use" license is kind of dumb..
They _are_ QNX after all, the same way Sun is Sun.
Properly open sourcing QNX will attract a much bigger developer community. They can even use a dual-like license, and make sure that 1) If using a GPL/MPL-like approach, they only accept changes for inclusion in the main branch if ownership or special usage rights are granted 2) If using BSD/MIT, etc license, they can easily just merge the changes.
I don't understand why does QNX fail to see this..
--
To make the point clearer, they are still the owners of the product and it's not like anyone will take it from them if they opensource it. Same way it happens with Solaris and Sun. On the other hand, they will get a much larger community instead.
Edited 2007-09-12 12:15
It goes in both way, maybe you fail to see all the amount of money they invest in it and are unwilling to let other company making profit out of it.
Then why should the license "limitation" a problem?
> It goes in both way, maybe you fail to see all the
> amount of money they invest in it and are unwilling to > let other company making profit out of it.
No, I think it comes down to their business model.
Like Sun, IBM, etc. QNX also realized how their market (Aix,Solaris,etc) is being eaten alive by Linux and the overall opensource community projects (PHP, MySQL, etc), in the server, embedded, etc areas,
Even if their are strong in their own areas (Solaris for highend servers, QNX for mbedded/realtime/critical), it is undeniable that they still share a lot with the opensource OS arena, which is growing several times faster than them, and makes them realize they are missing a big business chance.
Even microsoft did at some point see this and attempted to compete by using their "Shared Source" licenses (failing miserably).
But it's been proven endless times that unless the project is FULLY open, and not something that "resembles being open" or just "free", the community will lack interest and will not pick it up. Beos and QNX itself were examples of this. They looked great, worked great, but then died and left their "community" out in the cold.
So I think it's good to point out that either QNX really goes open, or they'll likely not get much community adherence. To me, it's just another in the long list of companies that don't seem to "get it", and repeat the same mistake over and over.
Neither Beos or QNX were open source, just free to copy. I am sure if Beos was open source, Haiku developers would have concentrated their efforts on the existing code base rather than starting from scratch.
Edited 2007-09-12 13:35
So I think it's good to point out that either QNX really goes open, or they'll likely not get much community adherence.
Define "open".
If you definition of "open" is either GPL or BSD - and nothing more... Than you have a very narrow-minded view on the world... And we all know what happens to narrow-minded people.
If you definition of "open" is either GPL or BSD - and nothing more... Than you have a very narrow-minded view on the world...
I don't think so. It often doesn't make much sense investing code into something that is not open as in opensource or free software. An opensource license put every participant in a project on an equal footing. When that is not the case, one participant in a project (QNX in this case) can play games with whoever is dependent on QNX for making their money. In an opensource project, the contributions of participants lifts the tide for every participant, and contributors can be sure that they won't be locked in, or disadvanted in other ways.
Of course, licenses differ in their strength to regulate participation, and arguably, the GPL is a lot better at it than the BSD license (just to name one other commonly used license). Additionally, dual licensing like MySQL does, is a kind of workaround.
And we all know what happens to narrow-minded people.
Right, like what? At any rate, many companies make misuse of the term "open" in software to suggest opensource. While this is explicitly denied in the interview (though the Apache license bit confused me for a second), it's not suprising that people enumerate the term 'open' with 'opensource'.
Edited 2007-09-12 14:01
Define "open"
I guess he means Free Software. There are many, many Free licenses apart from GPL and BSD. But QNX won't use any of the existing ones, nor their own Free license. They'll use a "friendly" one.
That's ok with me, of course. And I thank them for it (even if I have never used QNX and don't have plans to use it soon). But it's true that with a "friendly" license they won't get too much community contributions.
Isn't this somewhat similar to what Trolltech does?
If you simply want to play with it, use it, tweak it, spread it (say, make a distro) it's free.
If you want to make money out of it, the company makes money too.
In both cases you get to modify it at will.
Sounds like a reasonable long term strategy for a company rather than wishy-washy GPLing (or BSDing) it.
Edited 2007-09-12 13:29
Actually not. Trolltech releases QT under two commercial licenses. One license is Proprietary Commercial, and the other license is FLOSS Commercial. Both licenses allows for commercial use.
Proprietary is not the same as commercial. Licenses which do not allow for commercial use are not open. All open licenses allow for commercial use, incl. GPL and Apache License 2.0.
Nope. Trolltech (though I don't agree with the choice of GPL) chose a license that allows commercial development, etc. The QNX license will not allow commercial development (without a separate agreement with them).
In theory, you could perform commercial development with Qt's open source edition.
They could have offered the same freedom to their existing commercial customers without this bizarre licensing incompatibility situation.
No, not the same way. Sun chose an open source license for their code that meets all of the commonly accepted definitions of what open source is.
QNX has chosen a license that is clearly not reflective of what most people accept as "open" and will severely restrict what their community can do with the code due to license incompatibilities.
While they are to be commended for trying, I think they're just confusing matters. Even Microsoft has chosen better licensing terms for many of their "shared source" projects with the Ms-PL, etc.
Not just for commercial ventures, but hobbyists that want to dabble, and just perhaps wind up entering into the commercial venture realm, should their personal projects/research pan out.
Perhaps the iPhone will soon have a QNX port
This also opens up a lot of other single board computers (PCI-104 and other mutations) that aren't especially powerful systems that are (perhaps) old PC-compatible or mostly so, as well as those that just fit the form factors, that are relatively cheap to get, and provides another option with great development tools and an OS you can easily strip down to the bare requirements.
So do we see the old story repeating? It sounds like the good ole days of QNX6.0 only better in a sense that they don't intend to take the OS away or cripple it with time limits.
One thought flashed through my mind though: they're late. They should've made that move several years ago and could have had a great thriving community by now. Back in the day enthusiasts were really excited about QNX. Now they'll just have to spend all those marketing resources again to attract the dev crowd back. Hey, we've even seen QNX news sites shutting down recently...
Anyway, wishing them luck and wishing them to have a separate deskop/evangelistic department within the company. Nothing commercial or serious, mind you, just to fuel the interest.
PS Their site is broken in Safari v3. Does it work in Voyager though, heh.
PPS And bring back William Bull. Pleeeeease!
Edited 2007-09-12 12:46
"QNX source code is being released with the Apache Licence 2.0, which is compatible with the GNU GPL v3."
But only one way? Can people change the code and release it under GPL v3 only so it can't get transfered back to QNX?
I hate GPL, even if it protects "freedom". It's a little evil to FORCE "freedom" on everyone =P
I've always liked QNX. I started messing with it when I moved to Japan and was looking for something to pass the time while I was not working. Back then, I think it was QNX 4 something, you could install from CD in under 5 minutes. Total network transparency. Totally cool.
I'd love to see a port of the Photon MicroUI to other nixs, man that would rock!
While the code being open will certainly be useful as a source of study, the licensing will severely restrict how people can use it.
QNX is merely continuing to muddy the waters of licensing for projects that make their code available. Microsoft at least had the decency to choose licensing terms that would be compatible with a great deal of code that is available in the open source community.
The non-commercial restriction of the code will make it difficult at best to be able to use anything but BSD, MIT, or X11 -style open source code in combination with QNX code.
While this is beneficial for QNX's customers, I can't help but think that their company has "missed the point."
Nonetheless, they are to be commended for trying.
QNX is a very interesting operating system for a small, energy-efficient desktop system (e.g. sam440ep, efika).
A typical Linux system is already overkill for daily usage and provided a good browser (Opera sucks least imho, but a webkit port would be most promising), text editor and media player, I would ditch my current Archlinux desktop instantly.
My company uses QNX commercially. As much as I think this announcement is good, it doesn't help me at all, at least directly. Neither myself nor any of my co-workers has the ability, inclination, or business case for even LOOKING at the micro-kernel source code, much less modifying it.
But maybe someone will port OpenJDK to QNX, and that would be quite helpful to me.
-James Ingraham
Sage Automation, Inc.
This is great! Ever since 6.3 came out, QNX has died as a community. So many apps are so far behind (X11, Gaim, Abiword, etc) because of the restrictions place on 6.3.
I love QNX and its UI. I can't wait for the apps to start flowing, just like in the 6.2 days.
Rock on!
Again, nothing really happened. If you download source of this "open source" kernel, and browse it - please read the headers.
You can't call this free software, you can't even call this open source.
It seems like they wanted to make bug fuss about that, it's free commercial for them - I understand that - but it is nowhere close to revolution - until it's free for commercial use and redistribution - nothing changes.
Well, the anouncement seems to be targeted more at OS enthusiasts rather that businesses, even though QSSL is all about business.
Anyway, you can't call that "nothing" because it gives people a great code example to study and educate themselves. And if you're running a business you shouldn't expect to get things for free.
No it isn't.
Yes it is. Everyone can read the source at will, it is "open" to the public.
You need to clearly differentiate between the two. That is why there are OSI open source licenses which are not considered to be free software by everyone.
Anyway QNX has made a decision which makes sense for their business. Giving away their flagship product would probably ruin them (unlike Sun which doesn't depend on Solaris to bring in the megabucks.) Instead they have opted to just open their source so their clients can write better software because they are aware of how things work internally. Sounds like a good idea to me.
No, it's not and probably couldn't be approved by OSI, because you cannot freely redistribute the product (you need to buy a license.)
I guess it depends on what your definition of "open" is. ([CLINTON MODE OFF])
"Again, nothing really happened. If you download source of this "open source" kernel, and browse it - please read the headers. "
Would you please paste the license in a pastebin and provide a link? That would be very helpful.
http://rafb.net/paste/
Okay, so what exactly _are_ the licensing terms?
It's not any of the [L]GPLv[23] licenses, it's not MIT/X/BSD licensing, it's more than likely not an OSI approved license - so it's not "Open Source" at all. This is "look but don't touch open".
This is (maybe) good for existing customers of QNX and that's it. I'm sure their internal processes will be more open too, and they probably did the work to vet where all their copyrighted code came from, which is healthy too.
But this is definitely not an "Open Source" move.









