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

Adam S. Moskowitz adamm at menlo.com
Wed Feb 1 04:21:38 PST 2006


der.hans wrote:
> 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.

I still don't understand what benefit there is to the local group to be
a partner and not just an affiliate. Why would a small, loosely-organized
group (like BBLISA) want to commit to "at least one event per year?" Are
you saying LOPSA would help organize and promote events only with/for
partners? What if an affiliate wants to do a one-time event, or an event
less than once a year; would LOPSA say "no, you're not a partner?"

Also, what happens if a local partner group doesn't hold "their" event
one year? Do they get busted down to affiliate? What if they want to
hold it but LOPSA can't commit that year?

You don't list any group benefits for either affiliates or partners; why
not? Surely they need to be part of the grand proposal we submit to the
LOPSA board, no?

I really think a lot of our effort, maybe even most of our effort, needs
to go into what LOPSA can offer the local groups. Again, in most cases,
LOPSA needs them far more than they need LOPSA.

AdamM


More information about the Lopsa-regional-project mailing list