TLUG spam

[Tyler Aviss]

Actually, we sometimes have some pretty big issues at work with
name-changes, mainly because a lot of things are tied together. Our HR
system, email + forwarding
, LDAP, and various others all need to be updated when somebody
changes their name. As I work in a school district, we tend to get a
lot of those over the summer, and those with new married names seem to
get annoyed that it takes a long time at the start of the year to get
the name/username-change pushed through.

I suggested to my supervisor that we put in place a policy that only
one staff member can change his/her name per month. He thought it was
a good idea...  but I'm hoping he knew I was joking.

On 9/14/07, Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> On Thu, Sep 13, 2007 at 06:40:19PM -0400, Colin McGregor wrote:
> > Yes, but it carries another problem, members whose
> > names change. The most recent example that I can think
> > of (and there is at least one other examples I could
> > name) is Leah Cunningham / Kubik . Here we have a case
> > where Leah Cunningham joined the list, but postings
> > from that person (thanks to marriage) are now under
> > the name Leah Kubik. In other words, yes, screening
> > based on the name the person joined under would help,
> > but introduce a new set of issues. Which is worse?
>
> Name changes are obsolete anyhow.  They are such a hassle for account
> names and such.  Just leave the name alone.  Some places don't even let
> you change names anyhow (like Quebec).  Seems like a good solution to
> me. :)
>
> --
> Len Sorensen
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists