Slashdot Mirror


Making an Open Source Application More Successful?

morphex asks: "I've written an application for information and task management called the Issue Dealer that has hundreds of users, many of them very satisfied with how it works. However, new user growth has been slow, and there's not much of a community surrounding it. What can I do to encourage wider use of the application, and what can I do to get more developers interested in development and bugfixing? In short, what's missing in this picture to make it an Open Source success story?"

3 of 43 comments (clear)

  1. Do as you have just done. by suso · · Score: 5, Interesting

    Well, it does help to post a question about it to "ask slashdot". I did the same thing 3 years ago with my num-utils programs. After that, I definately saw increased usage and it was added to a few Linux distributions. If you're lucky, the same will happen to you.

  2. version number by ianturton · · Score: 5, Interesting
    If you bump your version number to 1.0 you may well see take up increase. We certainly saw that with GeoTools Version 1 never got beyond 0.96 beta. When wee restarted with version 2 we decided to bump the version number regularly and are now at 2.2.0 and 2.3.x. Usage certainly went up

    Ian

  3. Open Source It (for real) by mysqlrocks · · Score: 4, Interesting
    What can I do to encourage wider use of the application, and what can I do to get more developers interested in development and bugfixing?

    First, check out the book Producing Open Source Software, I found it to be a very informative read. As a starting place, your website needs a little help. It's a little bland but that's not the big problem. It needs to be obvious right-away how I, as someone interested in the project, can get involved. You have the mailing list info which is a good start but a look through the archives proves to be quite lacking activity. Your three target groups are end-users, hackers, and developers. How would someone start "hacking" or just playing with your software? Give them some documentation. What is the process for becoming a developer? Where do I submit patches, how do I get commit access to the repository? Where do I submit bug reports?

    You need to also ask yourself if you're really ready to release this as an open source project. I don't mean literally under an open source license, like you have done. I mean, are you ready to let a community of developers and users take control of your project and take it in directions you may have not considered? It's been your baby so far (from what I can tell) so this could be quite a change for you but the rewards could be great.