To view parent comment, click here.
To read all comments associated with this story, please click here.
"
So what you're implying is that we should ignore Novell R & D resources which are structured and well financed and instead look to disorganization as being good for consumers and the Linux community as a whole?"
There is obsolutely no need to do this within closed doors.
"You seem to forget what Novell has done for the Linux community and consumers in general. Such as releasing projects like YAST and AppArmor under the GPL, fighting FUD from SCO and Microsoft, etc"
SELinux is already upstream. Why is Novell selling security as a proprietary add on?. The user space solution for apprmor is still proprietary for your information.
"There's nothing stopping Red Hat, etc from reviewing the code as it's under the GPL."
Its not. Its under the Xorg license. Atleast get the facts straight
:What have companies such as Red Hat and Mandriva done in the last year that is so significant and wasn't just an attempt to make money?:
Who maintains glibc, gcc, large portions of the linux kernel.large amount of GNOME modules etc?
Manmist,
Regarding AppArmor: "SELinux is already upstream. Why is Novell selling security as a proprietary add on?. The user space solution for apprmor is still proprietary for your information."
These links http://developer.novell.com/wiki/index.php/Apparmor_FAQ and http://www.novell.com/products/apparmor/overview.html will explain the product better to you. As for your "proprietary add on" comment I've already stated AppArmor is licensed under the Gnu Public License (GPL) and therefore has no licensing fees. Novell is not forcing anyone to use the security product. What's good is by releasing the product under the GPL they are giving everyone access to another security tool in which to secure their networks.
Regarding XGL license: "Its not. Its under the Xorg license. Atleast get the facts straight"
Well then what you're implying is that information online such as here http://en.wikipedia.org/wiki/XGL where it's stated XGL was released open source 02/02/06 is incorrect.
So what you're implying is that we should ignore Novell R & D resources which are structured and well financed and instead look to disorganization as being good for consumers and the Linux community as a whole? You seem to forget what Novell has done for the Linux community and consumers in general. Such as releasing projects like YAST and AppArmor under the GPL, fighting FUD from SCO and Microsoft, etc. What have companies such as Red Hat and Mandriva done in the last year that is so significant and wasn't just an attempt to make money?
I think none of the posts said that, at least in this tone. Novell rightully got all the bling from this. No argue here.
Me personally, I'm all for the solution like this sooner than later, that's why I use Novells XGL now. But, I won't mind keeping the Novell-like bling after XOrg reorganizes and standardises it to something that can be called standard like "just works" solution. And having more solutions makes the possibility to pick the best one for basic default. Which is all that free software is about and it is how things worked in OSS from the dawn of time.
The way I see it is that Novell made a business decision that was in the best interest for consumers, not just their customers and used their resources to complete the project on time.
Yep, and this is where problems can start. You just have to look at it from distance. Read XDevConf papers and connect the presented technologies.
X needs a lot more global attention than just eye candy.
Let's also realize the reality is that Microsoft temorarily stopped developement of WinFS for Windows Vista so they can push it out the door sooner rather than later to market globally (Q3/Q4 2006 instead of Q4 2007). Sometimes having a small trained group working on a project is better because it's more focused than having a large group which tends to cause longer discussion, thus delays a project release.
Which works in MS case as charm. MS doesn't need to worry about getting attention from HW vendors. Linux is not so lucky.
And they all have common working environment. How would this work in free software where people mostly live in different countries?
What you said is equal to Novell taking the whole Linux development on it self and boost production. It is just too big project for this to happen'.
What have companies such as Red Hat and Mandriva done in the last year that is so significant and wasn't just an attempt to make money?
You *are* kidding right?
I'd suggest you check the kernel, gcc and gnome change logs.
Just type "gcc "at redhat dot com" site:gcc.gnu.org" in your google search bar.
Gilboa




Member since:
2005-07-10
Manmist,
RE:"You are barking up the wrong tree. Neither Red Hat nor Mandrake or any other organisation is working on XGL and has gone for a different approach. Novell basically decided to do closed development and wants everyone now to accept that."
So what you're implying is that we should ignore Novell R & D resources which are structured and well financed and instead look to disorganization as being good for consumers and the Linux community as a whole? You seem to forget what Novell has done for the Linux community and consumers in general. Such as releasing projects like YAST and AppArmor under the GPL, fighting FUD from SCO and Microsoft, etc. What have companies such as Red Hat and Mandriva done in the last year that is so significant and wasn't just an attempt to make money?
The way I see it is that Novell made a business decision that was in the best interest for consumers, not just their customers and used their resources to complete the project on time. Then they released the finalized project for other Linux developers to either use it or not. There's nothing stopping Red Hat, etc from reviewing the code as it's under the GPL. Let's also realize the reality is that Microsoft temorarily stopped developement of WinFS for Windows Vista so they can push it out the door sooner rather than later to market globally (Q3/Q4 2006 instead of Q4 2007). Sometimes having a small trained group working on a project is better because it's more focused than having a large group which tends to cause longer discussion, thus delays a project release.
Edited 2006-02-20 16:49