9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@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 14:29:29 -0500	[thread overview]
Message-ID: <a4e6962a0907181229o4f25f75biaf2427a399801f59@mail.gmail.com> (raw)
In-Reply-To: <13426df10907181059u192b75a6tefb37e56e3772f5@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
>

I once attended a talk where a statement was made about open source
projects being defined by their ability to fork in non-destructive
manners as a sort of evolutionary response.  Plan 9's source code is
available, and anyone that thinks they can do a better job is welcome
to fork it, repackage the distribution, mirror it, support it, and so
forth.  People will naturally flock to better solutions.  This is the
very heart of open source.  Conforming to Google's idea of open
source, or the Linux Community's model, or the GNU religion is in no
way essential to open source.  What is essential is that the community
works out what works best on its own and evolves through forking and
merging and different approaches which work best at different times.

Forks are already in place.  Inferno is very much a fork of Plan 9,
Octopus is a fork of Inferno. Brucee has his own fork (or perhaps
forks?) of Inferno.  p9p and 9vx are also forks after a fashion.
These forks often contribute fixes and improvements back to respective
parents, and some times they don't.  The secret plan 9 super secret
society fork is yet another evolution, actually primarily motivated by
bitter, disruptive, and ultimately destructive community members.  All
things are valid, evolution only moves forward with action.  We have
our fork, we are proceeding with it as we best see fit -- that's our
prerogative.  Unhappy?  Restless? Bored?  Go forth and fork -- IMHO,
this is a research operating system, its here to play with, learn and
explore.  If you aren't interested in those things, you'll be
disappointed or worse.

      -eric



  reply	other threads:[~2009-07-18 19:29 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
2009-07-18 19:29       ` Eric Van Hensbergen [this message]
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=a4e6962a0907181229o4f25f75biaf2427a399801f59@mail.gmail.com \
    --to=ericvh@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).