How community based development can blow away commercial efforts

    sequitur's picture
    2003
    30
    Jul

    Hi everyone,

    It's fun to have this platform for developers and so I thought I'd put forward
    an idea I've been trying to promote for some time that seems to not get much
    traction in the community. Often I get a request that reads like can you add
    auto completion support for [your favorite scripting language here]?
    I
    dilligently reply "I don't actually use that language and we have a policy
    that these must be done by people who use them and can test them. However Quanta
    is set up so that users can add a language using XML."
    Now, please allow me
    some small degree of indulgence here... but isn't it weird that given these facts

    • The program was free
    • XML should be part of a web developer's toolbox and no big deal
    • The idea of "community" means you'd think people would be both
      proud and anxious to do their part

    Yet it is maybe one in four or less that will finally step up and put a few
    hours into what is essentially making a tool their own. I'm not really surprised,
    but I can't say I'm still not dissapointed.



    Here's what really gets me. I talk about having the best tool anywhere for web
    work and I think a lot of people are excited about that. We have a handful of
    C++ developers actively working on Quanta and the vast majority of the code is
    written by Andras. More is gradually happening in community involvement and I'm
    working on my C++ skills for various reasons, not the least of which is that I
    feel I need to because Andras is so swamped. Then there are some people that
    feel that even being at the bottom of the Bugzilla top 100 and all we do, that
    we still have not offered enough support because we don't have a feature supported
    that is used by less than 5% of developers. I'm not complaining, but I am making
    a point here.



    How do we beat larger and more established developer teams? Granted KDE
    gives us advantages, but that only goes so far. What if we could turn this
    around and exceed the development efforts of any commercial product?!
    In fact
    this has been our plan, to involve the community in making templates, adding
    language support, doing scripts, creating Kommander dialogs... Quanta is
    so extensible that a major upgrade could be done with no C++ at all!
    This
    would be a dangerous strategy for commercial ventures. What if we
    involved the community on that level?




    Clearly this is the key. I figure maybe 1 in 10 to 1 in 20 people who use Quanta
    would actually download and compile the source. We ran 35,000 downloads on a
    major version in the 2x incarnations on Sourceforge. That would mean 350,000 to
    700,000 users almost two years ago before we became part of KDE. Here's a question
    for every user... "Do you see yourself more as a member of a community or a
    consumer, based on your mentality and actions?"
    It's an interesting question.
    I believe the biggest challenge of community developed software is that people
    are still operating on consumer conditioning in a community environment. If you
    observe many critical comments I'm sure you'll agree. The really good news is
    this... If we have over a million users and only 1 in 10,000 "get it" we
    can easily produce the most amazing tool ever...
    but right now only a handful
    of people get it. I regret to say that not 1 in 100,000 are on board
    with this yet
    , but I think we're doing a little better than 1 in 1,000,000.



    I remember thinking it was special to be one in a million, but I think we must
    be missing some special people out there who just haven't heard yet. How about you?
    Don't know C++? Neither did I, but you don't have to. Don't have time? Who does?
    We all have 24 hours in a day and we all have to make time. Last year I got called
    for jury duty. Did I have time? No. It's just part of being a citizen in a
    community. What will you do for your software community this year?

    Comments

    Comment viewing options

    Select your preferred way to display the comments and click "Save settings" to activate your changes.
    arden's picture

    Open for Job Postings

    I can post to the job board at some of my sites and see if I can actively recruit people for job.

    Canada
    Edmonton
    Hamilton

    datschge's picture

    Communities

    Hi Eric, nice to see you here :)

    I'd like to emphasize that's the talk about "the community" is misleading, as there are many isolated active users and isolated communities. Many users are not aware of existing places to communicated with others about their favorite software, many other users who found some place to communicate, like the mailing lists, kde-look, kde-forum, dotty, this place, all the local translated KDE sites with their own versions of news and forum pages, are not necessarily aware of even more direct ways to get involved. This results in a widely spread out community which isn't united at all and thus isn't exactly in the most effective state for getting direct feedback of any kind directly to the projects.

    In my opinion if you want to get more helpful and direct feedback you'd need to promote bugs.kde.org which has a quasi monopoly on wishes, bugs and crashs reports and also has a nice interface for attaching own files and patches. One way to promote it is to move KBugBuster to kdebase, extend it with an easy "Create new wish/bug/crash report" wizard and integrate it closely with the apps (more than the currently used "Help > Report Bug..."), in a way it is less a hassle than the current online wizard but results in more useful reports.

    datschge's picture

    Re: Communities

    I don't think I missed the point. As I said before bugs.kde.org can not only be used for "passive" stuff like reporting wishes, bugs and crashes but also for contributing files and patches. The latter is just by far not as emphasized even though bugs.kde.org is, due to its centralized database structure, much more appropriate than any mailing list and community forum. For example there are many open reports containing patches potentially supporting the developers. Don't limit bugs.kde.org's use to some one way services but make use of its advantage as a single central meeting point by luring additional contributors to there instead letting them confuse themselves on whom to contact in whatever other forum they are.

    Comment viewing options

    Select your preferred way to display the comments and click "Save settings" to activate your changes.