Slashdot Mirror


How To Spread Word About My FOSS Project?

An anonymous reader writes "I'm in a bit of a bind with an open source web software project of mine. It's a very small project that I've been developing for over three years. By now it's got a promising feature set, but very few users and virtually no community around it. The problem is that people I have asked to try it refuse to do so because it doesn't have a thriving community. It's an infinite loop: without users, we won't have a community, and without a community, users aren't coming. So, Slashdot, my question is: how can I build a community and help get the word out about a project led by 2 people and with only 5-6 regulars on our forum and IRC?"

63 of 244 comments (clear)

  1. Talk to your users by alain94040 · · Score: 5, Insightful

    1. Developers are king. If you could attract one more developer, your project would stand a much higher chance of success.

    2. Just because you open-sourced your project doesn't mean it's useful to anyone. No matter how much we geeks don't like marketing, you have to think hard about your users: where are they, what do they care about and what do they really need?

    It's normal for all new projects to languish for a while. If you think twitter was an instant success, remember that it had 2 years of null traffic before taking off. Go out and ask users what they want. Think. Then implement. Your #1 potential mistake today: feature creep. Don't think that if only you added this one more feature, the crowds would come. If anything, try to simplify things :-) and start communicating (posting on slashdot is not ideal, you should post wherever your users are, not talk to developers).

    1. Re:Talk to your users by Walker_Boh_Druid · · Score: 3, Insightful

      In the same post you say devs are king, and attracting them is key, then go on to say that posting on /. is a bad idea. Contradicting yourself much?

    2. Re:Talk to your users by Razalhague · · Score: 3, Insightful

      If you look carefully, you might notice that the project is neither named nor linked. It's kind of hard to attract devs that way.

    3. Re:Talk to your users by Bigjeff5 · · Score: 4, Insightful

      You didn't do well in reading comprehension in school, I'm guessing.

      The poster asked about attracting users. MOST of the GP's post was regarding attracting users. Slashdot really doesn't make a very good advertising vehicle for attracting new users, it's a one-shot deal and that's pretty much it. Plus, most Slashdot folks are going to do exactly as he described - they'll say "hey that looks neet, but I don't want to mess with it if it doesn't have a good community", and with only one shot to make an impression you are likely to get pitifully few new users. Getting involved in a general OSS user's forum is a much better idea, as you can build a presence and start attracting users in spite of a lack of community.

      For the exact same reasons, Slashdot is probably mediocre at best for attracting developers. However, getting involved in a good sized OSS developer's forum would be a great place to both advertise to try to attract new developers and to get more advice about getting your project out in the open.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    4. Re:Talk to your users by B'Trey · · Score: 3, Insightful

      It's also kind of hard to answer the question asked without knowing much about the software involved. We know it's a web project of some kind, but that doesn't do much to narrow things down. If it's a web application framework like Rails then promoting it would be a very different task than if it's a blog publishing application like Wordpress. Hopefully, it's not an exact duplicate of some other common open source project, of course. If, however, it does perform the same function as another well known program, particularly a closed source one, you might want to start by listing it on AlternativeTo.

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    5. Re:Talk to your users by timmarhy · · Score: 3, Informative

      spot on. no one wants to commit to using software that will disappear if you get hit by a bus.

      --
      If you mod me down, I will become more powerful than you can imagine....
    6. Re:Talk to your users by mattack2 · · Score: 5, Insightful

      I suspect they purposefully didn't give a link to it or name it, so that the thread wouldn't be perceived as an ad, and would simply be looking for general advice that could be applicable to others.

    7. Re:Talk to your users by bakes · · Score: 2, Insightful

      If you look carefully, you might notice that the project is neither named nor linked.

      That might be to avoid the hordes of slashdorks who cry 'Slashvertisement' at the slightest hint of anything that might resemble marketing/promotion. I think the submitter did the right thing in NOT naming/linking his product, to keep the discussion on the appropriate track instead of being diverted by opinions of how good/bad his program is.

      --
      Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    8. Re:Talk to your users by adamkennedy · · Score: 4, Interesting

      Last time my project got mentioned on Slashdot, I saw around 50,000 additional downloads for that release.

      So even if it's one-shot, that one-shot can still be big.

    9. Re:Talk to your users by Anonymous Coward · · Score: 2, Insightful

      If it's open source, it doesn't matter if the developer gets hit by a bus.

      That's one of the open source selling points.

    10. Re:Talk to your users by Lazy+Jones · · Score: 2, Funny

      no one wants to commit to using software that will disappear if you get hit by a bus.

      We *are* talking about FOSS here, right? You can always fix it yourself if you depend on it. Besides, most FOSS projects "disappear" in the sense you probably mean because the maintainer(s) lose(s) interest. I seriously doubt that developers getting hit by busses is a serious problem for FOSS users.

      --
      "I love my job, but I hate talking to people like you" (Freddie Mercury)
  2. It's simple by sopssa · · Score: 3, Insightful

    Ignoring asking about it on the Ask Slashdot section (which you intelligently avoided);

    Get friendlier with the people that are interested in the project. Not just answering their questions, but actually become a friend with them. Then ask them to do the same to other people. And get friendlier with many of them. It works in real life circles and it works in computer circles - some people are just going to lose interest no matter what you do, so you're better of getting to know as many people as you know (as you're better of getting to know as many girls as possible)

    Spreading word about FOSS project is actually no different than what it is in the real world. Charisma, getting people to work with you and having a reason to do so. We would all like everything to be just on mere technical terms, but it really isn't so. Learning to interact with people the best way goes a long way - in business world, in FOSS world, with girls.

    1. Re:It's simple by SQLGuru · · Score: 4, Insightful

      And some product, no matter how great they are at what they do will never appeal to a large crowd because of the focus. For instance, anyone maintaining a FOSS project targetting left-handed fim-bozzles will only ever appeal to people interested in left-handed fim-bozzles not matter how good of a product your FOSS iLHFB app is. Making friends will help it grow, but making friends with left-handed fim-bozzle enthusiasts will help your project grow even more.

    2. Re:It's simple by humphrm · · Score: 3, Insightful

      Very good point. And I would add one additional suggestion: go to open source conventions. I'm not going to name any, dare I get labeled a shill, but it's been my experience at open source cons that people with very narrow scope tend to run into other people with very narrow scope at these events. If possible, get on the con's speaker list, and talk about your product. People who aren't interested will skip the talk, but then you'll end up with a room where all the attendees *are* interested in your product. Great networking potential!

      Of course, that's just one way to go about it, there are many other valid suggestions here that you should do as well, not just one.

      --
      -- "In order to have power, I must be taken seriously." -Mojo Jojo
    3. Re:It's simple by 0100010001010011 · · Score: 4, Funny

      Last time I got "friendlier" with one of my users I got into a law suit.

    4. Re:It's simple by MrMadnutz · · Score: 3, Insightful

      Last time I got "friendlier" with one of my users I got engaged!

  3. This would have been a great start by stoolpigeon · · Score: 4, Insightful

    If there were any info. on what the project is and where to check it out. (I realize a lot of people would have made snarky comments if that info had been included too. A regular catch 22 -- but this is a great opportunity and you should post a description and link to the project in this thread.)

    Without any specifics I would think most answers are going to be just as generic. Post about it in different message boards, post about it at aggregator type sites (reddit, digg) - use twitter, facebook or whatever else might help people find out about it.

    Who are the intended users? Where would those people be that you might show up and promote your project? Are their user groups that might be a good place to frequent?

    Would a publication/site that deals with FOSS or whatever problem your project solves be interested in doing a write-up? Will they accept one from someone on the project or one of the users?

    If it runs on Linux is it available through the package management systems of the major distros?

    --
    It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
  4. Easy by ducomputergeek · · Score: 2, Funny

    1) Post a message to slashdot
    2) ????
    3) Profit

    --
    "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    1. Re:Easy by BlindSpot · · Score: 3, Insightful

      Nope, Slashdot is actually an exception to the three-phase model, because this is what happens:

      1) Post a message to Slashdot
      2) Get Slashdotted
      3) Spend all potential profits on bandwidth charges

    2. Re:Easy by nmb3000 · · Score: 5, Funny

      1) Post a message to slashdot
      2) ????
      3) Profit

      Except in this rare case the mystery step 2 is easy to identify:

      1) Post a message to slashdot
      2) Include a link to your project
      3) Profit!

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
  5. Tell us what it's called... by hhappy · · Score: 4, Informative

    some of us might be interested in it. You've just missed your best PR opportunity yet!

    1. Re:Tell us what it's called... by Galestar · · Score: 3, Insightful

      Some of us might be interested, other might consider it shameless self promotion. If slashdot was doing front page adverts for every tiny FOSS project, we'd never hear any real news.

      --
      AccountKiller
    2. Re:Tell us what it's called... by natehoy · · Score: 5, Informative

      I disagree. I think he's doing it perfectly.

      He's asked a generic question, without shilling in the article section. That means it's less likely he's just out spamming, because he hasn't identified who he is or what the project is. So he's largely avoided the shitstorm of angry slashdotters accusing him of spamming.

      But in doing so, he's piqued the curiosity of a few of us, and we've ASKED him to post details of his project now. If he does so, that means he's actually spent a few minutes here reading the responses. This marks him as someone who at least isn't doing a drive-by spamming.

      Either very good and sophisticated marketing, or an honest question from a manager of a small project. I can't decide which. But either way, it works, and I'm curious about the project.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    3. Re:Tell us what it's called... by Anonymous Coward · · Score: 3, Insightful

      Some of us might be interested, other might consider it shameless self promotion. If slashdot was doing front page adverts for every tiny FOSS project, we'd never hear any real news.

      So, kind'a like now? :)

    4. Re:Tell us what it's called... by Anonymous Coward · · Score: 2, Informative

      (I'm the anon who submitted the question)

      You're correct. I avoided revealing my identity here because my goal is to learn, not to spam Slashdot.

      I'm sorry to those whose curiosity is ebbing. I'm dying to post a link to the project, but am afraid it would be in bad taste, and I doubt our VPS could handle the traffic.

    5. Re:Tell us what it's called... by dandaman32 · · Score: 2, Funny

      Shit. My sense of vocabulary is fail. Must be this ice cream. I meant "effervescing."

      >_<

    6. Re:Tell us what it's called... by Random+Destruction · · Score: 5, Informative

      By googling his name, the project appears to be. Enano CMS

      --
      :x
    7. Re:Tell us what it's called... by rincebrain · · Score: 4, Interesting

      I'm genuinely curious how you produced an AC's name.

      --
      It's only an insult if it's not true.
    8. Re:Tell us what it's called... by dandaman32 · · Score: 5, Informative

      I was betting on my ability to remember to hit "post anonymously" every time I commented on this thread.
      Note to self: in the future, hit "log out." x_x

    9. Re:Tell us what it's called... by kainewynd2 · · Score: 2, Informative

      I for one am glad you screwed up and didn't log out...

      Seriously... I spent two days last month looking for a wiki with a usable WYSIWYG editor that didn't require stupid hacks...

      Lo and behold, here it is... this is slick. Just installed it in MAMP and I'll be checking this out a little more in-depth tomorrow. Failing major security holes or browser incompatibilities, I may start using Enano relatively soon.

      And no, I'm not affiliated in any way... just really impressed at first glance.

      --
      I just don't get... eh, ugh... never mind. This post wasn't worth the research I put into it.
  6. Re:Post to Slashdot! by rtfa-troll · · Score: 3, Insightful

    I'd agree, except it might help to a) not post Anonymously b) include a link to the project in the posting c) say what it does and why it would be good for us. If you do none of the above, then the reason why your project is unheard of becomes obvious.

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  7. freshmeat by mrflash818 · · Score: 5, Informative

    Try posting to freshmeat?

    http://freshmeat.net/about

    --
    Uh, Linux geek since 1999.
    1. Re:freshmeat by Anonymous Coward · · Score: 3, Informative

      ohloh is another good place to have your project linked. Shows the development activity, which counts to some people when choosing between multiple projects in the same niche.

  8. Re:Post to Slashdot! by tnk1 · · Score: 3, Insightful

    Agreed. Even if 99/100 people say "this project is useless", "you suck as a coder", or they just flagrantly troll you, if you inform even one person who says to themselves "I sure wish someone had an open sourced lolcats generator" that you, in fact, have a feature rich and maturing open sourced lolcats generator, you are still increasing your community by a significant percentage.

  9. Just time... by ZDRuX · · Score: 3, Insightful

    Like some have already said, time is your only enemy. Websites that need numbers to thrive take time. It is like a snow-ball effect, at first you'll have only 4-5 people (probably your friends), but that friend will tell the next person, and you'll be up to 10 users, and so on and so forth. Eventually it'll grow on its own without any need for intervention from your side.

    My bittorrent tracker took probably 6 months before it started taking off thanks to word of mouth. Now maxed out at 8,000 users and that's only because of server limitations. Perseverence and waiting is your only choice at this point.

    And remember, your only chance of making it ahead of others is offering something that nobody does, so ask yourself what *new* are you bringing to the playing field? If the answer is "not much" then I'm afraid you'll have a tough time.

    And like others said, you failed to list your website, which was a big mistake - don't worry about looking like you're trying to use ./ as a way to promote, it's obvious you are - so USE IT!

    --
    The magical number is: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  10. Re:Seriously by Eudial · · Score: 5, Insightful

    You have a crew of nerds here who are all about open source and you refer to your project as "an open source web software project of mine" and are asking for more users?!

    You must be new here.

    It's kinda sad that you didn't put it in the summary, as others pointed out before me, you really did miss out. Good luck getting it in in the comments, everybody who skims the summaries won't even see it...

    If he -had- posted it in the article, 70% of the comments would berate him for slashvertisement. So it's a case of damned if you do, damned if you don't.

    --
    GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
  11. Heh. by lattyware · · Score: 5, Funny

    I like how when there is a slashvertisement, everyone bitches.
    This guy sidesteps, and everyone is complaining because there isn't a slashvertisement. Oh the irony.

    --
    -- Lattyware (www.lattyware.co.uk)
  12. Re:Oh come on... by CannonballHead · · Score: 2, Insightful

    No it's not. He didn't name the product and he even posted AC. You can't get any more "This is not an advertisement" ... unless he's REALLY good at it, and is drumming up curiosity.

  13. Make them want to use your project by AlXtreme · · Score: 2, Insightful

    By now it's got a promising feature set, but very few users and virtually no community around it. The problem is that people I have asked to try it refuse to do so because it doesn't have a thriving community.

    Your project will have to stand on its own merits then and you will have to be focal about what those merits are. Hold talks at conferences, mention it to your friends, keep an updated blog, use FLOSS-distribution sites like freshmeat. If people are interested you will hear from them.

    If that doesn't help and you are sure your project is worthwhile you should investigate in your competition, take a good unbiased look. If there are a couple of large projects with large communities that accomplish something similar make sure you differentiate yourself from them. What makes your project unique and better than the rest? Perhaps those projects have something your project doesn't. A large community may be a plus but it isn't the only reason why users pick a certain project.

    If you can't make your project grow, relax and don't force the issue. If your project is truly worthwhile people will find it and the ones using your project will spread the word. If it doesn't gain popularity you can at least enjoy working on it and take pride in what you accomplish: the FLOSS community isn't a popularity-contest and there is no free car waiting for the one project that trumps the rest.

    --
    This sig is intentionally left blank
  14. Re:Slashvertisement Fail by Razalhague · · Score: 3, Insightful

    So, it's like... an actual question? On "Ask Slashdot"?! Wow.

  15. Open Source Development HOWTO by Anonymous Coward · · Score: 5, Funny
    1. Introduction

      As everyone knows, Open Source software is the wave of the future. With the market share of GNU/Linux and *BSD increasing every day, interest in Open Source Software is at an all time high.

      Developing software within the Open Source model benefits everyone. People can take your code, improve it and then release it back to the community. This cycle continues and leads to the creation of far more stable software than the 'Closed Source' shops can ever hope to create.

      So you're itching to create that Doom 3 killer but don't know where to start? Read on!

    2. First Steps

      The most important thing that any Open Source project needs is a Sourceforge page. There are tens of thousands of successful Open Source projects on Sourceforge.Net; the support you receive here will be invaluable.

      OK, so you've registered your Sourceforge.Net project and set the status to '0: Pre-Thinking About It', what's next?

    3. Don't Waste Time!

      Now you need to set up your SourceForge.net homepage. Keep it plain and simple - don't use too many HTML tags, just knock something up in VI. Website editors like Expression Web and DreamWeaver just create bloated eye-candy - you need to get your message to the masses!

    4. Ask For Help

      Since you probably can't program at all you'll need to try and find some people who think they can. If your project is a game you'll probably need an artist too. Ask for help on your new Sourceforge pages. Here is an example to get you started:

      "Hi there! Welcom to my SorceForge page! I am planing to create a Fisrt Person Shooter game for Linux that is going to kick Doom 3's ass! I have loads of awesome ideas, like giant robotic spiders! I need some help thouh as I cant program or draw. If you can program or draw the tekstures please get in touch! K thx bye!"

      Thousands of talented programmers and artists hang out at Sourceforge.net ready to devote their time to projects so you should get a team together in no time!

    5. The A-Team

      So now you have your team together you are ready to change your projects status to '1: Pre-Bickering'. You will need to discuss your ideas with your team mates and see what value they can add to the project. You could use an Instant Messaging program like MSN for this, but since you run Linux you'll have to stick to e-mail.

      Don't forget that YOU are in charge! If your team doesn't like the idea of giant robotic spiders just delete them from the project and move on. Someone else can fill their place and this is the beauty of Open Source development. The code might end up a bit messy and the graphics inconsistant - but it's still 'Free as in Speech'!

    6. Getting Down To It

      Now that you've found a team of right thinking people you're ready to start development. Be prepared for some delays though. Programming is a craft and can take years to learn. Your programmer may be a bit rusty but will probably be writing "hello world" programs after school in no time.

      Closed Source games like Doom 3 use the graphics card to do all the hard stuff anyhow, so your programmer will just have to get the NVidia 'API' and it will be plain sailing! Giant robot spiders, here we come!

    7. The Outcome

      So it's been a few years, you still have no files released or in CVS. Your programmer can't get enough time on the PC because his mother won't let him use it after 8pm. Your artist has run off with a Thai She-Male. Your project is still at '1: Pre-Bickering'...

      Congratulations! You now have a successful Open Source project on Sourceforge.net! Pat yourself on the back, think up another idea and do it all again! See how simple it is?

    1. Re:Open Source Development HOWTO by keeboo · · Score: 2, Insightful

      The MSN part is troll-ish, some parts are oversimplistic and troll-ish aswell but...

      While I'm a supporter of FOSS software, things like that do happen. There's a great deal of truth in that text.
      Ironically, it also applies to proprietary software. The difference? We never hear about that.

  16. Make it do something useful by takowl · · Score: 4, Insightful

    I've been involved with a project which fitted this description almost perfectly: FOSS webapp which was dependent on a community it never really had. I almost thought the question could be about it, until I visited its page to find that it's being closed down. It may sound obvious, but I think what really did for that project was that it didn't do anything people could already do. Specifically, a large part of its functionality was replicating things that Facebook did, and maybe 99% of its target users were on Facebook. Without a compelling reason to use it, it never really took off, and the developers weren't enthused enough to create the grand new features that had been planned.

    Getting critical mass in the first place is hard. I wonder if there's any stories out there about how Facebook/Myspace/Twitter first got started. As others have said, you'll need to sell it to your friends first, then work at keeping them happy until they're happy to recommend it to their friends. Perhaps focus at first on the non-social aspects of the site, that don't depend on community, then be ready to shift to a more social model once you've got a couple of dozen users. An empty forum is just depressing, but some old-fashioned content is useful even for the very first visitor.

    Oh, and since everyone's busy berating you for not giving the name: well done on not Slashvertising! Although I admit I'm also curious about it.

  17. My suggestions. by Tei · · Score: 3, Interesting

    Have good documentations, screenshots, maybe a video. A good website (cms + nice theme, maybe).
    Then, wen you do big releases, poke the bloggers or news posters about it. People like to read news.
    You can even poke the news-guys if you have something interesting, fun, amazing, to show.

    And wen you give articles to news-guys, make these article very good. avoid spell errors, use your better english, etc.. your text must be perfect. This really help these people, and your opportunities, everyone.

    --

    -Woof woof woof!

  18. Maybe the problem is not the community? by Ekuryua · · Score: 3, Insightful

    Am I the only to think that if a project doesn't get a grip at all it's MAYBE because it is not that useful to people? In my experience, projects do benefit from a community boost, but 90% of the work is still having a useful application that people desire.

  19. The sad fact is... by simaul · · Score: 3, Insightful

    For every successful FOSS project there are
    hundreds of wannabes. Most are ignored, and
    rightfully so. Yours might be different... you
    do have more than just yourself involved.

    But so often one hears the whine, "won't someone
    please join my little project" and there's just
    nothing there worth looking at. Could this be you?

  20. PSST! by TheSHAD0W · · Score: 3, Insightful

    Hey you! Open source developer! This is your chance! Post the name of your project and pretend you posted the original question!

    1. Re:PSST! by Anonymous Coward · · Score: 2, Funny

      It is so small and unused I thought I would be ridiculous... But here come the link: http://kernel.org/
      L.T.

  21. Re:Post to Slashdot! by QRDeNameland · · Score: 2, Informative

    "I sure wish someone had an open sourced lolcats generator"

    cat cat | sed 's/Meow/I can haz cheezburger?/g'

    --
    Momentarily, the need for the construction of new light will no longer exist.
  22. Reduce the barriers by plcurechax · · Score: 2, Informative

    Make it as easy as possible for users to try your software.

    Take the time to create and maintain packaging for major Linux and BSD distributions. Or at least make it as easy as possible for someone to maintain a distribution package of the current stable version.

    Make it easy to migrate to, and if possible, back out of again, from the popular alternative(s). Such as Import / Export functionality from popular commercial software (if there is any). In other words, as easy as possible for people to try your software.

    Improve documentation. Write basic tutorials for with specific instructions for more distributions. Ensure you have a good wiki / FAQ / knowledgebase dealing with installation and usage issues that have been already reported, and keep it up to date with new issues that arise in newer releases. I hate seeing a FAQ for project X that hasn't been updated since the original 0.9 release 3 years ago.

    Of course it has to be useful. Preferably better than the other free (either gratis or open-source / libre) alternatives.

    Does the usefulness of the web software itself increase with an increased userbase? Look at marketing that deals with the network effect. In general, look at IT marketing, consider what would work with your target userbase, and try to go with that. How much do you know about your userbase? Market research is vital, even on FLOSS projects.

    1. Re:Reduce the barriers by keeboo · · Score: 2, Interesting

      Make it as easy as possible for users to try your software.

      Agreed, and here are some tips:
      - Provide a decent and updated documentation.
      - Provide sensible defaults and (if that applies) pre-configured and commented configuration files.

      Take the time to create and maintain packaging for major Linux and BSD distributions. Or at least make it as easy as possible for someone to maintain a distribution package of the current stable version.

      Hmm... It depends.
      Is your software for non-technical end-users? Then it may be a good idea to provide packages for the most popular OSes.
      Is your software for server-like purposes and for a technical audience? If you provide pre-compiled packages, you may end with lots with non-technical people bothering you in your personal e-mail address (no matter how clearly you state that the mailing lists are the proper channel for that).

      If your software is desireable, voluntary packagers will appear eventually (BTW thanks for your work, packagers!).

      (...)

      Of course it has to be useful. Preferably better than the other free (either gratis or open-source / libre) alternatives.

      Does the usefulness of the web software itself increase with an increased userbase? Look at marketing that deals with the network effect. In general, look at IT marketing, consider what would work with your target userbase, and try to go with that. How much do you know about your userbase? Market research is vital, even on FLOSS projects.

      All those are valid remarks.

      If your project is better than the alternatives (or even unique), you have to state that clearly.
      Your potential users must be told, clearly, what for is your project and why it is so good.... and it's a good idea to provide snapshots/examples/whatever showing your software in action to "prove" your claims.

      Well-known projects do not need such - let's say - advertising, so often their websites presumes you know what is that all about.
      But it's not your project's case and you cannot afford such luxury.

  23. Not useful by CAIMLAS · · Score: 2, Interesting

    Your software is likely not terribly useful, difficult to set up, and/or not as useful as something which is easier to set up. It might also be ugly compared to the competition.

    You might also have an unreasonable requirement; eg. Postgresql (not MySQL, etc.) for a backend database on, say, a note/reminder application. That's a bit of a headache to setup. Poor documentation? There ya go - most people aren't intimately familiar w/ every piece of software out there and wouldn't be able to follow the sparse breadcrumbs of documentation. (Just guessing here, I don't know your project.)

    Let me take gxemul, an architecture emulator (ARM, MIPS, Motorola 88K, PowerPC, and SuperH). It's got very limited utility - IE, mainly for nostalgic users, hobbyists, or possibly as a way to make cross-compilation easier (by doing it 'native'). I've used it for the latter two purposes, and it does a good enough job that I got what I needed to get done (mostly).

    As far as I know, it's got a single active developer. The IRC channel has under a dozen users, with maybe 2-3 active at a time max (last I checked). Yet, as a project, it seems to do pretty well.

    Something you might try: packaging your project for a couple distributions and trying to get it added, with yourself as the package maintainer. I know that awesome (the window manager) is packaged in most distros at a reasonably current version, despite its fast paced development (it's under 2 years old, as a project). Having those packages available has certainly helped spread its adoption.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  24. You've got to please yourself by vtcodger · · Score: 2, Insightful

    Look, you aren't doing this for us, you're doing it for you. If you are doing a craftsmanlike job that's not a put down. Write software that pleases you. Make it available to others. If they could benefit from it and choose not to, that's not your problem.

    "But it's all right now, I've learned my lesson well
      You see, you can't please everyone, so you've got to please yourself"

    Ricky Nelson, Garden Party 1972

    That said, a brief statement of what the software does and a link to the project home page would not have been out of place.

    --
    You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
  25. Or ... by Anonymous Coward · · Score: 5, Funny

    Or imprisoned for murdering your wife.

  26. Its called marketing. by jellomizer · · Score: 4, Informative

    The fact the product is Open Source or free will not get any thing out...

    Lets figure out some things...
    The 5C's
    Customer or for your case you end users what is you app targeted for Corporate users or end users.
    Company or your OSS group that has developed the software what are your values why do you want the product to grow what makes your group better then most
    Context what itch are you trying to scratch. Does it solve a problem
    Collaborators who do you need to work with to make your program run. Is it linux only or does it work on windows... Do you need 3rd party tools to run it. Do you have any people who are willing to push your product.
    Competitors Sure you may have some cool new features but are they better then what the other Open Source tools have... Are there closed source application that do the same thing you do. If so how do you defend against any advantages.

    Next is the STP
    Segmentation What is the product the best fit for.
    Targeting Really push to the people the product is the best fit for. If they prefer a closed source solution or a big name you will be wasting your time. However there are other people who want you app in the open source form.
    Positioning make sure you make your product to really show off what it needs to do for your targeted group of people

    The 4P
    Product what is your product what does it do
    Price Sure it is open source and it is free are you going to offer consulting or support services if so how much are you going to charge.
    Place What will be your range you want the product to first go out
    Promotions Well if you are going to do consulting for your product you might as well add some Linux support too.

    These is Marketing 101 in a nutshell.
    Basic marketing isn't trying to trick people into getting your product but finding where people would like your product.

    Sure your product may not have a big following that is ok there are a lot of small software companies to make software to a lot of big players. I myself when I worked as a consultant myself made software for many large companies that was custom for them even if there was Open Source alternatives I created code and documentation for them so the code is theirs and with No strings attached.

    For Open Source tools the trick is to make sure that you are willing to back it up and if fail it is possible for others to pick it up.

    Open Source Projects do die sometimes so do closed source product. However there are people making closed source products and selling them. The fact that it is open source and has a small comunity isn't an excuse. You just need to market the product

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  27. 8. Magic Steps by Tablizer · · Score: 2, Insightful

    1. Put it on Sourceforge
    2. Give it a good intro description
    3. Plenty of screen-shots
    4. Good documentation
    5. Plenty of examples, both very simple and semi-fancy
    6. Make it easy to install
    7. Make sure it doesn't suck
    8. Read and respond to feedback

  28. Beta... by philosiphus · · Score: 2, Insightful

    (After looking at Enano CMS.)
    No one else mentioned this but for utility, as a user, I would also look for:

    • no beta level; there must be production-level version (if you achieved that level already then change the name but it must have all the bugs ironed out for the most common use cases).
  29. Ah-HAH! YACMS! by gdek · · Score: 4, Insightful

    *Now* we know why no one's using your open source project -- because it's Yet Another CMS!

    If you're trying to drive a new project in a space that already has a clear incumbent, you're in for a tough climb.

    If you're trying to drive a new project in a space that already has several clear incumbents, you're in for a *really* tough climb.

    If you're trying to drive a new project in a space that already has several clear incumbents and hundreds of failures, you're in for... ...well, you see where I'm going here.

    I'm sure your CMS is different. It's sensitive and nurturing and really cares about me in a way that those other CMSes don't, and would never throw me out of the car for getting drunk at Andy's party that night. I get it. But when you're competing against the Star Quarterback of CMS projects, you *must* define what is unique about your project, and you must *market* that uniqueness. And you'd better be right, too -- because otherwise, you can forget about getting a date to the CMS prom.

  30. Re:Post to Slashdot! by DrEasy · · Score: 2, Funny

    I'm not joking when I say: I love the idea of a lolcats generator! I'm gonna give this some more thought...

    --
    "In our tactical decisions, we are operating contrary to our strategic interest."
  31. And your project is ...? by mattr · · Score: 2, Interesting

    Just tell us the name already!

    Make a website that is clean and understandable.
    If the project is mature then it should be usable in the real world. Get it used.
    Make articles in newspapers. Get interview with client if they agree.
    Put client names on homepage if they agree.
    Contact blogs etc. about it and post it also on sites like freshmeat, etc.
    Respond lightning fast to queries and monitor online media.
    Write a column or blog describing what you do and new plugins etc. If it is useful people who already trust open source will try it.
    If it is too complex a system maybe that is a problem too. Simple things that are easy to understand tend to get sold quickly.
    Personally I'd be worried about trusting a system written by a tiny team with no real world clients, except as a hobby.
    Maybe you want to tell Wikipedia to update their page to include you in a category list too.
    Make sure all references link to your site. This will raise your google ranking.
    Talk to schools or potential customers and actually install and support it. This is your living right?
    Finally, tell us what the project is in the comments here. Yeesh!

  32. My project seems pretty successful by mrjb · · Score: 3, Insightful

    I run a small project about the age of yours, and it has a user base of several thousand users. It started out as a Linux alternative to a piece of commercial software. I believe the following has contributed to its success:

    - I joined the existing community forums
    - Made sure the software doesn't suck. I started by giving a few distinguishing features that the commercial software simply doesn't offer (data recovery, allowing the use of low cost hardware rather than $200 commercial hardware) giving it an edge over the commercial offering. Many of the distinguishing features were features *I* needed, so others likely did too.
    - Made sure my project was cross-platform; although I started it as a Linux project, the majority of the user base are Windows and Mac users.
    - I went on to make sure my software can do *everything* that the commercial software does.
    - I did set up a website asking for feedback, feature suggestions etc. which is a great source of inspiration for new features.
    - ...and so are complaints about the commercial software.
    - To be fair, the commercial software is no longer being developed (but it's still being sold!), which means by now Windows 7 users are starting to have trouble running it. But in any case, I'm not dealing with a moving target.
    - I never worried about Google, but I did make sure to mention the link to the software on the forum if someone asked a question that the software resolved. Eventually, word of mouth got out and people outside the forum started posting the link as well.

    So basically, rather than building up a new community from scratch, I built on top of an existing one. It's terribly hard to sell a fax machine if nobody else has one; but if there is a community of fax machine users out there, maybe you can build better fax machines than the company that created the market.

    Finally, if nobody hears about your project, nobody will check it out. Why didn't you mention the name of your project or link to it?

    --
    Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
  33. Write an article by aaronbartell · · Score: 2, Insightful

    One of the best ways I have found to get the word out about a free piece of software is to write an article about it. For example, I released a tool called RPGUI in December and I just got done having the second article about it published in IBMSystemsMag.com. You can learn more about the project here: http://mowyourlawn.com/rpgui.html Another benefit to writing an article is that is causes you the software author to go through motions of what a typical user would be confronted with as far as implementing your software. This helps to work out a lot of kinks. HTH, aaronbartell.com