Xref: utzoo comp.sys.amiga:16095 comp.sys.amiga.tech:52
Path: utzoo!mnetor!uunet!husc6!uwvax!dogie!uwmcsd1!ig!agate!eris!bryce
From: bryce@eris (Bryce Nesbitt)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Voting for comp.sys.amiga.tech (after a week)
Message-ID: <7694@agate.BERKELEY.EDU>
Date: 15 Mar 88 19:15:07 GMT
References: <5403@swan.ulowell.edu> <2372@unicus.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 35

In article <> craig@Unicus.COM (Craig D. Hubley) writes:
>In article <> page@swan.ulowell.edu (Bob Page) writes:
>
>Looks like it's a go.  However, the initial call for votes was about its
>existence, and explicitly stated that its name would be decided later.

No.  I made the initial proposal, and it was for ".tech".  The voting
for this group has a long and tortured history.  Compared to creating
a group, however, changing the name is easy.


>I suggest comp.sys.amiga.gurus, which I think has been suggested before.
>When people have to think about `does it belong there', then they think
>`am I a guru ?', or `did this cause a guru ?', which is about right.

The distinction I wish to see is "Am I creating some new {software,hardware}?".
".tech" is for the Bit Twiddling & Structure-Swapping crowd to work out how
to best twiddle & swap on the Amiga.  "How to get CMD_READ to work in
my new harddisk.device", "Here's how to write a virus" would be acceptable.

	>>> BEGINNER'S QUESTIONS ARE WELCOME in .tech, provided that	<<<
	>>> they are about how to get things done, programatically 	<<<
	>>> speaking.							<<<

".amiga" is for discussion on a less arcane level.  "How to hook up a
hard drive" and "what is a virus", for example.


>>>  ".tech" is is net-limbo at the moment.  Be sure to cast your votes
>>>	to: 	page@swan.ulowell.edu (Bob Page)

|\_/|  . ACK!, NAK!, EOT!, SOH!
{O_o} .     Bryce Nesbitt
 (")        BIX: mleeds (temporarily)
  U	    USENET: bryce@eris.berkeley.EDU -or- ucbvax!eris!bryce