9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: fig <type9freak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Formation of a Plan 9 Core Team
Date: Thu, 25 Jan 2024 23:55:34 -0800	[thread overview]
Message-ID: <CANF_3RhQ0Jn2yh3WpFV-XmEOdokU614hfYW15P8ODJQUdH-DJA@mail.gmail.com> (raw)
In-Reply-To: <17062539860.b17123c.899285@composer.9fans.topicbox.com>

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

What would the benefits be of adding hierarchy systems like this?

On Thu, Jan 25, 2024 at 11:26 PM Vester "Vic" Thacker <
vester.thacker@fastmail.fm> wrote:

> Is there interest in establishing a dedicated Plan 9 Core Team to
> spearhead its technical development? When we look at other communities like
> FreeBSD, they have both a foundation and a core team, with the latter
> overseeing the technical aspects of the project. If this idea resonates
> with you, then the idea of selecting members for the Plan 9 Core Team is
> worth considering.
>
> It's important to note that the Plan 9 ecosystem consists of multiple
> distributions. It's possible that the technical leaders of these projects
> might be willing to step up and contribute their expertise to the Plan 9
> Core Team, offering valuable guidance and facilitating the development of a
> new mainline.
>
> The Core Team's responsibilities would include making the tough decisions
> required to chart the future course of Plan 9. What are your thoughts on
> this proposal?
>
> --vic
>
>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/T8d272411830cebfc-M1cd4fdf08865e0eeb765c470>
>

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

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

  reply	other threads:[~2024-01-26  7:55 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 [this message]
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
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:
  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=CANF_3RhQ0Jn2yh3WpFV-XmEOdokU614hfYW15P8ODJQUdH-DJA@mail.gmail.com \
    --to=type9freak@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).