Index: branches/locker-dev/locker/doc/tickets/cnames.txt
===================================================================
--- branches/locker-dev/locker/doc/tickets/cnames.txt	(revision 1221)
+++ branches/locker-dev/locker/doc/tickets/cnames.txt	(revision 1414)
@@ -23,6 +23,6 @@
    reap it; they should do so quickly. If it belongs to an FSILG, e-mail
    ht-$ILG-acl (ht-et-acl, ht-pika-acl, etc.) and ask nicely. If it belongs
-   to an academic network, they're not getting the name back unless they can
-   negotiate with the current owner of the name
+   to an academic network, they're not getting even deleted names back unless
+   they can negotiate with the current owner of the name.
 
 2. Check that they're requesting a scripts.mit.edu path that they control
@@ -36,18 +36,31 @@
    before proceeding.
 
+   Confirm that they're signed up for scripts. http://locker.scripts.mit.edu/
+   should give something that isn't the "Account unknown" page.
+
 3. E-mail jweiss.
    * Open the ticket in RT
    * Click 'Comment' to the right of the body of the e-mail they sent
    * CC: jweiss@mit.edu (Don't use "To:", there's a bug)
-   * Write something nice. I typically use
+   * Write something nice, preferably including the stella command line.
+   I typically use
    Subject: scripts CNAME request: foo.mit.edu
 
-   At your convenience, please make foo.mit.edu an alias of scripts.mit.edu.
+   At your convenience, please make foo.mit.edu an alias of scripts-vhosts.mit.edu.
+
+   stella scripts-vhosts -a foo
        (or)
    At your convenience, please move the alias foo.mit.edu from bar.mit.edu to
-     scripts.mit.edu.
+     scripts-vhosts.mit.edu.
+
+   stella bar -d foo
+   stella scripts-vhosts -a foo
        (or)
    At your convenience, please rename the current host foo.mit.edu to
-     foo-old.mit.edu and make foo.mit.edu an alias of scripts.mit.edu.
+   foo-old.mit.edu and mark it as deleted, and make foo.mit.edu an
+   alias of scripts-vhosts.mit.edu.
+
+   stella foo -S 3 -R foo-old
+   stella scripts-vhosts -a foo
        (or)
    If the request below is sufficient authorization, please remove....
@@ -55,6 +68,6 @@
    * Set Status => Waiting and Blocking On => Moira
 
-   Occasionally jweiss is on vacation; check /mit/ops/Pager.Schedule for
-   "!jweiss" entries. It's worth asking him ahead of time if he's around. If
+   Occasionally jweiss is on vacation; generally he sets an auto-responder,
+   so you can just try emailing him and hoping, or ask him if he's around. If
    not, see if zacheiss or cfox or computing-help will handle the requests.
    (zacheiss has been willing to do them in the past.)
@@ -72,3 +85,3 @@
    or RewriteRules if they're having trouble.
 
---geofft, last updated 2008-08-02
+--geofft with minor edits by adehnert, last updated 2009-12-01
Index: branches/locker-dev/locker/doc/tickets/rt.txt
===================================================================
--- branches/locker-dev/locker/doc/tickets/rt.txt	(revision 1221)
+++ branches/locker-dev/locker/doc/tickets/rt.txt	(revision 1414)
@@ -10,14 +10,35 @@
 yourself of own updates" is on. You can also set the "Default Working Queue"
 to Scripts, and give yourself a signature referring to scripts@mit.edu.
-Another useful option here is to set a password, so you don't need certs to
-log in (and so you can use the zephyrbot).
 
-The zephyrbot (currently down) will take commands to -c scripts -i [ticket
-number] of the form /set status=resolved or /set owner=geofft.
+Another useful option here is to set an RT passwordfor your account, so you
+don't need certs to log in (though it sometimes will keep asking you for
+your password on each page load if you don't have certs) and so you can use
+the zephyrbot).  The zephyrbot will take commands to
+-c scripts -i [ticket number] of the form /set status=resolved or
+/set owner=geofft.  You need to drop a file in
+/mit/geofft/web_scripts/rt/rt-passwords by your username with the format:
+
+"username" "yourawesomepassword"
+
+And then ask geofft (zwrite geofft) to restart the RT bot.
+
+Note that in the event that Geoff's account is compromised, it is possible
+for an attacker to use this password do manipulate tickets in *any*
+queue you have bits on, not just the Scripts one.
+
+The RT bot will post ticket notifications as -c scripts -i nnn.  If you are
+responding to a ticket, it is conventional to post "lock" to the appropriate
+instance, so others know not to pre-empt you.  You should post "unlock" once
+you are done handling the ticket.
 
 You can also place these commands on a line by themselves inside e-mail; they
 will be acted upon and removed before the e-mail gets sent back out.
 
-Don't use the To field, it doesn't work. If you want to send the ticket somewhere else, use CC.
+If you're adding a *comment* (such as when you're forwarding a cname request
+on to IS&T), don't use the 'To:' field, because it'll be clobbered by our
+RT scrips and the mail won't actually go to the destination you added.
+Instead, you should use the 'Cc:' field.  Similarly, if you're adding
+*correspondence*, the 'Cc:' field will be clobbered and you need to use
+the 'To:' field.
 
 Don't CC other RT queues, it doesn't work. If you really need to, use your