Differences between revisions 1 and 26 (spanning 25 versions)
Revision 1 as of 2007-10-23 05:20:02
Size: 2659
Editor: FranklinPiat
Comment: Guillem Jover 's http://lists.debian.org/debian-devel-announce/2007/03/msg00018
Revision 26 as of 2015-09-22 11:54:22
Size: 4629
Editor: Ana
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
##[:FrontPage:Front page] > rt.debian.org
[[BR]]~-''Translation(s): none ''-~
----
##[[BR]]~-''Translation(s): none ''-~
##----
Line 12: Line 11:
## If your page gets really long, uncomment this Table of Contents
## ||<style="font-size:smaller">'''Table of Contents'''[[TableOfContents(2)]]||
<<TableOfContents(3)>>
Line 16: Line 14:
RT lives at: [https://rt.debian.org/] RT lives at: https://rt.debian.org/
Line 18: Line 16:
Anyone can view the public queues and tickets by logging in as the 'guest' user with the password 'readonly'. 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.
Line 20: Line 18:
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 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.
Line 22: Line 20:
This account can also create tickets through the web interface, if you prefer that to email [[FootNote(The 'guest' account can't create tickets because it has such a weak password it might as well not have one (in fact, if that were an option in RT, it wouldn't).)]] == CLI Access ==
See [[rt_cli]] and see above for about/access.
Line 24: Line 23:
== Other teams == == 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]".
 * When sending a GPG-signed ticket, remember to use [[http://www.earth.li/~noodles/blog/2014/09/automatic-inline-signing-for-m.html|inline signing]]
Line 26: Line 28:
If any other teams/groups want to use rt.debian.org to track their requests, they're welcome to do so, just send us the details in an RT ticket for DSA. == Teams ==
=== Debian System Administration ===
The DSA team uses 3 queues:
Line 28: Line 32:
== (Boring details on) Queues and Users ==  * 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 [[Teams/DSA/RTUsage|DSA RT Usage]] page.
Line 30: Line 37:
The current setup of queues and users in RT is a work in progress and may change depending on how well things work out. For example, with users we could look at either integrating RT with LDAP or using one of the auto-account-creation hacks for RT rather than having one shared account for DDs. === Keyring Maintainer ===
Line 32: Line 39:
Right now, the queues are as follows: The keyring maintenance team uses two queues:
Line 34: Line 41:
 o keyring [public]
 o DSA [public]
 * 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).
Line 37: Line 45:
 o keyring - incoming
 o DSA - incoming
 o DSA - private
=== Security Team ===
Line 41: Line 47:
With new tickets defaulting to the 'incoming' queues which are not
world readable. 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. There's a private DSA queue for tickets that really
should remain private but these should be the vast minority of tickets
with the majority being in the public queue.
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]].
Line 50: Line 49:
== Ressources == 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 [[http://www.debian.org/doc/developers-reference/pkgs#bug-security|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 ==
Line 52: Line 79:
 * [[http://www.debian.org/doc/developers-reference/resources.html#server-machines|Debian Developer's Reference - 4.4. Debian machines]] - some hints on DSA RT tickets.
Line 53: Line 82:
## - Sometime, it's useful to add some "keywords" not use in the page (synonyms, etc.)
## keywords:
## - If this page belongs to an existing Category, add it below.
## This page is linked from http://www.debian.org/doc/manuals/developers-reference/pkgs
CategoryPermalink

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]".

  • When sending a GPG-signed ticket, remember to use inline signing

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