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 12:47:09 +0100 (GMT+01:00)	[thread overview]
Message-ID: <d9dfc8f8-0b87-46e8-ae6e-a15f41dec41d@sirjofri.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2955 bytes --]

26.01.2024 10:49:42 Frank D. Engel, Jr. <fde101@fjrhome.net>:

> From my perspective, Plan 9 was split into two forks: 9legacy for people who don't want it to move forward but simply to be maintained, and 9front for people who want the project to move forward and continue to grow.
> Having a core team for "Plan 9" at this point would be kind of pointless as the name was a real product at one time but now encompasses a collection of related forks of what was once a product, so such a team would need to form around one particular fork.
> Having a core team basically expresses the goal of moving the project forward, so if a core team were to form right now, it would be for 9front, or around a new fork with a similar set of common ideals (maybe we move on to Plan 10?), since moving forward is kind of the antithesis of what 9legacy seems to be about.

That sounds about right. Basically everything you said.

Any attempt to release an official new edition of Plan 9 would be a fork.

I personally think it is ok for 9legacy to just maintain the original version and not move the project forward. I think 9front tries to stay as compatible as possible at runtime (so same binary formats, same protocols, basically Plan 9 4th "plus").

What OP wants might include breaking changes that break compatibility on some system layers. Probably not on a level of protocols or something, but filesystems might change, probably a complete new window manager, graphics acceleration, a different plumber and lots and lots of more "modern" software (anyone wanna port firefox or chrome? ;) ). That might really be a Plan 10 at some point.

I very much believe that this should be a fork, probably with some kinda package manager to make larger parts optional. Not everyone needs everything. Plan 9 as it is right now can include many things without asking, because they're so small. Imagine bundling a 100M graphics driver with Plan 9, including the source! No, thanks.

Back to topic with some question to the OP (and please, please, don't take it personally or something): Is it possible that you want to contribute to Plan 9 but don't know where to start? I remember, when I started with Plan 9, I wanted to improve many things, contribute everything I could, until I realized that many things are like they are on purpose. I was often grounded by people like ori, hiro, mycroftiv, kvik and a few others on grid, as well as cat-v. I learned that being part of Plan 9 does not necessarily mean contributing large chunks of code, or changing many things to be "better" (whatever better means).


P.S.: sorry Frank, I clicked the wrong reply button. Of course this should go to the mailing list.

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5bdb5197344e4e7f-Mca2888763f27456d047a1d2e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 4477 bytes --]

             reply	other threads:[~2024-01-26 11:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 11:47 sirjofri [this message]
2024-01-26 22:31 ` denzuko
2024-01-27  0:09   ` Vester "Vic" Thacker
  -- strict thread matches above, loose matches on Subject: below --
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
2024-01-26 14:49   ` hiro
2024-01-26 17:11     ` Lucio De Re
2024-01-26 14:49 ` ori

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=d9dfc8f8-0b87-46e8-ae6e-a15f41dec41d@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).