Matt Asay on the Status of OSS 86
OSS_ilation writes "An interview with OSBC director Matt Asay at SearchOpenSource.com gives some insight into where open source software (OSS) has been, is today, and where it hopes to be in the future. A common trend identified by Asay in the interview is that OSS has become very profitable. Asay also touched on the hot-button issue of where the GPL is headed, as well as how open source vendors shouldn't let high download rates give them a big head about the real validity of their projects."
Summation (Score:4, Insightful)
If people download it, it does not mean they are using it.
Funny, but I already knew that. Now I just have to find something people will use besides Video Fish
Re:Summation (Score:2)
But who is making the money, the distributors or the developers?
Re:Summation (Score:1)
Money people have been robbing idea people for centuries, while I think it is wrong, just consider that William G BOUGHT DOS, he did not code it.
Re:Professionalism in the open source world. (Score:2, Interesting)
You may be taking the wrong lesson from that exchange.
Re:Professionalism in the open source world. (Score:2, Informative)
All moderators: nothing CyricZ ever posts has any real content. All of his posts are made to generate responses - sometimes he comes across as reasonable, at other times as needling and nosy, but always content-free. Please mod him -1, Troll.
Re:Professionalism in the open source world. (Score:1)
Re:Professionalism in the open source world. (Score:1)
I do not feel that the users (or anyone else in the community for that matter) has any right to expect ANYTHING from open source developers. Indivuduals who are contributing are contributing because its a project that interests them, they see (and can help) fill a need, or they are just plain bored. The bottom line is that
Re:Professionalism in the open source world. (Score:4, Insightful)
There's a minimum standard, and that particular developer sunk below it in that particular instance. Intentional or not, it did reflect poorly on the entire project, including all of those individuals who have been extremely helpful in the past. If anything, such insults are more disrespectful to those with the KDE project who have helped built its fantastic image, rather than to the person the insults were directed towards.
Re:Professionalism in the open source world. (Score:2)
I think you will find that if you show respect, you will be given respect. If you behave like a spoilt child, you will be treated with contempt.
I'd rather see that that some pretend subservience.
Re:Professionalism in the open source world. (Score:2)
Re:Professionalism in the open source world. (Score:2)
I think you should take a long hard look at your understanding of what respect means.
Re:Professionalism in the open source world. (Score:2)
This is a fairly 'closed' environment. Anybody who actually reads it, knows whether or not they will use the software regardless of how somebody rants/raves about it.
If that weren't the case, we'd ALL be using Macintosh, playing Nintendo and sleeping with Real Dolls.
Re:Professionalism in the open source world. (Score:2)
Re:Professionalism in the open source world. (Score:2, Insightful)
If you follow that particular discussion back far enough, you would clearly see that that KOffice developer was incorrect with respect to his basic points. Follow it forwards and you'll see him blame his inappropriate beh
Re:Professionalism in the open source world. (Score:2)
Note your use of the word 'potentially' right behind 'misleading' when you claim that the developer who wrote the open letter made a 'potentially' 'misleading' comment.
Your claim that he is in any way obliged to consider the potential ways his comment could be misconstrued is incorrect.
In this world, if you don't find his statement professional, you don't have to do business with him. The extent to which businesspeople co
Re:Professionalism in the open source world. (Score:2)
The fact that it's moderated +5 shows that intelligence is a quality that many users of open source software fail to possess. I'm not necessarily calling you out as stupid, I just liked the flow of your original sentence and chose to recycle it.
Now, that doesn't surprise me in a way. The community itself has academic roots, and many members do not have the experience necessary to unde
They know professionalism at McDonalds. (Score:2)
Re:They know professionalism at McDonalds. (Score:2)
You have never contributed anything to KOffice.
As far as your claim about professionalism, in my professional experience, I have been treated rather rudely by support people on many occasions, but only during e
Re:They know professionalism at McDonalds. (Score:2)
And it sounds like your "professional experience" has been marred by a complete lack of professionalism. I would hope that you have a good idea about how damaging a lack of professionalism can be, whether it is a doctor, a businessman or an open source developer who is lacking such skills.
Re:They know professionalism at McDonalds. (Score:2)
Yes, in the open source world the users are the equivalent of business customers. That cannot be denied.
Wanna bet? How about this...I deny that the users are the equivalent of business customers.
Doctors, businessman, and open source developers are all entitled to any number of reasons for doing what they do. Money can be one of them, self-actualization can be another, education still another. Professionalism is a requisite for maintaining business relationships (and many others). An open source deve
Re:They know professionalism at McDonalds. (Score:2)
Re:They know professionalism at McDonalds. (Score:1)
Re:Professionalism in the open source world. (Score:1)
CC.
Re:Professionalism in the open source world. (Score:2)
its basic economics, see no evil, hear no evil, speak no evil, as long as one get what one wants.
Re:Professionalism in the open source world. (Score:1)
Re:Professionalism in the open source world. (Score:2)
Re:Professionalism in the open source world. (Score:2)
That is roughly as useful as reviewing the professionalism of "people", which are full of assholes. You trust those you do business with, you don't care that there are also conmen pretending to be businessmen. If he's being like that toward
Comment removed (Score:4, Funny)
Re:Professionalism in the open source world. (Score:1)
Re:Professionalism in the open source world. (Score:2)
Are you still sore at being called a blathering idiot because you spouted off on a subject you knew nothing about and got called on it by someone who did?
If so, then I agree with him, you're a blathering idiot ;-)
Justin.
Snort and Nessus (Score:4, Insightful)
Re:Snort and Nessus (Score:2, Interesting)
There's a difference between OSS and FOSS!
Re:Snort and Nessus (Score:3, Insightful)
My answer tends to be if you plan to make most of your money on support, training, specialized implementations, setup, etc then you've got a chance. If the only thing you're bringing to the table is the software itself, then opening it doesn't make a lot of sense.
I sort of walk a line of being a buisnessperson and an open source advocate.
Re:Snort and Nessus (Score:2)
Re:Snort and Nessus (Score:2)
Re:Snort and Nessus (Score:5, Interesting)
I really hope the Gnessus project rethinks their name, as a fork they should really try to take a different name so as not to confuse users. Also, I'd hate for this to cause trademark/copyright issues down the road...
Re:Snort and Nessus (Score:1)
Apart from which, Renaud was never exactly a model project leader. One reason they didn't get many contributions was because those they did get were routinely ignored - like the bug in gdlib which produced broken piecharts in the HTML output, or caused
Re:Snort and Nessus (Score:2)
That's laughable. Do you feel that Microsoft has been spitting in your face too?
Re:Snort and Nessus (Score:1)
Of course they are spitting in our face. Remember, this is slashdot, isn't it? :)
Re:Snort and Nessus (Score:2)
Re:Snort and Nessus (Score:2)
That's my point, if the community had actually contributed in a meaningful way, it wouldn't be Renaud's software, it would be community's software. I don't understand how you can take it as a personal attack that he personally changed the license for software that he personally wrote. If anything, the community spit in his face by not contributing to his project, atleast by your logic anyway.
Re:Snort and Nessus (Score:2)
Re:Snort and Nessus (Score:3, Interesting)
What kind of help did these people provide? Presumably if it were code, they would have something to say about Nessus going closed source.
Re:Snort and Nessus (Score:2)
Not a lot, apparently. For those who didn't read TFsummary on the subject the other day, the primary reason for closing the source was that keeping it open was gaining little benefit, while supporting those directly competing with the company offering it.
Re:Snort and Nessus (Score:1)
Re:Snort and Nessus (Score:2)
A Lesson for RIAA ... (Score:4, Insightful)
Re:A Lesson for RIAA ... (Score:1)
Same for software.
Source of revenue...? (Score:5, Insightful)
[I did RTFA, though it's entirely possible I missed something.]
Mr. Asay did not clarify the distinction between revenue from product sales and revenue from support and other services. He mentioned Red Hat as an example of an OSS company that is making money, but he didn't indicate how much of that money came from selling RHEL and other products vice the consulting, etc. that RH also offers. He alludes to it briefly when he says "OSS has trended toward examples like the Red Hat Network and the MySQL network" but leaves it at that.
This is not a slam on Asay, btw; it's just something I thought would make the article more useful.
Matt Asay's credentials and achievements. (Score:3, Interesting)
Is he a master contributor such as Bruce Perens, or is he more of an Eric S. Raymond?
Re:Matt Asay's credentials and achievements. (Score:5, Informative)
Before Novell, Asay was General Manager at Lineo, an embedded Linux software startup, where he ran Lineo's Residential Gateway business. Asay earned his Juris Doctorate degree at Stanford Law School, spending two of his three years studying software licensing and innovation, and specifically the GNU General Public License, under Professor Larry Lessig.
http://conferences.oreillynet.com/cs/os2003/view/
Re:Oracle (Household Name) (Score:5, Funny)
Re:Oracle (Household Name) (Score:1)
hobby computing (Score:2, Interesting)
Re:hobby computing (Score:3)
I'd love to know what experience you have in the field. Not to mention what you're smoking, because I've got news for you: the professional caliber tools are still being written by people who do it for a living. Just because they work on some of those tools in their spare time for their own reasons doesn't make them hobbyists. At the end of the day, they are st
Re:hobby computing (Score:1)
4 years isn't a long time, but it would feel like it if I didn't like wh
Re:hobby computing (Score:1)
*My* belief is that there is a place for commercial programming/proprietary systems AND open-source programming. Just because something new comes along doesn't mean that the old thing automatically goes away.
Re:hobby computing (Score:2)
Bullshit. There is a lot of annoying software development work, and only some of the parts are really fun to do. Take GUI development or graphic design for example: Why do the best programs often have a poorly designed GUI? Why is there no open source GUI? GUI programing is boring. Development of module tests is boring. Developing of graphic for computer games is boring, thats one reason there are only very few open source 3D games li
Re:hobby computing (Score:1)
There are other perceptual issues that may be more important.
Quality: who wants to work on something if they think it will be 2nd rate?
Recognition: who wants to work on some little project that nobody else uses, or even knows exists? Who wants to contribute to a monster like OpenOffice, Mozilla or X11 and be recognised on
OSS has been profitably for very few (Score:4, Insightful)
When more than a select few companies (only three listed) prove to be capable of pulling a profit, then I'd call it a trend. But considering that most open source development teams pursue their software with little to no financing, it's far too early to even call this a trend. I'd call this the beginnings of a foundation that may begin to include other viable open source products.
Re:OSS has been profitably for very few (Score:1)
Re:OSS has been profitably for very few (Score:4, Insightful)
Every business has pitfalls. This one just happens to have some weird ones.
OSS (Score:1)
Isn't this a lot like... (Score:2)
Seriously though, if corporations can't be trusted to be objective about their own products/ideologies then why would we immediately decide that we should take to heart the word of someone who is clearly pro-OSS regarding the state of OSS profitability? Following that, where do we look for an objective opinion these days?
Granted there are a few key profitable OSS creator/providers, but in the same breath, I'm sure there are many, many more that fall on their faces and drown
Are they profitable? Profit != revenue. (Score:1)
This is yet another case of someone claiming a company is profitable by looking at their revenues. Meaningless.
Also, MySQL (I know less about RedHat and JBoss) has dual licensing, and I'm sure their product revenues come entirely from the non-GPL side of the business. Their services and training revenues may come from both. Where their profits come from, if they have any profits, is unclear.
To my wa
Re:Are they profitable? Profit != revenue. (Score:2)
Exactly. And RedHat has per-seat licensing. JBoss is licensed under the LGPL. Their business model is support, which also means that the product (last I checked) is not well documented unless you buy support. I can see where they're coming from, but it's pretty obvious that they're defrauding the "Free Software must have Free Documentation" dictum.
So,
Re:Are they profitable? Profit != revenue. (Score:1)
Open source is an even smarter idea, especially for RedHat. You can get programmmers to work on your product without paying them. The GPL takes in one big step further: You can even get