Remember, the anchor links in part I won't work for the text in part II since I had to break it into two posts. But anyhow, here's part II of the Guide. Feel free to comment on either part with suggestions or questions.

( love the little cut tags )

Here's a much more finished version.
SuportOffice is down, but I just left the text as if it isn't. And my definition list in part II keeps being broken, but I have no clue why. If anyone can figure it out, that'd be neat.
Anyhow the LiveJournal Support Guide in progress:

( part one )

See previous post. Remember, please comment to my comment, not the post itself.
( more guide )

Notes:
a) For those who saw it before, some sections have been edited, most noticeably rules2 and improving.
b) For those who suggested improvements, I tried to improve, but if I missed some, let me know.
c) I need to post in two parts, I exceeded the max posting size this time
d) This post is public
e) I will leave a comment in each of these posts, please comment to that comment or other comments in the post, not the post itself - I just don't want to be emailed the guide bunches of times
f) Anchor tags will break when they straddle posts, don't worry about it.
g) The glossary is the only part known to be incomplete

So, without further ado, Part 1 of the Guide
( Support Guide )

I'm giving chemicallace co-administration status in embedding. When I have more details, I'll post to lj_support.

Note: this post is public, as I really didn't see any reason to make it confidential.

I think until the interims have an approved plan and email, category admins should continue sending out welcome emails themselves as they see fit. (Note: if any of them want the email I have or any of the other standardized emailings, just let me know.)

I don't want to rush the interims, nor do I want the new volunteers to lose out while we wait for the interim plan to be ready. So, I think it's best for us to just email, and let them know whom we've contacted. That's my opinion. :)

Note: this post is shockingly free of chinchillas. How sad.

I have a business trip coming up that will so heavily occupy my time as to take me 100% out of action beginning next Tuesday, August 13, through Monday, August 19. I'm expecting that arie will be carrying all cust admin through that period, although she could probably use an extra hand or two (or new computer or new OS).

This has been brought up informally in various places, but never formally discussed. And since several other support improvements are in the works (of which I am very appreciative) it seemed a good time to find out if this would be a wanted change -

Making support request answers default to screened answer

I view it as a good idea because this way if anything messes up it doesn't go through to the user. And you have to decide to send something publicly. We've had people have computer problems that sent an answer through. We've had people simply forget to change the option. This should cut down on anything like that.

Also, I think at this point most privs choose to answer screened and then approve anyway. So, while this would annoy a few people, they would still have the ability to select answer, and most people would probably find it more convenient.

Since this would likely affect the private categories as well, I think if people think it's a good idea then we should ask people who deal with the private categories, such as Tommyx (is there anyone else who doesn't read this community? I had listed Sherm, but since I made this public, he'll see it) whether they have any objections.

Hmmm, I thought about public/private level on this, but see no reason to make it private. I primarily want the opinions of the other admins, but it would affect all support volunteers with supportpriv.

So... opinions?

There's a new category available, "communities", and I was wondering if gooner would mind admin'ing it?

This CVS commit changes the format of the embedding page, and it shows a new ASP method. Later on tonight it'll be merged in live, but for now you can see the changes at http://goathack.livejournal.org:8006/developer/embedding.bml