Home | Forum | Unread | Sign in | Sign in | Beta? | Wiki
The Phoenyx
your roleplaying community

news > managers > main

Discussion, mostly technical, about running Phoenyx groups goes here. Hypotheticals and wishlists go in stakeholders.
Subscribe | Unread | Recent | Group options | Topic options | Post
CarlCravens
Carl D Cravens

Thu

May 31
2001

02:30

[Ed] Jitterbug notification & stuff

Bruce, could you log into jitterbug and enter your email address in the
user profile?

I found the bug in my notification script... I was splitting on spaces
when it's supposed to be commas.  Works fine when there's only one user in
the list, but broke when I added more.  (Most of you got notifications of
various types while I was playing around.  I'm done now.)

So... the notification script is working and everyone but Bruce and Lynn
are currently in the proper notification lists.  I've set up a different
folder for each category and taught the filter to deposit messages
accordingly.  I think I want to keep sharing the followup and inactive
folders.  I think having three folders per category (that's nine more
folders) would clutter up the screen too much.  Yeah... I just stuck nine
more directories in there and it's a mess.  Especially the pull-down menu
that has every folder on it.  And we'd just get more as we become more
successful and pull more categories out of "other".

(I set it up this way because you guys would have really gotten annoyed at
getting an email every time a ticket was modified by someone else in any
way.  By creating a different folder for each category, you'll only see
tickets you care about, for the most part.)

I'm also in the notify lists, so I'll see what's coming through.

My notify script (separate from jbug's notification, but using the same
notification lists) runs once a day and reminds you of tickets that
haven't been touched by a jbug user in over a day.  (If we're kept up to
date, you'll never see a reminder.)

The script is also running on the game2_followup and game3_inactive
folders with a 3-day and 5-day (respectively) period before warning.  That
is, it doesn't squawk until an game3_inactive ticket hasn't been touched
for five days.  I'm currently the only person on the notification lists
for these folders.

Alright... Jbug's set up the way I want, so I'm leaving it up to you to
get to the tickets quickly.  Right now, that's the only duty you need to
worry about... learning to handle game requests in a timely manner.  (I'm
bad at it, don't look to me for an example.)  *Some* kind of reply within
24 hours... usually "do better" unless they're too good for "do better"
but not quite good enough for instant approval.  If you don't have time to
deal with something, let me know.  Our new GM's aren't going to feel like
a very welcome part of the community if they have to "fight" to get a
mailing list.

Question: Would an automated response indicating that the request has been
received, what the application process flow is, etc. and introducing
yourself as the category editor be a good deal?  I expect the editors to
end up having a public profile and getting to know their GM's, at least a
little bit.  This might be a good place to get started and the user won't
see his application disappear into a black hole.

Mike... you've got Trek until Lynn opts back in.  I'll handle Horror until
Bruce gets back with the program.

Thanks *very* much, guys.  You probably don't realize at this point just
how critical this function is to the success of the Phoenyx and just how
grateful I am that you're helping out.  Remember that I'm here to help you
along in any way that you can.

Next:  I'm off to write approval guidelines and an approval process flow
description.

-- --------------------------------------------------------------
Listowner tools are found at http://www.phoenyx.net/listowners

Subject (required)




 
Refresh