Hacker News Reader

Well, let's call it not "feature list" but "specified vision statement" and then it should have that. It should be quite clear from the main README and the main website what distinguishes this project from others. Otherwise it's quite likely that such specification doesn't exist and goals are unclear, which usually means bloated blobb of unfinished 10 million "features".

View on HN

There is a milestone system setup on github which tracks when features will be introduced into master and such, so I wouldn't call it a lack of a vision statement.

I don't think a vision statement is necessary either since I'm a fan of developing software primarly for dogfooding, fixing problems you have is probably a good way to improve the software for others.

It isn't though. People will make stupid demands, not because they are stupid, but because they don't incorporate previous decisions taken and they don't incorporate how their desired solution affects other users of the whole system. Last but not least having a 1000 feature blobb doesn't help anybody.

That doesn't mean that the maintainers of a community fork will have to follow every demand of the userbase.

Reply on news.ycombinator.com