Differences between revisions 8 and 9
Revision 8 as of 2006-05-07 09:41:20
Size: 4185
Comment: 2 new TODO for the PTS
Revision 9 as of 2006-05-24 16:48:05
Size: 4570
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:

'''Provide RSS feeds for each source package'''

All the news should be available as an RSS feed. But the RSS feed should be richer: it should integrate more stuff like the upload of a new Ubuntu version with the corresponding Debian patch
 and also entries for the problems displayed. The difficulty is to have a good date for the various entries that are not tied to an email.

Developer information concerning the Package Tracking System

How to get the sources ?

$ export CVSROOT=:pserver:anonymous@cvs.debian.org:/cvs/qa
$ cvs login
$ cvs co pts

(you can use :ext:<yourdebianlogin>@cvs.debian.org:/cvs/qa if you're a Debian developer in the "qa" group and you'll have write access to it)

Quick introduction

Raphael Hertzog gave a short overview of the PTS intended for developers. Please [http://www.ouaza.com/textes/conf/pts-internals.pdf check the slides].

Actual TODO list

Provide RSS feeds for each source package

All the news should be available as an RSS feed. But the RSS feed should be richer: it should integrate more stuff like the upload of a new Ubuntu version with the corresponding Debian patch

  • and also entries for the problems displayed. The difficulty is to have a good date for the various entries that are not tied to an email.

Subscribe to set of packages

The members of the Gnome team would like to subscribe with a single command to all Gnome-related packages. The idea is to add a new "group subscription" feature. The GNOME team maintain the list of packages and anyone can then "groupsubscribe gnome-desktop" and be automatically subscribed to all relevant packages.

This feature could then be used by little "bugsquad team" to quickly move from one package to another.

Possibility to reset keywords to the default state

Right now, once you set some specific keywords on a given source package, you will always have a customized list keyword for this source package. And in some cases, you don't want anymore. A "keywordreset" command would be welcome.

Also te keyword DB is cluttered with wrong email/source package. It should be periodically cleaned of subscriptions which don't exist anymore.

Summary mails sent

Since the beginning, the mail part has support of a "summary" keyword. It was meant to be used to send regular (monthly or quaterly) summary mails repeating the most important information of the webpage and giving statistics about the evolution of the package (number of bugs opened since last summary mail, same for closed, number of uploads, top CVS/SVN committers, top uploaders, ...).

This mail should give some pride to the maintainers who are doing a great work and maybe even create a bit of competition between co-maintainers. :-)

Improve news handling

Each maintainer has the possibility to send (static and usual) news to the PTS. However he can't remove news which are outdated. Because of this, the maintainer are not using this very important feature. This needs to change !

Integrate better with <package>@packages.debian.org

The main maintainer can be contacted at <srcpackage>@packages.debian.org and co-maintainers can be contacted at <srcpackage>@packages.qa.debian.org. We should integrate both more tightely so that we can easily reach all contributors to a single package.

See discussion here: http://lists.debian.org/debian-devel/2006/04/msg00713.html

  1. We add a "contact" keyword to the PTS.
  2. We auto-subscribe all maintainers to their packages but with the contact keyword only.
  3. We change the package@p.d.o alias to point to the PTS.

  4. We change the default set of keywords for maintainers.

Keep the first "Accepted" mails

Right now the very first "Accepted" mail is dropped because the source package doesn't exist yet (and we can't accept blindly those mails because otherwise one could DoS the PTS by sending many fake "Accepted" mails). Instead of dropping it we should keep it until we have a confirmation that the package has been accepted by ftpmasters (and remove them after XX days if we didn't receive any confirmation).

http://ftp-master.debian.org/~joerg/joey/09.txt is a list of packages that got accepted by ftpmasters during september (change 09 into another number to get the other monthes). We could use that info to see if a "accepted" mail that's waiting can be pushed...

Integrate debtags information

Debtags is maturing quickly, it's time to push the maintainers to add tags to their own packages if they don't have any... you need to coordinate with Enrico Zini to get the information available in a usable form and then make use of it to add a new TODO item in the PTS page.

Show sponsored uploads

When receiving mails from katie extract the gpg signature and show the name of the uploader/sponsor along with Changed-By field.