Hacker News new | ask | show | jobs
by breton 1381 days ago
Karl Fogel shows a good example how issues like this should be treated: https://github.com/SparkDevNetwork/Rock/issues/5068

Another thing that should not be forgotten is that bug reports are there to contribute to the software. Not for support requests, not for rants, not for personal attacks on the developers, and not to explain them how wrong they are. "This wording exposes you to a lawsuit/might be offensive to certain contributors/is off-putting" would be ok.
1 comments
gray_-_wolf 1381 days ago
> Karl Fogel shows a good example how issues like this should be treated

Didn't this issue (n8n) actually get resolved favorably (open-source -> source-available) while the "how issues like this should be treated" was resolved (by the maintainer) by basically saying "fuck off, we will keep lying"?

link
janober 1381 days ago
Just want to make one thing clear. It did not get favorably resolved because of the way it got communicated, it got resolved favorably despite of it.

Btw. Karl Fogel was also part of the n8n open-source discussion and that was for sure also one of the reasons why it got resolved the way it did.

link