Is it time to split rt-users?

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

Thoughts? 


Jesse

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

I would find such a list interesting, and would definitely subscribe,
though I’m afraid I wouldn’t have much to add.

(darren)

Millions long for immortality who do not know what to do with
themselves on a rainy Sunday afternoon.
– Susan Ertz

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

the idea might be helpful for someone who is not moving them all into one
folder :slight_smile:
Then, you would probably need to prohibit crossposts. Which are quite frequent
already with the two lists.

And the more users you have, the more often you’ll have to tell them
that they actually write to the wrong list…

sorry, maybe I’m too much skeptical today.

Stan

Same here.

Les

darren chamberlain wrote:

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

the idea might be helpful for someone who is not moving them all into one
folder :slight_smile:
Then, you would probably need to prohibit crossposts. Which are quite frequent
already with the two lists.

And the more users you have, the more often you’ll have to tell them
that they actually write to the wrong list…

This is true, which is why I think that the list that I need to be
subscribed to is the “rt-admin” list. It would be a list about how to
make RT work, and how to admin it.

The users which belong on rt-users are the management types who tell the
admin types how to make it look, where the queues should go, and how
they should feel, and whatnot.

ugh.

rob

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new
list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

I would find such a list interesting, and would definitely subscribe,
though I’m afraid I wouldn’t have much to add.

I would definitely subscribe to both lists.

Regards,
Harald

I’m not certain the traffic level on rt-users warrants splitting a portion
of its traffic onto a separate list. Perhaps an etiquette request for
subscribers to prepend subject lines with one of a small set of keywords to
delineate the basic topic would be another alternative to consider? So, all
subjects would end up in the received form of "[list] [keyword] subject"
with keyword examples such as database, user management, user interface,
installation, etc. Mailing list etiquette rules could be addressed in an
RTFM article.

Thanks,
Christian

Christian Gilmore
Technology Leader
GeT WW Global Applications Development
IBM Software Group

I would definitely subscribe to both lists.

A few thoughts in no particular order:

  • rt-users isn’t a heavy mailing list
  • diehards will probably subscribe to both anyhow
  • people that aren’t diehards might not be able to
    tell technical problems from process questions, and
    process problems might evolve into technical questions,
    so it’ll have mucho crossposting

I don’t think it’s broken now. :slight_smile:

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html
rich@lafferty.ca -----------±----------------------------------------------

Can I suggest we introduce and discuss some of these topics on this
list, and see if it is too confusing before splitting the list?

Maybe a keyword in the subject for process questions…

If it is a pain, then split it.On Fri, 2002-12-13 at 21:12, Rich Lafferty wrote:

On Sat, Dec 14, 2002 at 12:33:46AM +0100, Harald Wagener hwagener@hamburg.fcb.com wrote:

I would definitely subscribe to both lists.

A few thoughts in no particular order:

  • rt-users isn’t a heavy mailing list
  • diehards will probably subscribe to both anyhow
  • people that aren’t diehards might not be able to
    tell technical problems from process questions, and
    process problems might evolve into technical questions,
    so it’ll have mucho crossposting

I don’t think it’s broken now. :slight_smile:

-Rich

Though I would most likely subscribe to both lists,
This sounds like a good separation to make, and it will simplify the way
I read the mailing list :slight_smile:

**just my 2 cents,
Ron.

Jesse Vincent wrote:

Recently, a couple of folks have asked about the possibility of a new
list dedicated to ticketing policy and process. Basically, this new list
would deal with how RT is used for various things and not so much the
mechanics of making RT run.

Thoughts?

Jesse

Best Regards,
Ron Gidron
Customer Support Manager
SHUNRA Ltd.
Phone: +972 9 7643750
Mobile: +972 54 792469

I would certainly be interested in a separate list which would discuss how
to configure RT from a business-process perspective, rather from a nuts
and bolts unix error prospective.

Someplace to discuss ‘I have this business model and I’m thinking of
configuring my system so - anyone else got a similar situation and any
experiences to share?’

I would subscribe to both, for sure.

John