Hacker News Reader

I think the sense entitlement goes both ways. Sometimes maintainers get the wrong idea that their work is above critique because it's open source.

Such that even when presented with reasonable feedback, they balk and snap at the contributor. "Well if you don't like feature X, why don't you GTFO and fork it". For some reason it's okay for contributions to be critiqued but not the projects. Who gave this poor author this wrong idea?

View on HN

Yes, nothing is free, when I start using an open source project I make some assumptions on what to expect from the project. Based on those assumptions I will invest more or less time learning and integrating the project into my workflow.

The problem arise when my expectations doesn't match the project maintainers expectation.

Ideally every project should announce clearly for newcomers what to expect. Will there be be features, how fast will bugs be investigated and fixed, at what cost.

Reply on news.ycombinator.com