|
|
Log in / Subscribe / Register

F/OSS needs to listen to its users to truly succeed

F/OSS needs to listen to its users to truly succeed

Posted Aug 13, 2009 9:12 UTC (Thu) by rvfh (guest, #31018)
In reply to: KDE struggles with feature requests by iq-0
Parent article: KDE struggles with feature requests

That's the root of problem. And all too often, the answer to 'I need this feature' is 'go code it yourself, then'.

There seems to be a lack of 'I want to please my users' kind of reasoning, and it seems developers only write code for themselves (I know I am exaggerating here).

This leads to the feeling that, with Linux, you have to accept whatever is there, and if, say, Bluetooth does not work anymore then tough!

If we really want Linux to succeed on the desktop, I truly believe we'll need to work a bit more for the end users, and less to scratch our own itches.

So yes, "demands" and "free software" are a bit of contradiction, but that needs to change or we'll remain a niche desktop OS, far behind Windows and MacOS...


to post comments

F/OSS needs to listen to its users to truly succeed

Posted Aug 13, 2009 10:13 UTC (Thu) by ikm (guest, #493) [Link]

That's what the article was about, don't you think? As long as you don't listen to your users, you haven't got any problems with their demands. You've got your itch scratched and feel fine. But when you attempt to make "Linux to succeed on the desktop", "work a bit more for the end users", "less to scratch own itches" -- that's where problems start. Because, really, why'd you do that? Are you paid for that? Do you get something off it?

All that stuff you've advised is a must for commercial developments -- but that's because they make money on it. That doesn't work for "for fun/scratch itch" projects. They are just different. And yes, that makes them niche, exactly.

F/OSS needs to listen to its users to truly succeed

Posted Aug 13, 2009 11:21 UTC (Thu) by iq-0 (subscriber, #36655) [Link]

Different groups have different goals. Distributions have a "I want to please the enduser" goal while application developers have a "I have a vision" goal. Okay, a bit of a oversimplification but you get the point.

The "succeed on the desktop" is not really what is on the minds of the respective developers. That doesn't mean that they don't care about the quality of their product, but that quality from their perspective means something entirely different from many of the users.

And the "bluetooth doesn't work" example you give is not really something that I think any maintainer has really said: "tough cookies, go figure it out yourself". But open source developers are limited in their resources (time, money, hardware, ..) and that can lead to a "tough cookies, I can't reproduce the error and don't have (insert resource limitation) to figure it out". And from the enduser perspective that may seem like the same "tough cookie" because they aren't helped by that. But many developers do really care about their project, if only because they are proud of their achievements (when that part fails and the initial itch is gone, you've probably lost the developer).

Even in a not open source setting this happens all the time, because developers have different problems than the customers. Only in those cases there is a clearer relation between demand and (possibly) available resources. Which often results in the customer having to pay more or other things being sacrificed if that is deemed acceptable. Now try doing that math with something you don't pay for (and others don't pay either) ;-)


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds