9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <evanhensbergen@austin.rr.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: Lucio De Re <lucio@proxima.alt.za>
Subject: Re: [9fans] plan9dev@googlegroups.com
Date: Mon, 26 Jul 2004 08:18:06 -0500	[thread overview]
Message-ID: <4105048E.6000500@austin.rr.com> (raw)
In-Reply-To: <cda06318108096c081cdca0b4d1da18a@proxima.alt.za>

Lucio De Re wrote:

>>The intent of this list is for people who are actually working on Plan
>>9 projects to be able to communicate. This is not an advocacy list,
>>nor is it a place to whine about incumbent operating systems or lack of
>>some functionality/application within Plan 9.
>>
>>
>
>I like the idea, but in my opinion the scope ought to be as carefully
>defined as possible to be worth subscribing in addition or
>alternatively to 9fans.  Nothing like some clear rules to
>self-moderate by ;-)
>
>++L
>
>
I'd really prefer it to be a development list - a place to talk about
what people are working on within Plan 9.  Whereas 9fans is more of a
user/advocacy list - where people ask questions about using existing
functionality, hardware support, installing a cpu server for the first
time, etc.

9dev would be more for discussing where we want to take the technology
--   What are the issues going to 64-bit, are there ways to tie Plan 9
functionality in better with incumbant OSs (ala plan9ports), etc.  With
only jmk being left in Murray Hill, the community really needs to step
up and start working towards the future, or stuff is going to just fade
away (no doubt to be reinvented later on).

The difference (for me), is that I only scan 9fans because the bulk of
it really doesn't interest me  -- and as a result, I miss some of the
important bits about what people are actually doing with the technology.

I know the prevailing sentiment is that Plan 9 is dead, and has been for
some time -- but I think there is still some hope to rally the troops
and work towards a community released "5th edition".  I also think its
well worth the community's time to improve/expand Russ' plan9ports stuff.

So, we'll see.  plan9dev is a list for people who actually want to/(have
time to) write code.  It is a place to post what people are doing
instead of wish-lists for what people should do.

    -eric



  reply	other threads:[~2004-07-26 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26  9:20 ericvh
2004-07-26  9:35 ` Lucio De Re
2004-07-26 13:18   ` Eric Van Hensbergen [this message]
2004-07-26 15:16     ` Jon Snader
2004-07-26 15:43       ` Justin Herald
2004-07-26 21:17     ` Steve Simon
2004-07-26 21:39       ` Roman Shaposhnick

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=4105048E.6000500@austin.rr.com \
    --to=evanhensbergen@austin.rr.com \
    --cc=9fans@cse.psu.edu \
    --cc=lucio@proxima.alt.za \
    /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).