3030
Comment: more stuffs
|
3159
Add new queues, advise email for ticket creation, remove useless details
|
Deletions are marked like this. | Additions are marked like this. |
Line 22: | Line 22: |
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).)]] | == Teams == |
Line 24: | Line 24: |
== Email Access == To create a new ticket, simply send a mail to admin@rt.debian.org and make sure to put the string "Debian RT" somewhere in the subject. |
=== Debian System Administration === |
Line 27: | Line 26: |
== Queues and Teams == Right now, the queues are as follows: * keyring [public] * DSA [public] * keyring - incoming |
The DSA team uses 3 queues: * DSA [public] |
Line 38: | Line 31: |
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. | New tickets can be created by mailing admin@rt.debian.org (make sure to put "Debian RT" somewhere in the subject). |
Line 40: | Line 33: |
== (Boring details on) Queues and Users == | === The keyring team === |
Line 42: | Line 35: |
=== users === 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. |
The keyring maintenance team uses two queues: * Keyring [public] * Keyring - incoming |
Line 45: | Line 39: |
=== queues === 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 |
New tickets can be created by mailing keyring@rt.debian.org (make sure to put "Debian RT" somewhere in the subject). === The security team === The security teams uses three queues: * Security [public] * Security - incoming * Security - private New tickets can be created by mailing security@rt.debian.org (make sure to put "Debian RT" somewhere in the subject). === The 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). === 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 |
Line 51: | Line 68: |
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 |
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 |
?BRTranslation(s): none
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/]
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
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).
The keyring team
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).
The security team
The security teams uses three queues:
- Security [public]
- Security - incoming
- Security - private
New tickets can be created by mailing security@rt.debian.org (make sure to put "Debian RT" somewhere in the subject).
The 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).
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.
Ressources
http://bestpractical.com/rt - Best Practical's request Tracker homepage.
[http://www.debian.org/doc/developers-reference/ch-resources#s-server-machines http://www.debian.org/doc/developers-reference/ch-resources] - some hints on DSA RT tickets.