On Jan 4, 2011, at 11:29 AM, Michael C Tiernan <[email protected]> wrote:
> ----- Original Message ----- >> From: "Adam Compton" <[email protected]> > >> What do you think about the term "guide" for this role? > I think it's better. > > Would we consider "advocate" or "advocator"? We should look at what similar organizations are called. What is AARP? What is the Teamsters Union? What is the AMA? Or the EFF? Of these organizations (or others), who I LOPSA's role model (I lean towards AMA)? We should model ourselves after a successful organization, even down to titles and labels. If we try to call ourselves "guides," with a communication ombudsmen -- or whatever -- that won't make sense to the very people we are trying to reach. But, more importantly, I think before we go trying to influence public policy, we need to focus on influencing ourselves, and our peers. We need to prove that our own industry takes us seriously. To Tom's point, this is focusing on education, curriculum, etc. There may be a place for an EFF style organization that focuses on sys admin issues. But given the limited resources of LOPSA, I am not sure that should be us. Yet. That's not to say we shouldn't have any voice. There may be instances were we would want to issue a press release that states how issue X is addressed by LOPSA tenant Y. That would probably be good PR to raise general awareness. Maybe we get some followups from the media, maybe not. But building our industry relevance should be of primary concern. _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
