9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Formation of a Plan 9 Core Team
Date: Fri, 26 Jan 2024 09:25:45 +0100 (GMT+01:00)	[thread overview]
Message-ID: <d975505e-f580-4bb9-a990-3df34552ed52@sirjofri.de> (raw)
In-Reply-To: <17062539860.b17123c.899285@composer.9fans.topicbox.com>

Hey Vic,

I followed the other thread and read through your initial mail. Here's my thoughts.

I don't think the development of another mainline release or the formation of a core team really makes sense. A core team is built around a solid vision and the ability (and want) to follow that.

My suggestion is, you just start building your own distribution based on your vision and people can join. I just doubt that this will end up being 5e, especially because there's nobody who's willing to give it a 5e stamp.

That said, we have "official" plan 9 releases: 4th is "officially" 4th, 9front is "officially" 9front, and 9legacy is "officially" 9legacy. It's ok to let history be and start building new stuff based on what happened in the past 15 years instead of building on a state 15 years ago and hoping for a magical stamp to give you an "official" branding.

People don't care if they're using an "official" system. People use linux, which is not unix. People use 9front, which is not plan 9. Many good things started as forks, and that's ok.

Forming a core team is like forcing people into a vision without a base. Maybe they'll start, but there's no guarantee. It's more likely they'll just leave and that was it.

If you take a look at FreeBSD, they started more or less as something like 9legacy, and they continued to be 9legacy. They never were "official" 386BSD, they even looked for another name, which ended up being "FreeBSD".

I'll write another mail as response to your new mail.


9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8d272411830cebfc-M995ec6ebe520824e44358edb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-01-26  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  7:26 Vester "Vic" Thacker
2024-01-26  7:55 ` fig
2024-01-26  8:08   ` Vester "Vic" Thacker
2024-01-26  8:36     ` sirjofri
2024-01-26  9:09     ` Juhani Forsman
2024-01-26  8:25 ` sirjofri [this message]
2024-01-26 14:49   ` hiro
2024-01-26 17:11     ` Lucio De Re
2024-01-26 14:49 ` ori
2024-01-26 11:47 sirjofri
2024-01-26 22:31 ` denzuko
2024-01-27  0:09   ` Vester "Vic" Thacker

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:

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

  git send-email \
    --in-reply-to=d975505e-f580-4bb9-a990-3df34552ed52@sirjofri.de \
    --to=sirjofri+ml-9fans@sirjofri.de \
    --cc=9fans@9fans.net \


* 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).