On Mon, Jun 4, 2012 at 5:03 PM, John Stoffel <[email protected]> wrote:
> > So which has priority? Making the list handle tickets, or keep the > discussion? If it's mostly for tickets (in an ah-hoc manner > currently), then making it into a ticketing system is a good idea. > Move the discussion off to a new, well publicized list and you're good > to go. > > Difficulty in publicizing a new list is exactly the reason I'm opposed to breaking the list apart. Most of the messages to the list are sent by non-subscribers. Over time, we have managed to get the word out and create a strong internal brand around that email list. I'm not convinced we can easily reproduce that with new email lists but I haven't ruled it out. > Don't try to combine them. > To be clear, I'm not really combining them, they're already unified. I'm just trying to extract the requests on that list out into tickets rather than forwarding them in manually. Matt
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
