Re: Paul Wise 2008-12-22 <1229926966.25919.101.ca...@chianamo> > I think a generic way to allow people (inc those not in the QA group) to > add QA report links to each package with issues that QA report covers. > > I think a mail bot is the way to implement this, some ideas on that: > > To: pts-rep...@qa.d.o > new broken-shlibs-local > http://people.debian.org/~kibi/broken-shlibs-local.yaml > remove foopkg from broken-shlibs-local > add foopkg to broken-shlibs-local > sync broken-shlibs-local > delete broken-shlibs-local > thanks > > The YAML (or XML) file could look something like this: > > title: Broken shlibs.local > about-url: http://people.debian.org/~kibi/broken-shlibs-local.html > update-frequency: weekly > contact: k...@debian.org > packages: > - name: foo > url: http://people.debian.org/~kibi/broken-shlibs-local/f/foo.html > title: 5 issues > > The mail bot could regularly mail the contact address whenever the PTS' > list of packages for that report are out of sync with the list of > package names in the YAML file (to motivate them to fix the report).
Hmm, this sounds a bit overkillish. What if we do it the other way round, and have the ability to display groups of packages in DDPO more easily that are affected by something? I guess importing some of pkgreport.cgi's abilities to list packages per user tag into DDPO wouldn't be too hard, and doesn't need a new mechanism. For per-package reports, we could make the PTS subscribe to some (configurable) set of usertags. Christoph -- c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
