The important things are 1) does it do what I need 2) is there a good community and 3) is the licensing clear, and compatible with my needs.
If you're someone writing an open source project you're wasting your time if it goes completely unused. So even as an open source developer you're still trying to sell your project to people. You're just giving it to them at a VERY reasonable price.
So what he's saying is all the same "selling a product" rules apply even if it is open source. You can't just throw it out there and expect people to use it
That's putting words into my keyboard. I think most of it is reasonably good marketing advice, and some of the items listed are horrible reasons to not use something.
The title is the problem, really. If it were something like "how to help people find your open source project" it would all fit into place much better.
The others: not so much. When it matures (jQuery) perhaps worrying about branding is in order. But if you are spending your hours making a tool for me to freely use, I'm ok if your design isn't so pretty. And if you don't want to spend much time on Twitter. And ...
As someone whose tried to use open source whenever possible I can tell you there's no feeling worse than using an open source component that's been left for dead
I'd say using a commercial component that's been left for dead is much worse.
The current title reads like: "this is what you owe me if you want me to look at you." Well, ok, but I don't feel that way. I'll use smaller, humbler projects. But I do agree that in doing so I must be prepared for the day that it is no longer updated and the bugs aren't being fixed. I'd certainly feel more comfortable with projects that met most of the lists' criteria, and would be willing to bet more on them for the long haul. But I would still use smaller projects.
Some things (couchdb) seem riskier than others (php), and some very small projects (php-on-couch) seem quite risky indeed. However, I could pick up and go if php-on-couch stalled, I could probably manage if couchdb stalled, but I would be in trouble if php did.
You get what you pay for. And your best insurance against the project being completely abandoned is to have the source code.
Seriously? This would never in a million years have crossed my mind as a reason to avoid using something.
If I'm looking for a heavy duty technical library, say 3D mesh generation or image processing I want someone serious behind - preferably with a full time academic job in the field and some papers, more than a twitter account and a cool logo.
If that's not something you're worrying about, ignore the article.
If open source figures into you company's strategy, as it does more often these days, you need to do it professionally. Yes, even if it is free.
Also, creating a separate page for a project means there will no longer be one page for people to link to. Links will be split across the two pages, and links are important for SEO.
I agree a separate project page is great for branding and makes it look like a dedicated, serious project; but I wouldn't do it for SEO purposes.
Otherwise thanks for the great list of ideas.
Love CanCan btw.
Actually, I do use open source, even so. Its just lots harder than it needs to be.
I do embedded work a lot, and it doesn't have any of that, or its so different as to be unrecognizable.
IP examples: encryption, protocols, file format interpreters, translators. I (and very probably others) need your magic code 'naked'.
By the way, my thoughts on community projects are here:
it's a multipart post, not yet finished.
See: http://blogs.nuxeo.com/fermigier/2011/02/top-10-reasons-for-... for more details.
Open source is not a product. Open source is a community effort. If you don't want to use it - well, it's your problem. No one will shed a tear about it.
If you actually would care about open source you wouldn't be making shitty top10 lists. You would get your ass up and contribute to the project of your choice. If you think twitter is important ... fine! Start a twitter account for that project. Draw fancy icons. Do "SEO". Do something to help. And do something to get rid of that false sense of entitlement.
I will say though, that Wynn does contribute to Open Source - we all do at The Changelog. He also did apologize in the opening sentence of the first paragraph for the "loaded headline" as a hat tip to Mashable for an article they posted two years ago titled, "FOLLOW FAIL: The Top 10 Reasons I Will Not Follow You in Return on Twitter". It's Wynn's character to reference and relate, but I can see how that could be missed. It's hard to "hear" someone's tone in plain text, especially when you are quickly scanning a top 10 list.
This post was more about concrete ways to build community around your code and things you can do to promote your open source projects.
Bullshit. Open source or not, a product is a product. If nobody uses it, you've waisted your time (and the time of the other contributors) building it.