At 3:42 PM -0700 5/3/98, David B. Smith wrote:
> If a maillist is a particular technological structure of hardware and
> software, then I suppose knowing how to run that hardware and software
> is required for competency.
*Someone* has to know how to run the servers. But the task of running
the server and the task of running the list are not necessarily the
same person. I think this list is stacked with folks who more or less
run their own show, and that bias is quite evident.
My job is to do the plumbing, so that the folks at Apple who use mail
lists can focus on content. A bit part of the work I've done building
things is to set things up so people DON'T need to know the grimy
details to get THEIR job done.
In fact, I'd break it down into three jobs, which can heavily overlap
depending on the situation -- the person who runs the list server, the
person who runs the list, and the person who manages the content on
that list (as moderator, list mom, friendly uncle, or whatever). So you
need three separate skills definitions, and it may or may not be
multiple people.
Server operator: general server operations. postmaster mail. Intercedes
when all hell breaks loose. Makes sure everything runs.
List operator: handles the specific of the list. The primary difference
beween this one and teh server operator is that I view this as where
bounce processing and subscribe/unsubscribe intervention handles for a
list.
content operator: moderator, content cop, list mom. Name your poison.
The person who's actually IN the list making decisions on what is and
isn't posted to the list.
Two "jobs" are operational, one editorial. And how you split up the
"jobs" depends on the people, the server, and the organizational. For
most lists, I'm server and list operator, but for most lists on my
site, others are content -- and it makes sense for a technical person
to deal with the technical stuff, and let the folks worry about the
information.
> Makes me wonder why folks gave up on BBS networks -- where after all,
> the Sysops provided the necessary technical savvy and security, and the
> conference hosts conducted the discussions. Maybe someday, when
> civilization reaches this part of the High Plains.
Because the costs of the internet dropped to the point where it was
cost effecive to connect to the net, instead of dealing with the BBS
with/without a phone dialup setup. Eventually, technology just overtook
BBSes. And if you look around, a bunch of them (and/or their operators)
are actualy still around, but doing it via Internet instead now in
various forms.
sort of like asking why folks switched USENET from phone/UUCP
connections to NNTP connections. Because the technologies and costs
changed....
--
Chuq Von Rospach (Hockey fan? <http://www.plaidworks.com/hockey/>)
Apple Mail List Gnome (mailto:[EMAIL PROTECTED])
Plaidworks Consulting (mailto:[EMAIL PROTECTED])
<http://www.plaidworks.com/> + <http://www.lists.apple.com/>
