Differences between revisions 24 and 25
Revision 24 as of 2013-08-28 20:50:31
Size: 4952
Editor: GeoffSimmons
Comment: Add CategoryPermalink.
Revision 25 as of 2014-03-05 21:41:37
Size: 4476
Editor: ?SalvatoreBonaccorso
Comment:
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
The security team (for stable and oldstable) uses three queues:

 * '''Security''': default queue, publicly viewable. For any non-private issue, that is, issues already public on any medium, e.g. bugtraq or other mailinglists, reported to the BTS, websites etc.

 * '''Security - incoming'''
 * '''Security - private: '''issues still under embargo, e.g. coming from the vendor-sec mailinglist or by direct notification to the security team. These often have an agreed disclosure date set in the "Embargo" field.
New tickets can be created by mailing security@rt.debian.org (make sure to put "Debian RT" somewhere in the subject).
The security team does not use anymore the RT queues, see [[https://lists.debian.org/debian-devel-announce/2014/03/msg00004.html|Bits from the Security Team]].

rt.debian.org - Debian Request Tracker

rt.debian.org is a Request Tracker used by some Debian teams. (some others use a pseudo-package on bugs.debian.org or a tracker on an Alioth project.)

Web Access

RT lives at: https://rt.debian.org/

Debian developers can also log in as the debian user. The password for this account is available from: master.debian.org:/home/debian/misc/rt-password. There's currently no connection to the central Debian LDAP, but accounts can be created for regular members of the teams using RT.

Due to abuse, the former "guest" account has been disabled and it's no longer possible for others to view the public queues and tickets.

CLI Access

See rt_cli and see above for about/access.

Mail Access

  • To create a ticket by a mail to the appropriate team (listed below). Make sure to put "Debian RT" somewhere in the subject.
  • To provide extra information to a ticket, you can mail rt+nnn@rt.debian.org (or rt-comment+nnn@rt.debian.org for private comments readable only by the queue owners). You can also mail the initial address, but in that case you must make sure to include the precise subject tag like "[rt.debian.org #379]".

Teams

Debian System Administration

The DSA team uses 3 queues:

  • DSA [public]
  • DSA - incoming
  • DSA - private

New tickets can be created by mailing admin@rt.debian.org (make sure to put "Debian RT" somewhere in the subject). see DSA RT Usage page.

Keyring Maintainer

The keyring maintenance team uses two queues:

  • Keyring [public]
  • Keyring - incoming

New tickets can be created by mailing keyring@rt.debian.org (make sure to put "Debian RT" somewhere in the subject).

Security Team

The security team does not use anymore the RT queues, see Bits from the Security Team.

If you are a maintainer looking for more information on how to deal with a security problem in one of your packages, there are detailed instructions in the Developer's Reference - Chapter 5. Managing Packages.

Mirror Team

The mirror team only use one public queue: Mirror.

New tickets can be created by mailing mirror@rt.debian.org (make sure to put "Debian RT" somewhere in the subject).

Debian-Edu/Skolelinux Sysadmin (drift) Team

The Debian-Edu/Skolelinux Sysadmin team uses three queues:

  • DESA [public]
  • DESA - incoming
  • DESA - private

New tickets can be created by mailing desa@rt.debian.org (make sure to put "Debian RT" somewhere in the subject). Tickets will be created in the DESA - incoming queue and then manually changed to either the public or the private queue by a team member.

Backports Team

The Backports Team only use one queue: Backports.

New tickets can be created by mailing backports@rt.debian.org (make sure to put "Debian RT" somewhere in the subject).

Other teams

If any other teams/groups want to use rt.debian.org to track their requests, they're welcome to do so, just send the details in an RT ticket for DSA.

Incoming queues and visibility

When a team uses an "incoming" queue, all newly created tickets end up there and are thus not public by default until someone move them to the public queue. This is so we can have tickets mailed in which shouldn't immediately become public, e.g. '/bin/lala is a 4755 bash on master' or whatever. The idea is that almost every ticket will move from the incoming queue to the public queue the first time a human sees/touches it. When there's a private queue, it's intended for tickets that really should remain private but these should be the vast minority of tickets with the majority being in the public queue.

Resources


CategoryPermalink