Peter Volkov wrote:
1. Our good non-formal policy "if developer touched anything he becames responsible for that ebuild and should fix issues noticed" is sometimes ignored. We see people reacting: you've noticed - you fix. I think such attitude is unacceptable.
Keep in mind the downside to such a policy is that people just ignore problems that are trivial to fix, because they don't have the time to go over the ebuild with a fine-toothed comb. Then, if people get their heads chewed off on -dev if they do miss something that lowers the motivation just a bit more.
Sure, if a dev fixes an ebuild they should give it a once-over to make sure there are no major problems, and obviously they should do moderate testing to make sure it builds and works. However, if I spotted a minor problem with an ebuild that I could fix, and a major problem that I couldn't fix, chances are that I wouldn't touch it at all. Then the ebuild stays in the tree with both problems, instead of one fewer.
I think it all boils down to "we're all in this together." If you see a problem try to fix it, and if you see somebody make a mistake try to help them out. While we do need policies, and policies do imply police, nobody likes the police, so let's try to make that work with the minimum in fuss. A good rule of thumb is whether a dev has left a situation better off or worse off than when they touched something, and in this case I'd have to say that we're better off.
While the good can be the enemy of the best, sometimes the best can be the enemy of the good, and I think that sums up the current situation well.
