[Lopsa-regional-project] project start

[LOPSA-regional-support at LuftHans.com]

Am 09. Jan, 2006 schwätzte Jack Coats so:

> I suggest we have both LOPSA Chapters (a formal arrangement) and Affiliated
> Groups (a less formal, but supportave arrangement).

I think we will need to have both type of relationships.

What kind of groups do we want to seak out for affiliated groups?

LUGs? m$-admin groups? programming language groups? vendor groups? market
segment groups?

I think LUGs, *BSD group, Solaris groups, etc. make obvious affiliates
we'd like to work with. Some PC/m$ groups as well, but we're more likely
to run into pure end users who aren't likely affiliates[0]. Same with Mac
groups.

I think PHP, Perl, Java, etc. groups are potential affiliates. Maybe just
for cross-promotion of related events, e.g. a Perl group presenting on
managing Perl modules or a LOPSA event about PHP.

Would Oracle, Veritas, etc. groups make good affiliates for LOPSA?

I'm not completely certain what I mean by market segment groups. I am
thinking something like gov't or accounting IT groups, I think.

> If there are sucessful groups in an area, they might not want to turn
> over 'keys to their kingdom' to another group, but this might be a way to
> have currently existing groups become affiliated and, with active LOPSA
> members also being in these groups, share the benefits of networking,
> discounts, have invitations to LOPSA functions extended (members get
> discounts, others don't) to these groups and their members, etc.

I agree. We can't make every tech group out there an affiliate, though, so
we need to figure out which ones we want to work with and how we want to
work with them.

ciao,

der.hans
-- 
#  https://www.LuftHans.com/        http://www.CiscoLearning.org/
#  Join the League of Professional System Administrators! https://LOPSA.org/
#  Hope has two beautiful daughters: Anger and Courage. Anger at the way
#  things are, and Courage to struggle to create things as they should be.
#  -- St. Augustine