* Ben Finney <ben+deb...@benfinney.id.au> [2014-01-27 10:37:06 +1100]:
> Nicolas Dandrimont <ol...@debian.org> writes: > > > - Dust off the team's PET instance ([1], which looks rather outdated). > > [1] - http://python-modules.alioth.debian.org/cgi-bin/pet.cgi > > I've never seen PET before. It seems redundant with the official QA > Packages Overview tool for each maintainer, which for DPMT is at > <URL:http://qa.debian.org/developer.php?login=python-modules-t...@lists.alioth.debian.org>. > > Thanks for bringing PET to my attention. But I wonder whether it's > unused for good reason? > > What does PET do which the Packages Overview tool does not? Why advocate PET > rather than advocating for those features to be added to the QA PAckages > Overview tool? PET is a VCS-centric view rather than an archive-centric view, which is what DDPO provides. See for instance the Perl team view: http://pet.debian.net/pkg-perl/pet.cgi This tool is meant to serve as a useful TODO-list of things that need to be done in (the VCS of) a team that maintains hundreds of packages. DDPO could probably be modified to take into account VCS information. But the data is not easy to gather, and I'm not sure that would align with the original intent of the tool. PET updates itself through VCS hooks, and has been specifically designed to use VCS data. Hope this clarifies, -- Nicolas Dandrimont BOFH excuse #90: Budget cuts
signature.asc
Description: Digital signature
