DB> I am a member not by "choice" at this point but because I am
DB> "captured", like a union-shop employee, unable to go to a given
DB> conference without kicking up to the local capo who ensures that
DB> everything runs smoothly because that's a really nice conference
DB> you've got there, it'd be a shame if anything happened to it.
That's not my sense of how this works; it's more like if you go to the
conference, you get a free membership. In particular, I assume that if you
declined the free membership, they wouldn't kick you out of the
conference, right?
(Also, that LOPSA isn't actually threatening to wreck these conferences if
not enough people join LOPSA, which is sort of what it sounds like you
were implying there.)
My two cents are:
(1) There's nothing wrong with "capturing" members this way. It means your
membership numbers don't reflect "how many people think our
organization is a worthwhile organization to pay $50/yr to join",
because lots of your members joined without having to pay for it, but
as long as you know that, that's fine. In particular, it has the
advantage of giving people a free trial, so they can understand from a
year of experience why membership *actually is* valuable, rather than
trying to guess based on a list of benefits whether a year of
membership *hypothetically will be* valuable.
(2) Someone should check the archives to see how often this topic comes
up, and write a cron job to start a thread about it at the appropriate
time, so we don't have to keep remembering to do it by hand.
Automation, people! Is there an Ansible playbook for this?
Shrug.
-Josh ([email protected])
_______________________________________________
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/
