Tomas Fulopp wrote:
To summarize: this is just to show that the answers provided in this thread are unlikely to provide an efficient solution for developers like Markus. We must not be satisfied with such answers and keep searching more effective methods of recognizing and applying results of good coding. And I am sure we'll manage, for this is a marvellous community.
Well, you said it yourself: "it is a fact it is easier and faster to spot problems than to solve them" ...which seems like exactly what you've done here. :) Others have explained the realities of the community-driven development process in a community as large as ours, itemized the constraints and obstacles that exist (by necessity, to keep code quality high) to get patches in, and have tried to help Markus by offering tips to help that have also helped them get patches into core. If you have better ideas on how to manage the process more efficiently, obviously we'd love to hear them.