🚀 go-pugleaf

In article <34g02n$mpr@news.ycc.yale.edu> una@doliolum.biology.yale.edu (Una Smith) gibbered like a rabid baboon:

>>If I was a newbie interested in museums I would ignore a
>>sci.infosystems.museum figuring it to be a group dedicated
>>to computer systems in museums. ...
>
>That's the idea.  The newsgroup in question would be gated
>to an large mailing list of professionals who run museums.

How about *.museums.admin, then?  That way I'll be sure not to subscribe.

(I still like rec.buildings.* ).

>>I can see misc.museum (or sci.museum) being a good name, easy to split
>>when traffic becomes higher.
>
>The MUSEUM-L subscribers probably don't want high traffic.

The solution to this is to give the newsgroup a hard-to-understand name?
It seems like a better solution would be to hide it in a completely 
unexpected place, such as comp.compression.research.museums.  Maybe
comp.lang.cobol.museum.

@Man

PS: 

Oh, since Museums tend to have full-on nappy concrete architecture with
lots of nifty sloped sections, I motion that we consider
alt.skate.museums, or alt.skate.museums.shredding.

               
             O
            'I`
            _I_ 
           |   |
           |_|_|
        \   # #   /
         -+-=-=-+-
          o     o

      "Skater De Milo"
-- 
shaunc@faceplant.gvg.tek.com  ||  PGP public key available on request

"Anchovies, sometimes referred to as sardelles, discreetly added to food,
can bring a piquancy the source of which is most difficult to trace." -- JoC