A tie-dye icon that says Peterstein: Disco King of the Fireflies with a little crown on it.
[personal profile] zarhooie
Hello all,

I am writing this missive to let you know that the email address support @ dreamwidth.org is now functioning as expected. If you have submitted any Support requests via that method, please resend, as your previous email was eaten by a grue.

Thanks!

Kat
Dreamwidth Support
painting of a girl with flowing red hair looking out to sea
[personal profile] jennifer
I've read through the comments to the brainstorming post and these are the most popular requests I'm seeing:

- ability to preview and/or edit screened responses
- adjustment of point assignments
- approval links on a given answer instead of having to use the drop-down
- better tracking of when a request was last touched and in what way (screened answers, ICs)
- responding directly to other responses (threaded comments)
- improved filtering/sorting/tagging
- view of all requests a given user has sent in
- view of all requests a given user has answered
- per-request notifications
- better wording for support email notifications
- linking of support requests to Zilla bugs with access to relevant stats
- ability to reference multiple FAQs

That sounds like a pretty heavy overhaul, but I think if we work on a chunk at a time, it'll get done!

If there's no objection I can open a Bugzilla item for each of the bullet points I've listed above. Any additional discussion about implementation details can go in comments to this post for now.
Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome
[staff profile] denise
One of the things we really want to prioritize is a total overhaul of the support system's code, to make it easier for people to Get Shit Done without having to struggle with the tools available or try to bend them in ways that they were never meant to be bent. So, this is the brainstorming thread: if we were to be rewriting the support system from scratch (and assume that we will be, more or less), what would you like to see new/different/changed?
Photo of Mark's face, taken in standard office fluorescent.
[staff profile] mark
I have asked [personal profile] domtheknight to, in effect, just poke through open requests and approve answers that look good. This is temporary for closed beta. She won't be doing this long term, but she was conveniently located when I was in the mood to get support trundling along.

So -- we've got three of us now watching the board for answers at various times, feel free to go poking and answering.

I know most of the things are importer related. They should be collated into groups, people reporting the same issues, and Bugzilla bugs created for them so they can be investigated. Get as much information as possible: what service, what actually worked, what didn't. Especially if they've done anything unique or special: did they use the mass privacy tool on LJ? Did... oh I don't know, other stuff.

This is going to be a lot of feeling things out. If you have questions, you can bug me on IRC or here in comments, and I'll be happy to answer.
Photo of Mark's face, taken in standard office fluorescent.
[staff profile] mark
Just braindump, but this is how we've taken to answering requests, and it'd be useful to follow the same form for everybody.

Hi $user,

Blah blah answer to your question, blah blah. See the wiki for more information about how to write this section. It's pretty much what you expect.

Best,
  $signoff


If they sign their request, then the $user section should be whatever they sign with. First name is fine. If they don't have a name, you can greet them by their account name.

The $signoff is something you pick. You're welcome to use your name (First + Initial, aka Mark S.) and you're welcome to use your account name (e.g., xb95). Whatever you're comfortable with. Denise and I have taken to including our email address, but you shouldn't do that.

That's about it for now.
Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome
[staff profile] denise
This is eventually going to be the community for Dreamwidth's technical support volunteers. It isn't intended to be "user-facing" -- in other words, this won't be the place to go for technical support, but it will be the place to go to learn about how to provide technical support for others at the Support board.

Community membership is currently moderated, and until we figure out how we're going to structure the ranks of Support volunteers and how we're going to give people access to the administrative elements of the Support board, I'm not going to approve any community membership requests. (You're more than welcome to watch the community if you're interested in volunteering for the Support team, though!)

Obviously, the first step to getting people volunteering in Support is to write up a basic guide to what a support answer should look like. [personal profile] azurelunatic (bless her) went through a year's worth of my emails to the dw-discuss mailing list to distill some basic principles that apply to both Support answering guidelines and all official Dreamwidth communication. I've gone through her list and taken a first stab at pulling out the Support-specific elements, and collated them on the Wiki as a (very, very) basic support guide:

Support guide (first pass)

It's obviously going to take us a while to get it to cover everything, and some things will never quite be documentable; there will always be an exception to every rule. But if you're interested in volunteering for Support, take a look over that list, and then:

* What other questions do you have about how you should be writing your Support answers that aren't covered in that guide?

* Is there anything in there that you don't think should be in there?

* Is there anything in there that needs to be covered in more detail?

(Meanwhile, if anyone who's done LJ support and is familiar with the mechanics of the system (how screening works, what the various priv levels are and what they do, etc, etc) wants to write up a basic "this is how the system currently works" sometime over the next day or so -- just the technical bits of how the system works, not how LJ support grants privs and does training, since we'll be doing it differently -- that would be awesome, since I am overextended like whoa right now.)

Profile

Dreamwidth Support Volunteers

December 2009

S M T W T F S
  12345
678 9101112
13141516171819
20212223242526
2728293031  

Syndicate

RSS Atom

Style Credit

Style:
[personal profile] branchandroot
Resources:
Holy crap!

Expand Cut Tags

No cut tags
Page generated Jan. 29th, 2012 02:13 am
Powered by Dreamwidth Studios