22 Apr
2005
22 Apr
'05
9:33 p.m.
A decision to either accept or drop a patch must be clearly so. We cannot expect that Dries be the judge of every patch, nor can we accept a few +1 and a few -1 to be the final word. There has to be a clear Yes or No on a patch, and if No, we have to say why No clearly, and whether it is the functionality that is the issue, or the implementation (user interface, coding, security, ..etc.) This has to happen in a speedy manner, and not drag on till we have 100+ patches pending.
Once again: either I am completely in misunderstanding, or the things we are talking about are already in place. I always received clear reasons for the numerous rejected patches I submitted, and I also see that rejections do get reasons on other patches. Goba