NEW Packages process

[Scott Kitterman]

On Wednesday 16 April 2008 08:06, Daniel Holbach wrote:
> Stefan Potyra schrieb:
...
> > Having recipes, how to solve a problem is imho orthogonal to the question
> > of reviewing. It's good to be able to point people to these, if they have
> > questions on how to do it, but in my experience, that's not the problem
> > when reviewing a package.
>
> Why don't "reviewing tips" help?

Because the problem isn't reviewers not knowing how to solve the problem, the 
problem is that reviewers don't always look for the right things/know enough.

Even the Debian NM process isn't enough to ensure people know enough to get 
all aspects of a package correct.  Multiple reviews are needed.  I don't 
think they are a cause of slack reviews.  I don't think people advocate 
packages thinking someone else will catch any problems.

I'll say again that I think we ought to require MOTUs to get another MOTU to 
review their new package prior to upload.  I've certainly always done it.  It 
has long seemed and odd hole in our policy to not require it.

Scott K