KDE needs 'contributors, not users'--really?
Occasionally, intelligent conversation erupts online--this time as the KDE open-source community tries to figure out whether it needs users or simply contributors. Jason Harris suggests:
KDE, like many other open-source projects, doesn't really need users at all, whether they are poisonous or not. What we need are contributors: that's the life-blood of our community, what keeps KDE growing and evolving. To the extent that users can and do become contributors, I will grant that we need a userbase as a pool of potential future contributors. But I am simply baffled by any argument that we "need" to have a large number of people that never do more than use KDE.
Given that Harris is apparently not trying to make a living directly from KDE, his view is understandable. It is true that open-source projects flourish when people contribute code, rather than passively digest others' code.
But for anyone hoping to build a business around an open-source project, users are critical (even if one of Harris' KDE compatriots may not think so). Who else is going to buy support/add-ons/etc.?
With that in mind, it's important to remember what will make an open-source project relevant to contributors. The answer? Users. Also, who is going to indicate to the contributors/developers which features are important to satisfy their needs and encourage more users? Users. It's a virtuous cycle. The more users, the more contributors (salaried and otherwise), and the better informed those contributors are.
The real challenge in my view is in figuring out how to turn a significant percentage of users into customers, but then again I'm coming at the question from the exact opposite perspective of Harris. With enough (paid) users, contributors can also be paid/encouraged to participate. Just look at what IBM, Intel, Red Hat, and others have done for Linux.
In sum, I think Harris has missed the forest (users) for the trees (contributors), and KDE suffers as a result.
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.




Your note that KDE4 is not ready for mass consumption and needs more development may be accurate, but that's reflective of your disagreement with those in charge of its release.
Finally, I am in no position to judge Matt's motives with respect to greed, as you have, but being a programmer, I am concerned with crafting good code for two reasons. I take pride in the work I do, but I also want my employer to be happy with my work so that I can be paid well to support my family. Thus, economics factor into my writing software. Surely the same is possible of others that might contribute to KDE.
Akiba - FreakLabs
As an open source programmer, I'd have to say that a programming project not needing users is as absurd as a book author that doesn't need readers. Akiba - FreakLabs
About contributors - I think part of the problem is the entry level required to contribute to some of these projects once they reach a certain evolutionary stage. Sure - I could write a plugin for this/that/other project ... but to improve the core, this usually involves a lot of time, effort and sacrifice most good programmers can't afford.
Either you go to a business model that works - such as paid-for-support or something (time will tell) - or somehow you start requiring companies to put time back into software - something most companies don't do unless they are huge and have an open mind. I don't have the answers, which is why I'm just a pleb ... but time will bring us answers.
Two of his posts about this topic:
http://www.linuxtoday.com/news_story.php3?ltsn=2008-07-02-011-26-OP-KE-DV-0002
http://www.linuxtoday.com/news_story.php3?ltsn=2008-07-01-010-26-OP-KE-DV-0002
He reminds us about this thing called context:
" Here is his summary of his posting, which many KDE4 antagonists seem to ignore:
I'm happy to see lots of people using our software,
and I hope they find it useful and enjoyable.
But in terms of what we *need* for the continued vitality of the project?
We need contributors, not users. "
Skip lines 1,2,3 and line 4 becomes more inflammatory.
The great thing about the blogosphere (hate that word) is that bloggers can take things out of context and it helps getting more page views. Its actually more profitable to do so..
And you realize that the Greygeeks of the world are actually better at this stuff.
Decider is right about developers caring about writing good clean code that works efficiently.
That is what they do. Theyre life is not lived on the desktop but in a confusing myriad ot letter and numbers. Their battles arent the ones of the user.
That I believe is a big problem of any free software project, you cant have developers and engineers on every job. You need marketing savvy, management and people skills.
Those arent the fortes of geeks.
Akiba, I dont know what kind of programmer you are but I have yet to meet a user that has helped me code a piece of software. I can have the test it and run it and tell me what they would like but to program, I dont need them.
Guess what, the engineers who made your car didnt need your input UNTIL the final stages where you get to choose color and options.
-
by Eruaran
July 8, 2008 9:20 PM PDT
- Yes KDE need contributors, NOT users.
-
Reply to this comment
-
(14 Comments)Do you understand what that means in the KDE community ?
Did you not notice that Harris didn't say you need to be a coder ?
If you submit a bug report, you're a contributor.
Brainstorming ? You're a contributor.
Feedback ? You're a contributor.
It may only be a small contribution, but lots of small contributions add up to a very big plus. Whatever little thing you contribute, you're a contributor and THAT'S what KDE needs.
How does a passive user help KDE ?