It happens although I'd like to believe it's rare. I perpetrated the most glaring example of patch refactoring I've ever seen. The scenario: - Original maintai

It happens although I'd like to believe it's rare. I perpetrated the most glaring example of patch refactoring I've ever seen. The scenario: - Original maintainer's module code totally ignored the code style conventions for the larger project it was a part of. - Module maintainer had been dragging heels on a raft of bugfixes, module stuck in beta limbo for six months. - Boss says we need this feature (cleaned up and stable) in our codebase by the end of the month. My play: I refactored the codebase to meet larger project coding style standards, patched every bug in the issue queue, added a suite of unit tests and submitted the entire thing back to the maintainer. Maintainer's play: The maintainer opted to reject my patch on the grounds he preferred his personal coding style to the project standards. Endgame: I promptly re-rolled the patch as an addition to another related module, got the code committed to that project, posted an issue to the original maintainer's queue indicating his module was deprecated. Last time I checked in dude's module was still buggy and he was taking flack from several people involved with the larger project for being a cowboy with the coding standards.