A merge is someone who seeks to go with the flow, usually sacrificing ones individuality and integrity in doing so. When someone has a stance on a controversial issue but is silent when around a group with opposing views, that person is being a merge. Also applies to non-serious and humorous situations such as wearing the same outfit as someone else, even if on accident. One who does not think for themselves. Effectiveness of the term "merge" is increased when proceeded by a expletive.

By now, if you’re part of the Ruby programming community, you’ve probably heard of the proposal to rename RuboCop and the unpleasant events that followed it. I really struggled with coming up with a name for this article, as there are many topics I wanted to touch upon (e.g. the burden of OSS stewardship, being respectful and adhering to the norms that once defined the Ruby community, creating a safe collaborative environment, the final decision about the name, etc), but I’m quite limited in time right now. This generic title is the best that I could, but I hope you will forgive me and focus on the content instead. Once again I got reminded that naming is (very) hard. I don’t really want to go repeat/retell everything that has transpired. The GitHub issue and the surrounding Twitter conversations should give you a good idea. There’s also a nice summary, written by Tim Riley that you can peruse. The purpose of the article you’re reading now is to provide some closure for that topic and a path for us to move forward.…