Differences between revisions 29 and 30
⇤ ← Revision 29 as of 2024-03-18 20:07:51 →
Size: 4946
Editor: wookey
Comment: Clarify which credentials to use when
← Revision 30 as of 2024-05-26 00:34:33 → ⇥
Size: 5003
Editor: PaulWise
Comment: polish
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
Line 9: Line 10:
Line 14: Line 16:
rt accounts are different from other debian accounts (db, sso, salsa). There's currently no connection to the central Debian LDAP, but accounts can be created for regular members of the teams using RT. Most interaction is done over email, but a generic read-only login is provided for debian developers to use the web or cli interfaces.
RT accounts are different from other Debian accounts (db, sso, salsa). There's currently no connection to the central Debian LDAP, but accounts can be created for regular members of the teams using RT. Most interaction is done over email, but a generic read-only login is provided for Debian developers to use the web or CLI interfaces.
Line 17: Line 20:
Line 19: Line 23:
Debian developers can log in as the ''debian'' user. The password for this account is available from: master.debian.org:/home/debian/misc/rt-password. Or if they have rt accounts they can use those credentials for read/write access. Debian developers can log in as the ''debian'' user. The password for this account is available from: master.debian.org:/home/debian/misc/rt-password. Or if they have RT accounts they can use those credentials for read/write access.
Line 24: Line 28:
Line 27: Line 32:
Line 29: Line 35:
 * When sending an OpenPGP-signed ticket, remember to use [[http://www.earth.li/~noodles/blog/2014/09/automatic-inline-signing-for-m.html|inline signing]]  * When sending an OpenPGP-signed ticket, remember to use [[https://www.earth.li/~noodles/blog/2014/09/automatic-inline-signing-for-m.html|inline signing]]
Line 32: Line 38:
Line 33: Line 40:
Line 50: Line 58:
The security team does not use the RT queues any more, see [[https://lists.debian.org/debian-devel-announce/2014/03/msg00004.html|Bits from the Security Team]]. The security team does not use the RT queues any more, see [[https://lists.debian.org/msgid-search/20140305190301.GA2912@pisco.westfalen.local|Bits from the Security Team]].
Line 52: Line 60:
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]]. 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 [[https://www.debian.org/doc/developers-reference/pkgs#bug-security|Developer's Reference - Chapter 5. Managing Packages]].
Line 55: Line 63:
Line 70: Line 79:
Line 75: Line 85:
Line 78: Line 89:
Line 81: Line 93:
 * http://bestpractical.com/rt - Best Practical's request Tracker homepage.
 * [[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.
* https://bestpractical.com/request-tracker - Best Practical's request Tracker homepage.
 * [[https://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 85: Line 98:
## This page is linked from http://www.debian.org/doc/manuals/developers-reference/pkgs ## This page is linked from https://www.debian.org/doc/manuals/developers-reference/pkgs

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 issue system on a Salsa project.)

Contents

  1. rt.debian.org - Debian Request Tracker
    1. Accounts
    2. Web Access
    3. CLI Access
    4. Mail Access
    5. Teams
      1. Debian System Administration
      2. Keyring Maintainer
      3. Security Team
      4. Mirror Team
      5. Debian-Edu/Skolelinux Sysadmin (drift) Team
      6. Backports Team
      7. Other teams
    6. Incoming queues and visibility
    7. Resources

Accounts

RT accounts are different from other Debian accounts (db, sso, salsa). There's currently no connection to the central Debian LDAP, but accounts can be created for regular members of the teams using RT. Most interaction is done over email, but a generic read-only login is provided for Debian developers to use the web or CLI interfaces.

Web Access

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

Debian developers can log in as the debian user. The password for this account is available from: master.debian.org:/home/debian/misc/rt-password. Or if they have RT accounts they can use those credentials for read/write access.

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 send 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 an OpenPGP-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 the RT queues any more, 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