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:36:45 +0100 (GMT+01:00)	[thread overview]
Message-ID: <a8c653f2-9205-42f0-b78a-1befe57ef233@sirjofri.de> (raw)
In-Reply-To: <17062564930.ACf5A79A0.23655@composer.9fans.topicbox.com>

Hello again,

26.01.2024 09:08:29 Vester "Vic" Thacker <vester.thacker@fastmail.fm>:
> 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.

There currently is no project 5e. That's why there's no need for a core team, but people to start the project.

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

This will happen somewhat automatically once people are there who do the work. There's no need for an official core team.

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

Who/What attracts the attractors?

People will join when it's attractive to join. What do you offer to the core team besides your vision?

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

There are no resources yet that should be directed. I can only see a vision and you who offers the vision. Do you also offer other resources like code?

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

That needs people who do the work.

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

As you can see in the inline responses, you first need people who do the work. Without that, there's no need (and also no opportunity) to build a core team.

You can, however, start yourself and wait for people to join. Be the core and don't just wait for the core.

You can even build a company and hire people to get things started faster. But that again needs resources: money.

Note that I'm not opposed to your general vision. There are many very good aspects in there. I just can't envision that in an official 5e release, but in another fork (maybe of an existing fork). I personally would think it's best to built upon 9front, because they have good hardware support already. And there's many great ideas in that bubble, some of them get rejected.


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

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

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

  git send-email \
    --in-reply-to=a8c653f2-9205-42f0-b78a-1befe57ef233@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).