Re: Helping busy maintainers
* Romain Francoise <[EMAIL PROTECTED]> [2003-10-12 19:59]: > W: libkemo-m104 source: out-of-date-standards-version 3.5.2 > > Martin, what do you think? The maintainer told me that he tried to contact the upstream maintainer and was told this library is no loner supported. I filed a request for removal. -- Martin Michlmayr [EMAIL PROTECTED]
Re: Developer's Packages Overview formatting
* Andrew Lau <[EMAIL PROTECTED]> [2003-10-15 14:58:33 +1000]: > Hi Igor and QA, Hi Andrew, > Could you please format the Developer's Packages Overview at Debian QA > so that co-maintained packages are displayed separately from a > maintainer's own packages? 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. Cheers -- Igor Genibel http://www.answare.fr/ [EMAIL PROTECTED] http://www.tuxfamily.org/[EMAIL PROTECTED] http://people.debian.org/~igenibel/ [EMAIL PROTECTED] GPG: 1024D/9D735B4F: 4F61 8D8F 05AC 8D2C 5F92 9B99 C44B 0266 9D73 5B4F signature.asc Description: Digital signature
Re: Developer's Packages Overview formatting
On Tue, Oct 21, 2003 at 12:53:42PM +0200, Igor Genibel wrote: > * Andrew Lau <[EMAIL PROTECTED]> [2003-10-15 14:58:33 +1000]: > > > Hi Igor and QA, > > Hi Andrew, > > > Could you please format the Developer's Packages Overview at Debian QA > > so that co-maintained packages are displayed separately from a > > maintainer's own packages? > > 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. Friendly, Sven Luther
Re: Developer's Packages Overview formatting
* 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. But if you have the time, patches are welcome ;) Friendly -- Igor Genibel http://www.answare.fr/ [EMAIL PROTECTED] http://www.tuxfamily.org/[EMAIL PROTECTED] http://people.debian.org/~igenibel/ [EMAIL PROTECTED] GPG: 1024D/9D735B4F: 4F61 8D8F 05AC 8D2C 5F92 9B99 C44B 0266 9D73 5B4F signature.asc Description: Digital signature
Re: Developer's Packages Overview formatting
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
Re: Developer's Packages Overview formatting
* Sven Luther <[EMAIL PROTECTED]> [2003-10-21 14:35:59 +0200]: Sven, [...] > Some packages share a much stronger relationship between themselves > than the coincidental fact that they are maintained by the same > person. I don't want to close this discuss but the DDPO (Debian Developer's Packages Overview) is about developers, not packages. All the information are structured around the developer not the packages. If this kind of feature is necessary, all the backend and most of the frontend had to be rewritten in order to match the new aim. I don't want/have enough time to do such thing but it could really be a good thing if one wants to implement this. -- Igor Genibel http://www.answare.fr/ [EMAIL PROTECTED] http://www.tuxfamily.org/[EMAIL PROTECTED] http://people.debian.org/~igenibel/ [EMAIL PROTECTED] GPG: 1024D/9D735B4F: 4F61 8D8F 05AC 8D2C 5F92 9B99 C44B 0266 9D73 5B4F signature.asc Description: Digital signature
Re: Developer's Packages Overview formatting
On Tue, Oct 21, 2003 at 03:13:30PM +0200, Igor Genibel wrote: > * Sven Luther <[EMAIL PROTECTED]> [2003-10-21 14:35:59 +0200]: > > Sven, > > [...] > > Some packages share a much stronger relationship between themselves > > than the coincidental fact that they are maintained by the same > > person. > > I don't want to close this discuss but the DDPO (Debian Developer's > Packages Overview) is about developers, not packages. All the > information are structured around the developer not the packages. > > If this kind of feature is necessary, all the backend and most of the > frontend had to be rewritten in order to match the new aim. > > I don't want/have enough time to do such thing but it could really be a > good thing if one wants to implement this. No problem, i just wanted to mention it in case it was easily possible to do it or something, and to put the idea out for thinking about it. Please put it in the TODO or whatever list for some time to think about it when there is a redesign though. Friendly, Sven Luther > > -- > Igor Genibel > http://www.answare.fr/ [EMAIL PROTECTED] > http://www.tuxfamily.org/ [EMAIL PROTECTED] > http://people.debian.org/~igenibel/ [EMAIL PROTECTED] > GPG: 1024D/9D735B4F: 4F61 8D8F 05AC 8D2C 5F92 9B99 C44B 0266 9D73 5B4F
