This is probably the best possible course of action at this stage, even if I'm extremely skeptical about the longevity of the fork. The ideal scenario is to com

This is probably the best possible course of action at this stage, even if I'm extremely skeptical about the longevity of the fork. The ideal scenario is to compartmentalize people who can't get along, like you would in a workplace - having two separate forks that absorb each other's changes is not too far off from that. There's another reason too; there's a theory going around that there's a sizable pool of potential competent contributors who are currently staying away from the Node.js project (and other projects) because they feel excluded (and this is commonly used as an argument as to why policies need to be changed). This fork is going to show whether that group of people really exists; if it does, then the fork will thrive, but if it does not, then it will die. I don't think there's much to do about this now other than wait and see it play out. The results of this fork will become obvious soon enough, and it seems that this at least will get everybody off each other's backs for a while. EDIT: Also, let's dial down the vitriol in this thread a little. There's no point in getting outraged over something that'll resolve itself.