On Tue, Oct 21, 2003 at 02:29:34PM +0200, Igor Genibel wrote: > * Sven Luther <[EMAIL PROTECTED]> [2003-10-21 13:37:09 +0200]: > > > > I need to rewrite the engine and provide an option to display or not > > > the co-maintaning packages. I will do this for the next weeks. > > > > Ideally, it would be possible to create lists of packages that could > > be overviewed together, for those developers who have lot of packages, > > or for group of packages that are commonly maintained. > > Hum, this is not a realistic thing since the main aim of DDPO is to > provide "synthetic" information. This is not an ugly web application > that manage cookies, sessions, etc.
Well, the idea is to have an overview of groups of packages which are related (and need to go into testing together). For example i manage, together with a few other developers, the ocaml debian packages. In order to get them in testing, i have to look at the buildd results of all those packages and the excuse files also. Sure, the Bjorn script helps, but i still go to the package overview of myself, and also of Stefano and Jerome who maintain most (but not all) the other related packages. The idea is to have 'pools' of packages, the ocaml pool, the gnome pool, the kde pool, the powerpc-arch support pool, the whatever pool, and be able to get a quick overview of the situation of those packages, and quickly find the place where problems are and investigate the bug reports and other reasons why the autobuilders are not doing their jobs (they where waiting on the wrong build-depend for example in my case, and had i not looked at Stefano's page together with mine and Bjorn's script, i may not have noticed). Some packages share a much stronger relationship between themselves than the coincidental fact that they are maintained by the same person. Friendly, Sven Luther
