9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Langdale Geoff_Langdale@GS10.SP.CS.CMU.EDU
Subject: comp.os.plan9
Date: Thu, 30 Mar 1995 13:32:56 -0500	[thread overview]
Message-ID: <19950330183256.sWuLlwUqyeh2MBXJ1IkuBXx8DTvNcanRMFS0BXoEWaM@z> (raw)


An alt group is probably not a good idea. Aside from the cruddy
distribution of alt, do we really want to saddle ourselves with
a such a low-rent title as alt.os.plan9? (alongside alt.os.multics
and alt.os.nachos, as it happens)

Over a year ago, I ran a proposal for comp.os.plan9 up the flagpole.
Not very many people saluted. Remember, in order to get comp.os.plan9
newgrouped we need 100 more YES votes than NO votes and a 2/3rds majority.
Taking into account the small group of troglodytes who vote NO to every
newsgroup proposal, that amounts to 110-120 YES votes. I never took the
proposal for comp.os.plan9 beyond the discussion phase, as at the time it
was obvious that we weren't going to get the required number of votes.
I decided that it was probably better to put off the proposal until a
general release of Plan 9, rather than get defeated from lack of interest.

Possibly, it's time to try again. The discussion of the newsgroup should
probably follow an announcement of the imminent availability of the general
release, just to drum up interest (half of the messages that I got after my
original proposal were people asking how they could get Plan 9). There's
certainly a need for a FAQ, but no need whatsoever for a moderator. If it
comes to that, we can work out comp.os.plan9.announce later (not to
mention comp.os.plan9.advocacy for the religious flamewars).

Geoff.






             reply	other threads:[~1995-03-30 18:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-30 18:32 Geoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-08-28 16:30 comp.os.plan9 Steven
1995-08-28 13:45 comp.os.plan9 Scott
1995-08-28  9:33 comp.os.plan9 Kiran
1995-08-28  9:19 comp.os.plan9 forsyth
1995-08-28  8:27 comp.os.plan9 dhog
1995-08-01 17:27 comp.os.plan9 Jim
1995-04-04  7:30 comp.os.plan9 Hans-Peter
1995-04-03  0:58 comp.os.plan9 Christopher.Vance
1995-04-02  0:29 comp.os.plan9 Scott
1995-04-01 21:38 comp.os.plan9 Gregg
1995-04-01 20:48 comp.os.plan9 Geoff
1995-04-01 11:36 comp.os.plan9 Harald
1995-04-01 11:28 comp.os.plan9 Martin
1995-04-01  3:59 comp.os.plan9 rob
1995-04-01  1:15 comp.os.plan9 rob
1995-04-01  1:08 comp.os.plan9 Bill
1995-03-31 22:56 comp.os.plan9 Jim
1995-03-31 14:14 comp.os.plan9 Dirk
1994-02-07  0:21 comp.os.plan9 Scott
1994-02-06 19:46 comp.os.plan9 Vijay
1994-02-06 17:15 comp.os.plan9 geoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19950330183256.sWuLlwUqyeh2MBXJ1IkuBXx8DTvNcanRMFS0BXoEWaM@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).