[volunteers] (forw) Re: Web note re: recipe for successful LUG

Rick Moen rick at linuxmafia.com
Thu Nov 13 17:15:25 PST 2008


Possibly of interest for the anecdote from SVLUG history.
(I did, despite what I said, sit down and append a note about 301
redirects.)

----- Forwarded message from Rick Moen <rick at linuxmafia.com> -----

Date: Thu, 13 Nov 2008 15:48:59 -0800
From: Rick Moen <rick at linuxmafia.com>
To: [correspondent's name elided]
Subject: Re: Web note re: recipe for successful LUG

Quoting [correspondent's name elided]:

> In http://linuxmafia.com/faq/Linux_PR/newlug.html item 17, you suggest an
> HTML page in an old slot to alert people of a new location. Vastly
> preferable would be a status 301 URI redirect, as easily demoed for Apache
> configuration files as in the HTML page you suggest. 

301 via the httpd configuration indeed leads to ideal outcomes.  
The technique is obviously available only by those with site httpd admin 
access, plus requires implementation-specific explanations for each
likely (i.e., popular) httpd.  I'd strongly consider adding a paragraph
about how to do that -- much, much sooner if you write one.  ;->


The matter first came to my attention early in the history of Silicon
Valley Linux User Group, in 1997.  I set myself the task of figuring out
why attendance was stuck at almost always the same ten people at the
north San Jose Carl's Jr.'s community room, and why there was vague talk
of people out there thinking (in error) that SVLUG had ceased to exist.

I found that there were _two_ sets of Web pages for SVLUG.  One was at
http://www.worldtalk.com/~dkionka/svlug.html and was continuing to
public obsolete meeting information (wrong dates).  The other was
correct.  The former page was far better known.

I wrote Dan, and asked what the story was.  He said the Worldtalk page
was indeed obsolete, and should be disregarded.  I said, sure, but the
problem is that _only insiders knew that_.  I said he needed to fix or
remove the bad page(s).  No reply.

A month later, I pressed Dan on the matter again:  Why wasn't he fixing
or removing the page?  Mumble, mumble.  Eventually, Dan said the issue
was that he no longer worked at Worldtalk (had been laid off).  So, he
said, he didn't feel comfortable with telnet'ing in (this was 1997) and
editing files at a firm where he was no longer an employee.  Therefore,
his solution was to do nothing at all.

I thought about it for a moment, and e-mailed back pretty nearly exactly
the HTML example cited in "Recipe for a Successful Linux User Group", 
saying "Clip here, and please send to the sysadmins at your former firm,
with a note asking them to please replace
http://www.worldtalk.com/~dkionka/svlug.html with it".

He did that (finally), people consistently got to a _real_ SVLUG Web
site that no longer actively mislead them, and SVLUG meeting attendance 
immediately shot up to hundreds per month.

And, of course, Dan almost certainly could _not_ have pulled off getting
a 301 redirect implemented at a firm that had just laid him off, but the 
universal (if suboptimal) solution of a redirect replacement page was
easily achievable.


There are (at least) three lessons to that:

1.  If you want something done, there's nothing quite as helpful
as doing the "work" parts yourself.  (Hint, hint.)

2.  Doing nothing because you don't have the ideal solution handy, but
do have a pretty good one, is a stupid habit.  Especially if that
solution works everywhere.

3.  Telling a stranger that something would be an "easy" job (that you 
intend for _him_ to do) is rather unlikely to accomplish your goal --
especially if you're talking to someone who's been on the Internet for a
while and recognises the signs of someone considering his time to lack
value.

So, to repeat, if you want a pointer on implementing 301-code redirects
in popular http daemons added to "Recipe for a Successful Linux User
Group" sooner rather than later, you're invited to send me one.

----- End forwarded message -----




More information about the volunteers mailing list