[All but the last bit of this piece was the early form of an essay
now on the Web at http://linuxmafia.com/faq/Linux_PR/newlug.html .]


Having seen (and helped run) quite a few Linux user groups (LUGs),
and seen some thrive and others die, I think I can hazard a few 
strong recommendations.  If you're thinking of starting a LUG, or
are running one now, please ponder these lessons from many other
LUG leaders' experience.  In fact, please consider reviewing this
list from time to time, as a checklist.

1.  You need a Web page.

I can't stress this enough.  The Internet is crucial to Linux:  It
made Linux possible, and is where everything happens.  If it's not
on the Net, your group might as well not exist.

2.  Your Web page needs a reasonable URL.

The usual http://www.some-isp.com/~randomuser/lugname/ isn't good
enough:  You want people knowing only your group's name to find you
easily.  http://www.lugname.om/ is therefore ideal.  Consider choosing
a group name whose Internet domain isn't taken, and then pay to register
the domain and get an ISP to virtual-host it.  It's not that expensive.

3.  You need a regular meeting location.  

If you keep moving around, you'll lose attendees like mad.  Why?  Because
some will come to the previous meeting location, instead, get discouraged,
and maybe even conclude that your group folded.  Because finding out how
to get there, where to park, whether the neighbourhood's OK to walk in,
etc., is a strain on people, every time you move.

The location doesn't have to be good:  I've seen a college cafeteria
suffice for one group, and a small downstairs room in someone's house
do well for another.  It just has to be reliably usable.

4.  You need a regular meeting time.

"Regular" usually means an easily-remembered-and-used formula for
people's calendars, pocket planners, and PalmPilots, such as 2nd Tuesday.
Don't get fancy with things like "every 2nd Thursday".  Make it so
anyone with a calendar can _easily_ figure out when the next meeting is.

5.  You need to avoid meeting-time conflicts.

Check out the schedules for nearby tech events:  Linux user groups, 
Perl groups, and whatever else your target audience is likely to want
to also attend.  Don't pick recurring dates that are already spoken
for.

Hint:  1st and 2nd Tuesdays, Wednesdays and Thursdays are all 
very popular.  The advantage is that they're easy to remember, and 
mid-week days are popular.  But, in my geographical area, there are 
(for example) four competing groups with first-Tuesday evening meetings.

6.  You need to make sure that meetings _happen_ as advertised, without fail.

One LUG in my area fell apart largely because the president set an
aggressive meeting schedule, but frequently failed to show up and
open the meeting space.  Would-be attendees would read the next 
meeting date from the Web page, show up, find a locked door, and
give up on the group entirely.  It's best to have multiple people
committed in advance to showing up early, and signs pointing to the 
meeting.

7.  You need a core of several Linux enthusiasts.

LUGs have succeeded wonderfully on the strength of ongoing efforts from 
as few as four energetic and inquisitive people.  That's really all you
need, but one or two are not enough.  E-mail is terrific for coordination.

Your core enthusiasts don't need any knowledge initially, but must be
self-starters, and _must_ have Internet access and know how to use it
well.

8.  You need to get on the main LUG lists, and keep your entries accurate.

http://www.ssc.com/glue/
http://lugww.nllgg.nl/
http://nlug.org/webring/
http://dir.yahoo.com/Computers_and_Internet/Software/Operating_Systems/Unix/Linux/User_Groups/
http://www.LinuxMall.com/LinuxUserGroups.html
http://www.currents.net/resources/usergroups/usanc.html
http://www.redhat.com/community/namerica.html
http://www.linux.org/users/
http://www.linux.com/Links/User_Groups/LUGs/
http://dmoz.org/Computers/Software/Operating_Systems/Linux/User_Groups/
 
Assign someone in your group to re-check your LUG list entries,
say, every quarter.  You'd be amazed how inaccurate they become 
over time.

An inaccurate entry is often markedly worse than none at all:  If it
directs prospective members to an obsolete URL, or to the wrong meeting
date, it will actively hurt your public outreach program.

Each major function of your group should have a Web page.  If you
start doing InstallFests, have an InstallFest page.

9.  You must have access to maintain your Web pages, as needed.

A static page that someone else emplaces for you isn't good enough.
You need to be able to fix/edit/enlarge it at the drop of a hat.
Typically, this means ssh (or telnet, if necessary) access to the
command shell on the hosting Web server.






You don't need to be in the Internet Service Provider business.

Leave the ISP business to the professionals.  You won't be able to 
beat their prices, so don't try.  When the moochers in your crowd 
ask for dial-in lines and shell accounts on the group's Web server,
say "No."

Don't go into any other business, either.

I hear of LUGs being suckered into the strangest, most cockamanie
business schemes.  Don't.  Don't try to be a Web design firm, a
technical support firm, and network design consulting firm, or a LAN 
cabling contractor.  Or any other business.  Not even if you're told it's
for a wonderful charitable cause.

Along the same lines, remember that you are not a convenience for
job recruiters:  If allowed, they will spam your mailing lists and 
abuse every possible means of communication with your members.  Nor
are you a source of computers for the underprivileged, a repair service 
for random people's broken PCs, or a help desk for non-Linux operating
systems and applications.  Believe it or not, you will be pestered by all
of the above sorts of strangers, on the "nothing ventured, nothing gained"
theory.





Referral pages
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="refresh" CONTENT="2; URL=http://www.newlocation.com/">
<TITLE>New location for FOO Home Page</TITLE>
<HEAD>
<BODY>
<H1>The FOO home page has moved!</H1>
The new location is <A 
HREF="http://www.newlocations.com/">http://www.newlocation.com/</A>
</BODY>
</HTML>


BALUG:
Good:  directions, RSVP link prominent.  
Bad: Only one upcoming event listed.  It's already in the past.
Mailing list Web archive is broken with no explanation.
No proper maintainer link.  No revision date.

BayPIGgies
Good:  Two upcoming events, prominently displayed.  Regular date and
time highlighted.  Maintainer link, revision date.  Mentions that
meetings are free and public.

CalLUG:
Bad: Irrelevant info up top (office location).  No real events 
schedule.  

NBLUG:
Bad:  Dates reported for InstallFest are contradictory.  No revision
date.
Good:  Dates are at least in the future.

SVLUG:
Bad:  Events aren't as prominent as they should be, nor is the date
formula (but it's there, at least).  No revision date.

SVPUG:
Bad: Not a reasonable URL, which is difficult to understand, given
that pm.org gives out DNS entries.  No regular meeting place.
Good:  Current info, and date formula is prominent

SlugLUG:
Good: Revision date.  Maintainer link.  Meeting formula up top.
Bad: Only one upcoming meeting, but at least it's in the future.

LUGoD:
Good:  Revision date.  Maintainer link.  Meeting formula highlighted
plus prominent "NOTE NEW SCHEDULE".