Top ten reasons why I won't use your open source project
thechangelog.com
Top ten reasons why I won't use your open source project
1–10 of 36 posts
Re: Top ten reasons why I won't use your open source project
#2#1,2, and 7: Yes.
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 ...
Re: Top ten reasons why I won't use your open source project
#3My, that comes across as a bit preachy. You get something for free. So what if it doesn't have a twitter account associated with it.
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.
Re: Top ten reasons why I won't use your open source project
#4My, that comes across as a bit preachy. You get something for free . So what if it doesn't have a twitter account associated with it. 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.
It's great feedback for people who are interested in attracting more people to their project, which is clearly (to me, at least) the manner in which it's intended.
Re: Top ten reasons why I won't use your open source project
#5#1,2, and 7: Yes. 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 ...
I don't think the issue is as much about design as it is about seriousness. Having a homepage for the project, spending some time or money on design and reaching out to the community shows you're committed to the project which will get others to commit. That's the best insurance a user can get against the project being completely abandoned one day.
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
Re: Top ten reasons why I won't use your open source project
#6My, that comes across as a bit preachy. You get something for free . So what if it doesn't have a twitter account associated with it. 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.
Not intended that way, in fact, that's the purpose of the article - how to build that community. Even if the code is good, it takes time and there are practical steps you can take.
Re: Top ten reasons why I won't use your open source project
#7My, that comes across as a bit preachy. You get something for free . So what if it doesn't have a twitter account associated with it. 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.
It's great feedback for people who are interested in attracting more people to their project, which is clearly (to me, at least) the manner in which it's intended.
It's pretty good marketing advice for many things. "How to market your open source project" might be a nice, less linkbait title. I guess it worked, though:-/
Re: Top ten reasons why I won't use your open source project
#8Ready for linkbait, I read the article and...it's good!
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.
Re: Top ten reasons why I won't use your open source project
#9My, that comes across as a bit preachy. You get something for free . So what if it doesn't have a twitter account associated with it. 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.
Perhaps but he's preaching against the very attitude you have which is "you're getting this for free so you'll take what you get and like it"
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
Re: Top ten reasons why I won't use your open source project
#10Add: your source has so many accidental dependencies that its agony to extract the bit I need.
Actually, I do use open source, even so. Its just lots harder than it needs to be.