Thanks for starting this thread. I hope there are lots of reqponses
as we are holding the Directors Face to Face meeting this weekend as
can use the input from members.
Here's a couple of thoughts in random order:
- Don't lock the mailing lists to members-only. Those people that
aren't members but on the list are here for a reason - they want to be
part of LOPSA, but haven't felt compelled to part with their money. In
advertising, that's the biggest hurdle. If you lock it out, you've
pissed off _the easiest potential members_.
- Why are people finding LOPSA? Ultimately the majority come across
looking for information to fix their current problem at hand, not
because of looking for secondary education reasons (some do, but not
that many). LOPSA could be providing the "why" to the solution they'll
find at stack exchange/et al (lopsa can't compete with SE's
size/backing). People will come back to find out why doing "x" in their
software makes things work better though.
- Why isn't LOPSA working with vendors to host/provide "best practice"
papers and processes.
- It's okay if papers are vendor specific. It really is. Really.
- People buy $250k+ SAN boxes regularly and have no idea how to make it
run in their environment at it's best. What's $100 when you just spent
a quarter of a million dollars or more, and don't know how to make it
run it's best or set it up wrong.
- What's $100 when you can find out in one place what $250k+ SAN box is
best for your environment _before you buy it_? (by being able to find
BCPs for multiple vendors in one place to compare against your environment).
- Dell/HP/etc will buy you steak + wine if you buy their gear (in large
quantity obviously), why not a lopsa membership? (hint - it'll reduce
their tech support costs)
R.
_______________________________________________
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/
