9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] Formation of a Plan 9 Core Team
Date: Fri, 26 Jan 2024 09:49:26 -0500	[thread overview]
Message-ID: <AEC38E099B90358C0CD2FC94E7BC245C@eigenstate.org> (raw)
In-Reply-To: <17062539860.b17123c.899285@composer.9fans.topicbox.com>

In my experience, an open source team forms when
someone does work.  If the work is good, others join
in.  They start with someone taking initiative to

Eventually, it may make sense to put in some
bureaucracy, as people doing the work struggle to
communicate effectively.

Right now, it appears that (outside 9front) the problem
is the opposite -- there's a lot of folks trying to
communicate a direction, but far too few sharing code.

It may be worth quoting the FreeBSD wiki on what their
core team does:

    The FreeBSD/core team manages the project as a
    whole.  In theory, they set the long term goals and
    agenda for development and then delegate the
    implementation of these goals to the appropriate
    teams.  In reality, the groups of developers doing
    work in a particular area tend to have an even
    greater say in the direction of the project.  The
    core team has historically recognized this and
    gives great deference to active, productive members
    of the community in matters of direction.  Core,
    and its members, encourage the developer community
    to work together towards a consensus driven final
    goal.  Core rarely explicitly endorses these goals,
    but often takes note of progress or its lack in
    areas important to the project.

Again, it's worth emphasizing here that the FreeBSD
core team sees its job as facilitating consensus, and
dictating direction is a failure mode rather than the
common outcome.

Don't worry: if you start setting a direction and
making progress, you'll have a peanut gallery chiming
in and trying to chart the work you do.  If you're
lucky, some may even help.

Quoth Vester \Vic\" Thacker <vester.thacker@fastmail.fm>:
> 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: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8d272411830cebfc-Mb98bf58b1bd32699b4a025de
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-01-26 14:49 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
2024-01-26 14:49   ` hiro
2024-01-26 17:11     ` Lucio De Re
2024-01-26 14:49 ` ori [this message]
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=AEC38E099B90358C0CD2FC94E7BC245C@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).