Hello Ozdk,
There are a number of resources that provide ideas on how to set up
and maintain user groups. There does not seem to be a guide
specifically for Sybase, but here are some resources that should help.
Recipe for a Successful Linux User Group
http://www.linuxmafia.com/~rick/essays/newlug.html
A little bit rambling, but it does has a pretty good organization of
issues to consider. Starts with a 23 item list of issues and closes
with three addenda that address association with a parent group, a
checklist, and other references.
Linux User Group HOWTO
http://www.tldp.org/HOWTO/User-Group-HOWTO.html
A more structured document on the same topic as above. Has a different
emphasis as well; for example, one section is on legal and "political"
(strong opinions held by participants) issues.
Association of Personal Computer User Groups
http://www.apcug.org/links.htm
In particular, check the page "How to start a UG". This seems to be a
more formal site. It suggests early emphasis on a good plan (financial
and technical) as well as getting legal protection.
Apple - User Groups - Leader Resources
http://www.apple.com/usergroups/leaders/
A good example of how a vendor works to support user groups with
guides and pointers to speakers, suggestions, and so on.
Sybase and PowerBuilder User Group (Switzerland)
http://www.spbug.ch/hist2000.htm
A group that charges a reasonably high fee (CHF 100 individual, CHF
300 corporate) and only plans to meet three times per year (but for a
whole day each time). Part of the expense is to fly in speakers from
other countries. Something to consider or a group to contact for
hints.
Google Directory - Computers > Software > Databases > Sybase
http://directory.google.com/Top/Computers/Software/Databases/Sybase/
this is a general reference list but includes a few other Sybase user
groups you can contact.
There were over 3000000 hits for the search phrase
"how to" user group
and most of the references above came from the first page. The last
few came from a "search within these results" by adding the phrase
Sybase
to get a new (much smaller) list. Note that the Sybase specific
references are to existing groups, not specifically about setting up a
new group.
To the specific questions, I can't find a specific reference for most
but will comment on each in turn.
1. How can I get people interested in attending?
Offer something they are interested in. Using Linux as an example,
several groups offer on a regular basis (e.g, quarterly) a workshop on
setting up a PC to run Linux. Make it worth their while to pay to
participate and attend.
2. How can I get attendees interested in being more involved, such as
to
make small presentations?
Hmm. You could pay them (perhaps a year free if they speak). You make
sure you publicise the meeting (local newspaper) and their expertise.
There are a number of methods suggested by the references I provided.
A search phrase such as
user group encourage speaker
is not too specific, but can be used to find a few more ideas.
3. Do you have examples of how other small user groups set themselves
up
and how they became sustainable?
See the references I provided above (the Sybase ones in particular).
Perhaps the most important part is to have a plan and income /
participation that exceeds that plan.
4. Do you have any other tips on conducting meetings?
There are a lot of good resources for holding meetings. If you want it
to be more formal - I suggest learning how using a resource such as
"Toastmasters International"
http://www.toastmasters.org/
which has groups around the world to help people become good speakers
and improve their leadership skills. Organization and running the
meetings is a part of what you can learn from them.
5. What role would non-technical gatherings, such as the occasional
dinner or movie or bowling etc have on the primary focus of having
members keen on attending and particpating technical group sessions?
It depends on what type of goals you have. The group in Switzerland
mentions having paid lunch as part of each meeting. It does not
describe much activity separate from the technical meetings. I can't
be sure - perhaps an email would clarify that.
My suggestion for now is to avoid that kind of activity. For example,
the first reference has a special caution to avoid business
opportunities. It is not that the group might have good intentions,
but it diverts from the original goals.
Good luck with your group!
--Maniac |