> we (luckily) lack the personalities to just tell people to fuck off and die in a ditch, like some other project does
actually, I think you (as a project) are doing a pretty good job of getting that exact message out.
This article is one of the very few items that goes the other way.
Not accepting patches because they don't agree with your vision for the project is within your right (and your responsibilities for that matter), but you can't do that and then complain "why don't they just send patches" when they fork your project.
Preventing a fork is at least as much the responsibility of the people running the project (thorugh the process of accepting outside viewpoints and expanding the scope of the project when patches are supplied) as it is the responsibility of the people who start the new fork