Giving up on Ruby packaging

Re:Giving up on Ruby packaging by gwern on Sunday January 02, 2011 @10:32AM (#2060149)

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 - "

"FORK IT!"

[ Parent | on HN ]

Re:Giving up on Ruby packaging by dudus on Sunday January 02, 2011 @04:36PM (#2061122)

It's very true. And if you decide to fork it than that's what you hear:

"OMG, YOU CAN'T FORK RUBY. ARE YOU CRAZY? THAT WOULD BE TERRIBLE."

[ Parent | on HN ]

Re:Giving up on Ruby packaging by jamesbritt on Monday January 03, 2011 @01:43AM (#2062389)

    It's very true. And if you decide to fork it 
    than that's what you hear:   "OMG, YOU CAN'T 
    FORK RUBY. ARE YOU CRAZY? THAT WOULD BE TERRIBLE."

Or not:

http://pragdave.blogs.pragprog.com/pragdave/2008/12/forking-...

[ Parent | on HN ]