Ollivander
This is a multipart post. See part 3 Just a brief conclusion to my post sequence; the three principles for succeeding at community-driven projects are: * Make it easy for the people to give you their feedback - it's highly valuable. * Listen and reply to people's feedback.
Ollivander
This is a multipart post. See part 2 6. State your missionWhat's your project for? Who should use it? Which platform is designed for? Answer those questions somewhere in your project page. You won't risk people looking for the wrong solution coming to you and asking
Ollivander
This is a multipart article - link to part 1 3. Make it easy to report issues.Yes, your software is got a bug. Never thought about it, didn't you? And here it is. Now, users shouldn't be forced to climb mountains in order to report
Ollivander
There's a lot of buzz about open source software lately. Many projects are supposed to embrace the Bazaar development model, but they really don't, and their leaders just seem to ignore users a lot. This often leads both to wild forking - one new feature, one