[development] How to post bug reports and patches

Greg Knaddison - GVS Greg at growingventuresolutions.com
Thu Oct 30 14:37:40 UTC 2008

On Thu, Oct 30, 2008 at 8:18 AM, Marijn Kruisselbrink
<m.kruisselbrink at student.tue.nl> wrote:
> gave up doing after a couple of months)). So what is wrong with the current
> system that it can take this long?

The problem is that there is a very small set of people to commit
patches.  Those people are busy.  So, they rely on reviews from other
people to help them decide what to commit.  Since there are not enough
people who do reviews, the people who review code get wide respect
from the community including the people that they help the most: the
core committers.  When the core committers see a patch by someone they
respect (like a patch reviewer) the patch is more likely to get
committed because of the respect and trust.

So, it's very simple:
1. To get your patch committed quickly, you build trust and respect
with the committers
2. To build trust and respect with the committers you review other
people's patches
3. Repeat until there are no more bugs


Greg Knaddison
Denver, CO | http://knaddison.com | 303-800-5623
Growing Venture Solutions, LLC | http://growingventuresolutions.com

More information about the development mailing list