NEW Packages process

[Siegfried-Angel]

2008/4/16, Stefan Potyra <stefan.potyra at informatik.uni-erlangen.de>:
> hm... that's tough. Well, there is lintian, but not all of lintian output is
>  always correct for each source package (that's why you can override parts of
>  it). So the tricky part here is: What to do with the result of a package
>  checker? (should it reject the package, which would be wrong for some, should
>  it leave a negative reviewing comment, same problem, or should it just be
>  informational, which is what we have right now, though not really presented
>  very nicely).

I'm thinking about adding a "Automatic checks have detected X problems
with this package." message (linking to lintian's result) on the top
of the details.py page (in a rectangular box like those in Launchpad).
Do you think this would help raise awareness about those problems?