wine patches the black hole of code?

[ Thanks to Tom Wickline for this link. ]

" I'm not criticizing the fact that these patches were rejected, even skimming over them I can see a few issues that could do with fixing before they are accepted. What I do get annoyed about is these people have spent hours of their lives developing something, they've gone through the effort of creating patches and emailing them to the wine mailing list, and the first patch didn't even get a reply! Yes, they could join #winehackers and chase for comments, yes, they could take on board the comments and resubmit, but why? They've already put in the extra effort to get the patches out there, isn't a bit unfair to expect them to jump through hoops to get the patches in to Wine? I think so.

"I know how frustrating it is to get patches into Wine. In fact, of the patches I have submitted I think only one went in first time, and that was only because it was a simple addition to an existing structure. It's taken me 3 attempts to get even simple patches in, this is not encouraging for a developer looking for a project to devote their time to. Even I have just abandoned patches, simply because I couldn't be arsed to go through the loop again for a minor minor thing. So let's break down the actual problems:"

Complete Story

Related Stories:

• Bordeaux 1.8.0 for Linux review(Jul 22, 2009)
• CodeWeavers Announces CrossOver 8.0 for Linux(Jun 22, 2009)
• 3 Ways to Install Latest Wine in Ubuntu 9.04 Jaunty Jackalope(Jun 21, 2009)
• Bordeaux 1.8 for Linux Released(Jun 18, 2009)
• Games on Linux. Say what? Penguspy Beta.(Jun 15, 2009)
• Bug 421: Wine Developers Upset About Maintainer(May 26, 2009)
• Bordeaux Group and MyLinuxSupport signs first reseller agreements(May 21, 2009)
• WINE and the importance of application compatibility(May 17, 2009)