9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about Plan9 project
Date: Sat, 18 Jul 2009 10:59:20 -0700	[thread overview]
Message-ID: <13426df10907181059u192b75a6tefb37e56e3772f5@mail.gmail.com> (raw)
In-Reply-To: <5d375e920907180959p1a7630eaj4d089c750b803e5f@mail.gmail.com>

On Sat, Jul 18, 2009 at 9:59 AM, Uriel<uriel99@gmail.com> wrote:

> Plan 9 is *not* an open source project, it can hardly be called a
> project even: There is no release management, there is no development
> process, there is no way to know what anyone is working on, no way to
> have any idea of what changes and features to expect in the future or
> when, or when any given bug might be fixed, or even a bug database for
> that matter,


This is an interesting statement and should be revised. So let's correct it.

Take that above text and add this, please:
"That is visible to Uriel, or that will ever be visible to Uriel, or
that Uriel has any possibility of influencing, given that Uriel has
burned every last bridge he might have ever had with the Plan 9
developers to the ground.".

> So you are on your own, you can take the code (while the site happens
> to be up, or from a mirror), do whatever you like with it, but that is
> all there is and all anyone can count on.

So, let's revise this one too..

"I, Uriel, taking up Noah Evans offer, will be forking the code base
and releasing an OS called Plan-U. I will provide servers that resolve
all the problems seen with the bell labs server, and I will take on
the task, with my friends, of providing all the things I see lacking
in the current setup. It's much easier to contribute a solution than
complain, and I am not the type who gets perverse joy out of just
complaining and yelling at people on a mailing list. That game is for
losers. Rather, I wish to provide a constructive solution, and I know
that after a few months people will ignore the bell labs site and
flock to mine. It worked for openbsd, and it can work for Plan U. As
part of this effort, I hereby unsubscribe from this list, and am
starting a new one called ufans for my new OS release. Please join me
in this important work. "

There now, wouldn't that be much easier? You already run a bunch of
servers; I think you could pull it off. And it might lower your blood
pressure :-)

You declined Noah's serious offer to take over sources; here's another
chance! Go for ti! You should not assume it would not work.

Ron



  reply	other threads:[~2009-07-18 17:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 15:10 Adriano Verardo
2009-07-18 16:18 ` Skip Tavakkolian
2009-07-18 16:25 ` Anthony Sorace
2009-07-18 16:59   ` Uriel
2009-07-18 17:59     ` ron minnich [this message]
2009-07-18 19:29       ` Eric Van Hensbergen
2009-07-18 19:37         ` Corey
2009-07-18 19:50           ` Eric Van Hensbergen
2009-07-18 20:01             ` J.R. Mauro
2009-07-18 20:11             ` Corey
2009-07-18 23:21       ` Corey
2009-07-20 12:16       ` Iruata Souza
2009-07-18 20:40   ` Adriano Verardo
2009-07-19 12:38     ` Ethan Grammatikidis
2009-07-18 16:39 ` erik quanstrom
2009-07-18 18:35 ` dorin bumbu
2009-07-18 18:49   ` J.R. Mauro
2009-07-18 19:09   ` Adriano Verardo

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=13426df10907181059u192b75a6tefb37e56e3772f5@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=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).