Next message: Sea Quell crew.: "lv-ab: Teen sailing opportunity, Seattle area."
Yahoo is pretty cumbersome, so a "private" server would be nice.
Setting up a serious backup for the list and the archives should be a priority - in the computer world it's easy to lose everything in a second. I'd suggest a form that would the most easily recoverable by the most software packages; save it online and also in two or more geographical locations (snail-mail media to archivers once a week?? - once a month?) purely for insurance. That provides a way for the list to survive various upheavals, but the backups would still need to be transferred when one repository decided he needed to pass the baton. However, if a single backup media condtains ALL the archives and the list (single DVD?), then it would be pretty compact and two or three disks would provide redundancy in a tiny package.
Just my .02. I was/am associated w/a group of outdoor enthusiasts who need to rent 100 acres or so for a couple weeks each year. To do this our predecesors compiled a book of photos, sample documents and appreciation letters from local and federal authorities, landowners and local township officials; they used the book as a history and a tool to present themselves when bidding for land use. It's all a volunteer organization with the inefficiencies you'd expect and somehow the book disappeared a couple years ago. This created a really serious problem; fortunately the membership list was handled separately and many agency and government names and contact info could be retrieved. from individuals. But it entailed a huge amount of work and we undoubtedly lost out on some wonderful open spaces for lack of convincing documentation of the group's bonafides.
So I flog the backup issue whenever I get a chance.
Cheers.
Rufus
--
We've Got Your Name @ www.mail.com!!!
Get a FREE E-mail Account Today - Choose From 100+ Domains
___________________________________________________________________________
|| The Live-Aboard List : send a "subscribe" or "unsubscribe" request ||
|| in body of message to: ||
