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
HanleyMartin
Hanley, Martin

Thu

May 31
2001

13:46Z

[Ed] [Ed] Jitterbug notification & stuff

> 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.

I think this would be a really good idea!  Of course, I've probably just
given myself the job of writing this auto-response letter :)... .which I
don't mind, but a quick overview on the application process would be a good
thing :)

Let me see IIRC:
1. Application received
2. Application reviewed
3. If game sounds ok, check web links, else get more/better info
4. If web links ok, check game concept, else get web links fixed
5. If game concept ok,... this is where I lost the process

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

CarlCravens
Carl D Cravens

Mon

Jun 4
2001

03:33Z

[Ed] [Ed] Jitterbug notification & stuff

On Thu, 31 May 2001, Martin Hanley wrote:

> I think this would be a really good idea!  Of course, I've probably just
> given myself the job of writing this auto-response letter :)... .which I
> don't mind, but a quick overview on the application process would be a good
> thing :)

> Let me see IIRC:
> 1. Application received
> 2. Application reviewed
> 3. If game sounds ok, check web links, else get more/better info
> 4. If web links ok, check game concept, else get web links fixed
> 5. If game concept ok,... this is where I lost the process

The editor is the front-line of the application process.  You're going to
make a decision on most of the games yourself, generally to reject them.
Rarely, you'll approve one on your own.  If you've decided that a game
might be worth accepting, but aren't sure, the proposal gets forwarded to
the peer review group (listowners+prospects@phoenyx.net).  Checking the
web links ought to happen before sending for peer review... peer review
happens after you've gathered all information.  Once in awhile the review
group will ask for more, but the goal is to have enough that they won't
have to.

In fact, Karen and I were discussing this today... we don't think the
editor should have to go to a web site to evaluate the game.  Everything
we need should be handed to us in a concise manner.  (I once had a
prospect email me a megabyte PDF of the previous two years of his game
written up in novel form... like a hundred pages.)  This is something
that'll have to go on the application instructions... complete but
concise, the editor shouldn't have to wade through lots of junk to figure
things out.

So I'm going to call it this...

1) Application received, the applicant gets an auto-response thanking him
   for his application and explaining the review process
2) Applicaiton initially reviewed by editor (max 2 days)
   a) Editor asks for more information
   -or-
   b) Editor accepts/rejects immediately
3) Editor forwards application and requested info to the peer review
   group, applicant notified of application status
4) Peer review responds within three days
5) Editor makes final decision to accept/reject based on peer review
   a) Sends friendly rejection letter, explaining why rejected
   -or-
   b) Editor requests list to be set up, mails instructions to new GM

Notice something implicit up there... I'm looking for a five-day
turn-around maximum, and that's including a three-day peer review.  If
you, as editors, think that five days is too much pressure on your
schedule, we need to set a time frame that we can all agree with.  I
certainly have fallen short here myself, but I never set a standard for
myself either.

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

MikeF
Mike Feldhusen

Mon

Jun 4
2001

22:20Z

[Ed] Jitterbug notification & stuff

On Sun, 3 Jun 2001, raven@phoenyx.net wrote:

[Lots snipped]

> Notice something implicit up there... I'm looking for a five-day
> turn-around maximum, and that's including a three-day peer review.
> If you, as editors, think that five days is too much pressure on
> your schedule, we need to set a time frame that we can all agree
> with.  I certainly have fallen short here myself, but I never set a
> standard for myself either.

Just as a note, people who expect to be out of touch for a while (more
than a day probably) should let the rest of us know, so coverage can
be arranged.  Otherwise, this schedule cannot be met.

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

CarlCravens
Carl D Cravens

Tue

Jun 5
2001

20:40Z

[Ed] Jitterbug notification & stuff

On Mon, 4 Jun 2001, Michael Feldhusen wrote:

> Just as a note, people who expect to be out of touch for a while (more
> than a day probably) should let the rest of us know, so coverage can
> be arranged.  Otherwise, this schedule cannot be met.

Very true.

Unless I'm gone, I can always back you up, but right now I'm trying to
keep my hand out of things except to watch and guide... you guys won't get
the hang of things if I keep jumping in and "helping" before you can get
to it.

BTW: You guys can ignore _incoming.  That's the general "help@phoenyx.net"
dumping ground and pretty much everything there is for Karen or I.  If
it's not, I'll... probably dump it in your game1 folder, I guess, since
you'll get notified automatically that way.

If having only one "personal" folder for your category and sharing the
followup and inactive folders is a pain, we can look at creating new
folders.  We're in an exploratory mode right now.  I'm just trying to
avoid creating new folders... there are already 15 in the list.

I've already got a personal jbug setup to track my eBay auctions... it's
fairly simple, except right now I have to clone all the external scripts
that I use.  (I should rewrite those to be generic and take the queue
directory off the command line.)  If it comes down to it, I can separate
out the editor function and Karen and my "support" functions (especially
because our todo folders are pretty internal, though I'd like you guys to
be able to dump stuff in them) into a separate jbug queue directory to
keep things "cleaner".

Or if you don't mind 30 items on the drop-down menus and large lists, we
can just add more folders as we need them.

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

MikeF
Mike Feldhusen

Tue

Jun 5
2001

20:47Z

[Ed] Jitterbug notification & stuff

On Tue, 5 Jun 2001, raven@phoenyx.net wrote:

> On Mon, 4 Jun 2001, Michael Feldhusen wrote:

> > Just as a note, people who expect to be out of touch for a while (more
> > than a day probably) should let the rest of us know, so coverage can
> > be arranged.  Otherwise, this schedule cannot be met.

> Very true.

> Unless I'm gone, I can always back you up, but right now I'm trying to
> keep my hand out of things except to watch and guide... you guys won't get
> the hang of things if I keep jumping in and "helping" before you can get
> to it.

But that means that we need to know if you're gone as well, so we can
make sure that we *don't* drop the ball.

Can you make it so that if anything doesn't get acted on in the normal
amount of time, we *all* get notified?  That should help out in those
case were someone "falls off the face of the earth" for a while.

> BTW: You guys can ignore _incoming.  That's the general
> "help@phoenyx.net" dumping ground and pretty much everything there
> is for Karen or I.  If it's not, I'll... probably dump it in your
> game1 folder, I guess, since you'll get notified automatically that
> way.

I have no problem with looking at and cleaning out trash (spam) if
there happens to be some (I've done so a couple of times now already
anyway, and dutifully logged it and why :-) ), or moving things along
to the appropriate place if I can tell what that would be.

> If having only one "personal" folder for your category and sharing the
> followup and inactive folders is a pain, we can look at creating new
> folders.  We're in an exploratory mode right now.  I'm just trying to
> avoid creating new folders... there are already 15 in the list.

I don't see a problem with sharing the followup and inactive folders,
there shouldn't be that much stuff in them and the logs for everything
should indicate who is handling them.

> I've already got a personal jbug setup to track my eBay
> auctions... it's fairly simple, except right now I have to clone all
> the external scripts that I use.  (I should rewrite those to be
> generic and take the queue directory off the command line.)  If it
> comes down to it, I can separate out the editor function and Karen
> and my "support" functions (especially because our todo folders are
> pretty internal, though I'd like you guys to be able to dump stuff
> in them) into a separate jbug queue directory to keep things
> "cleaner".

> Or if you don't mind 30 items on the drop-down menus and large
> lists, we can just add more folders as we need them.

Let's just say that 30 item drop-downs are not my "ideal".

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

HanleyMartin
Hanley, Martin

Wed

Jun 6
2001

13:04Z

[Ed] Jitterbug notification & stuff

Just to let you all know, I will be gone next week.  I'm going to be at Boy
Scout Summer Camp.

And, 30 folders, would be a Bad Thing :)  A little too much to sift through,
I would say.

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

CarlCravens
Carl D Cravens

Fri

Jun 8
2001

21:17Z

[Ed] Jitterbug notification & stuff

On Tue, 5 Jun 2001, Michael Feldhusen wrote:

> But that means that we need to know if you're gone as well, so we can
> make sure that we *don't* drop the ball.

Not a problem.  But I'm never "gone"... I only go on vacation to my
mother-in-law's and I monitor everything from there.  (I need to take a
real vacation.  Sigh.)

> Can you make it so that if anything doesn't get acted on in the normal
> amount of time, we *all* get notified?  That should help out in those
> case were someone "falls off the face of the earth" for a while.

Hum.  I'm on all the notification lists, so I see it all anyway and the
only time something would fall through the cracks is if I'm not paying
attention or out of town.  I'll think about this, but it might not be
worth the trouble to implement.

> I have no problem with looking at and cleaning out trash (spam) if
> there happens to be some (I've done so a couple of times now already
> anyway, and dutifully logged it and why :-) ), or moving things along
> to the appropriate place if I can tell what that would be.

I've implemented a simple filter that doesn't accept anything without an
expected address in the To: line.  No spam's gotten through yet, so that's
been kind of nice.

> Let's just say that 30 item drop-downs are not my "ideal".

Me either.  If we went to that, I'd rename z_trash to _trash, becasue
that's the folder I select multiple times the most.  (I suppose if I made
Karen handle all of the inactivity notices, many of which are bogus
because they're for testlist or other lists we expect to be inactive, she
might get that ignore_this_lists_activity feature written.  I suppose I
could just write a mail filter to discard the reports I don't want.)

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

Subject (required)




 
Refresh