Making It Easier To Start Working On Bugzilla

[Colin Ogilvie]

On Tue Dec 20  9:16 , Jochen Wiedmann <jochen.wiedmann at gmail.com> sent:
>That's, IMO, not the point. The question is, whether I have to push a
>patch ("against" the reviewer) or whether the reviewer pulls the
>patch. Besides, if a person has such a large ego, that he or she is
>unable to accept that a projects standards require some changes, then
>he or she should possibly better work on a standalone project and not
>in a team.
>
>To me, Max approach (contributors guide), and yours ("Tell us if you
>don't mind ...") are basically the same thing over and over again. You
>create bureaucratic structures. But  bureaucreatic structures are also
>limits for new developers. In other words: Your attempts will fail.
>(At least, that's my opinion.)
>
>I wholeheartly support your concerns for quality. But isn't that
>exactly the reviewers job? If he does pull a patch in, applying
>necessary changes, isn't that enough for quality? If it is not, then
>he possibly should stop review.

Personally, I'd rather that if there was a problem with the patch (other than say a minor typo 
that could be fixed on Checkin) that I (as the author) got the opportunity to fix it, rather than 
the person reviewing it had to.

What I think would be more useful is that you didn't have to wait weeks / months for reviews, 
sometimes but that could be partly what Max is trying to work towards...

Colin