9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Juhani Forsman <jf@vrl.jyu.fi>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Formation of a Plan 9 Core Team
Date: Fri, 26 Jan 2024 11:09:45 +0200 (EET)	[thread overview]
Message-ID: <8099bd2c-d586-da81-db6-e65be4f4232@vrl.jyu.fi> (raw)
In-Reply-To: <17062564930.ACf5A79A0.23655@composer.9fans.topicbox.com>

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

Honestly speaking, in current situation this tastes a bit for 
administration for the sake of administration. In my opinion it would be 
more fruitful to bring together at first the niners with similar goals and 
needs i.e. "SIGs" at first which could form the core later if necessary


On Fri, 26 Jan 2024, Vester "Vic" Thacker wrote:

> When looking at the FreeBSD project, the introduction of a Plan 9 Core Team can offer several benefits:
>  1.
>     Centralized Technical Leadership: A Core Team can provide clear technical leadership and direction for the project. This ensures that development efforts are
>     coordinated, focused, and aligned with the project's goals.
>  2.
>     Consistency and Stability: With a dedicated Core Team, there is a better chance of maintaining consistency and stability in the development process. This can lead to
>     more reliable and predictable updates.
>  3.
>     Efficient Decision-Making: The Core Team can streamline decision-making processes, especially for critical technical decisions. This can help avoid delays and
>     conflicts that might arise in a more decentralized development model.
>  4.
>     Attracting Contributors: Having a well-defined leadership structure can make the project more attractive to potential contributors, as they can see a clear path for
>     their contributions and how they can impact the project's direction.
>  5.
>     Community Cohesion: A Core Team can act as a unifying force within the community, bringing together contributors from various Plan 9 distributions and projects. It
>     fosters collaboration and cooperation.
>  6.
>     Long-Term Sustainability: By focusing on technical governance, a Core Team can help ensure the long-term sustainability of the project, making it less reliant on the
>     efforts of a single individual or a small group.
>  7.
>     Representation: The Core Team can include representatives from different Plan 9 distributions, ensuring that various voices and perspectives are considered in the
>     decision-making process.
>  8.
>     Resource Allocation: The Core Team can allocate resources more efficiently, directing efforts towards areas that are most critical to the project's success.
>  9.
>     Enhanced Documentation: With a centralized team, there's often a better opportunity to maintain and improve project documentation, making it easier for newcomers to
>     understand and contribute to the project.
>  10.
>     Fostering Innovation: A Core Team can actively promote innovation and new features, driving the evolution of the Plan 9 operating system in a direction that aligns
>     with the community's needs and goals.
> --vic
> 9fans / 9fans / see discussions + participants + delivery options Permalink
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8d272411830cebfc-Mee7183485baa66140167edbb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-01-26  9:10 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 [this message]
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:

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

  git send-email \
    --in-reply-to=8099bd2c-d586-da81-db6-e65be4f4232@vrl.jyu.fi \
    --to=jf@vrl.jyu.fi \
    --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).