Telling someone to FORK IT is only useful if the maintainers are so incredibly incompetent or toxic that even accepting the massive penalties of a fork (especially massive for huge commercially popular projects) one is better off with the fork.
Nowhere else. I don't want to live in a world where this is considered an acceptable response to every small and big criticism or suggestion for improvement:
"Hey, maybe we should remove that dead code."
"IF YOU DON'T LIKE DEAD CODE, FORK IT!"
"Have we considered moving to Git from our crufty old CVS?"
"IF YOU DON'T LIKE CVS UP, FORK IT!"
"Docbook really isn't very easy to contribute doc fixes to; I was thinking about rewriting our manual in Markdown since it's really not that complex a document - "
Nowhere else. I don't want to live in a world where this is considered an acceptable response to every small and big criticism or suggestion for improvement:
"Hey, maybe we should remove that dead code."
"IF YOU DON'T LIKE DEAD CODE, FORK IT!"
"Have we considered moving to Git from our crufty old CVS?"
"IF YOU DON'T LIKE CVS UP, FORK IT!"
"Docbook really isn't very easy to contribute doc fixes to; I was thinking about rewriting our manual in Markdown since it's really not that complex a document - "
"FORK IT!"