I'm (obviously) not a dev but contribute some from time to time. Not much more can be said than has already been stated, but since (I believe) this thread started out asking for input, I just wanted to toss in a negative vote. Essentially I don't see it solving any problem and stepping on the toes of current changes (-project for instance). As of late, it seems more traffic has been generated due to non-development threads such as this than any other topic -- take that as you will.
As for some very brief points, I have a few: * Whether it's intented or not, the negative perception being projected on non-devs will be there. Call it what you will, but essentially they'll be outsiders. * This original thread seems to be an attempt to lessen damaging posts to -dev and yet does not address the possibility that these posts may come from current devs. Chris Gianelloni seems to have modified the thread to include dev moderation with the possibility of delays being applied to them via policy. * While no delay duration has been set, I think one of the problems here (again) is perception. Currently it's the idea of quick feedback from the source. * This sounds like a boring, mundane, time consuming task to place on all developers. As with most things, only a few will take the time to do their duty as per policy dictates. This either means we'll have developer-devs doing paper work or non-developer-devs in a developer position doing paper work -- an overly simplistic view. -- [EMAIL PROTECTED] mailing list
