[Lopsa-regional-project] chp/partner/affiliate

[der.hans]

Am 19. Jan, 2006 schwätzte Adam S. Moskowitz so:

> der.hans wrote:
>> (a lot of stuff)
>
> How about we start with defining *WHY* we want the different levels of
> affiliation. Specifically, what benefit is there to LOPSA for each of
> the proposed types of affiliation, and what benefit would there be to
> "the other group?" Exactly what services would LOPSA provide and exactly
> what would LOPSA require of each type of affiliate?

Why is because I think there will be varying levels of partnership with
different organizations.

> For "Affiliate" this is clear (as der.hans stated): "The relationship is
> mostly ad hoc co-promotion."
>
> But what about the others? Do we need them? If so, why?

Here's how I see it for now.

At the affiliate level we have someone, the LOPSA member liaison, working
to promote LOPSA events/services/whatever with the affiliate when
appropriate and passing affiliate info up to LOPSA when appropriate.
Basic, low-level, ad hoc co-promotion.

At the partner level LOPSA members are members of the organization. LOPSA
and the organization organize and promote at least one event per year.
This is a place for non-chapters to build a consistent relationship with
LOPSA. I think BBLISA would fall into this category as it probably doesn't
want to be an actual LOPSA chapter.

At the chapter level there is a symbiotic relationship between the two
organizations. Chapters could: get whatever affiliates and sponsors can
get; have LOPSA-based logos; be tied into LOPSA web site, membership and
dues paying mechanisms; get discounts to LOPSA events; get LOPSA swag for
giveaways; get service hosting from LOPSA; and event listings in main
LOPSA calendar; get assistance from LOPSA in building corporate
partnerships.

Maybe some partners approach the cooperation levels of chapters. Maybe we
just need multiple levels of group partnerships. For now I think we're
good with the 3 levels.

> One thing we could do is get in touch with the IEEE and the ACM and ask
> how they do it. Then, get in touch with some of the locals on the other
> end of those arrangements and ask whether the particular type of
> relationship has helped, and in what way?

Good idea. Anyone work with either of the organizations and want to find
out how they do partnerships?

>> I think the tasks can mostly be done in parallel although board buy in
>> is something we should get sooner than later.
>
> I've said this to the Board, now I'll say it to this group: LOPSA needs
> to develop a business plan before they do anything else. That business
> plan needs to spell out what LOPSA's goals are and what they plan to do
> in the next 1-2-5-10 years to meet those goals. Until that business plan
> exists, the Board shouldn't be "buying in" to anything.

I understand your concern, but last week Doug said to keep going while the
board works on the business plan.

A couple of board members have told me that the current list of volunteer
projects are sanctioned by the board and that the board wants progress to
be made :).

ciao,

der.hans
-- 
#  https://www.LuftHans.com/        http://www.CiscoLearning.org/
#  Join the League of Professional System Administrators! https://LOPSA.org/
#  The most likely way for the world to be destroyed, most experts agree,
#  is by accident. That's where we come in; we're computer professionals.
#  We cause accidents.  -- Nathaniel Borenstein