feat: update goals, roadmap, and add forum link
This commit is contained in:
parent
d697f2daf3
commit
134cc83632
GPG key ID:
9762169A1B35EA68
|
|
@ -4,52 +4,54 @@
|
|||
|
||||
<section id="goals">
|
||||
<h2 class="title">Goals</h2>
|
||||
<ol>
|
||||
<li class="goal">
|
||||
<h3 class="name">Independent</h3>
|
||||
<p class="description">
|
||||
We will fork and maintain Nix, NixPkgs, and NixOS. Additional support
|
||||
for projects such as Nix Darwin and Home Manager will be considered.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Governance</h3>
|
||||
<p class="description">
|
||||
A democratic model of governance with elected positions will be used to
|
||||
manage the project. A steering committee will provide direction with
|
||||
additional committees handling specific logistical tasks. Features or
|
||||
individual projects will be owned by Special Interest Groups. SIGs will
|
||||
collaborate within Working Groups to achieve their goals. Each committee
|
||||
and group will have its goals, requirements, and management process
|
||||
clearly defined.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Stabilization</h3>
|
||||
<p class="description">
|
||||
User-friendly features such as the Nix v3 CLI will be enabled by
|
||||
default. Nix Flakes are used too heavily to remove or change and will
|
||||
instead be stabilized as a v0 in its current state with any future work
|
||||
being handled by a Special Interest Group.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Infrastructure</h3>
|
||||
<p class="description">
|
||||
We will build and maintain the tools and infrastructure necessary to
|
||||
keep the ecosystem healthy, including Continuous Integration and Binary
|
||||
Caching.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Education</h3>
|
||||
<p class="description">
|
||||
Unified documentation, tutorials, guides, and examples will provide a
|
||||
better onboarding experience for newcomers and a faster iteration cycle
|
||||
for experts.
|
||||
</p>
|
||||
</li>
|
||||
</ol>
|
||||
<div class="goals">
|
||||
<ol>
|
||||
<li class="goal">
|
||||
<h3 class="name">Independent</h3>
|
||||
<p class="description">
|
||||
We will fork and maintain Nix, NixPkgs, and NixOS. Additional support
|
||||
for projects such as Nix Darwin and Home Manager will be considered.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Governance</h3>
|
||||
<p class="description">
|
||||
A democratic model of governance with elected positions will be used to
|
||||
manage the project. A steering committee will provide direction with
|
||||
additional committees handling specific logistical tasks. Features or
|
||||
individual projects will be owned by Special Interest Groups. SIGs will
|
||||
collaborate within Working Groups to achieve their goals. Each committee
|
||||
and group will have its goals, requirements, and management process
|
||||
clearly defined.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Stabilization</h3>
|
||||
<p class="description">
|
||||
User-friendly features such as the Nix v3 CLI will be enabled by
|
||||
default. Nix Flakes are used too heavily to remove or change and will
|
||||
instead be stabilized as a v0 in its current state with any future work
|
||||
being handled by a Special Interest Group.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Infrastructure</h3>
|
||||
<p class="description">
|
||||
We will build and maintain the tools and infrastructure necessary to
|
||||
keep the ecosystem healthy, including Continuous Integration and Binary
|
||||
Caching.
|
||||
</p>
|
||||
</li>
|
||||
<li class="goal">
|
||||
<h3 class="name">Education</h3>
|
||||
<p class="description">
|
||||
Unified documentation, tutorials, guides, and examples will provide a
|
||||
better onboarding experience for newcomers and a faster iteration cycle
|
||||
for experts.
|
||||
</p>
|
||||
</li>
|
||||
</ol>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<style>
|
||||
|
|
@ -57,6 +59,9 @@
|
|||
max-width: 800px;
|
||||
margin: 0 auto;
|
||||
padding: 4rem 1rem;
|
||||
}
|
||||
|
||||
.goals {
|
||||
padding-left: 2.5rem;
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,16 +10,15 @@ interface Props {}
|
|||
</a>
|
||||
</div>
|
||||
<div class="right">
|
||||
<!-- TODO: Enable these once the pages are ready. -->
|
||||
<!--
|
||||
<nav>
|
||||
<ul>
|
||||
<!--
|
||||
<li><a href="https://aux.computer/documentation">Documentation</a></li>
|
||||
<li><a href="https://aux.computer/contribute">Contribute</a></li>
|
||||
<li><a href="https://aux.computer/community">Community</a></li>
|
||||
-->
|
||||
<li><a href="https://forum.aux.computer">Community</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
-->
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,101 +4,103 @@
|
|||
|
||||
<section id="roadmap">
|
||||
<h2 class="title">Roadmap</h2>
|
||||
<ol>
|
||||
<li class="phase">
|
||||
<h3 class="name">Soft Fork</h3>
|
||||
<p class="description">
|
||||
This initial phase will involve an ad-hoc management structure due to
|
||||
its bootstrapping nature. As such, the project's stated Values, Goals,
|
||||
and Roadmap serve to keep all contributors aligned and safe knowing that
|
||||
the work they have committed to will not change.
|
||||
</p>
|
||||
<p class="description">
|
||||
The initial forking off of Nix and NixPkgs will be performed in this
|
||||
phase and new contributors will be given roles for handling package
|
||||
maintenance and pulling changes from upstream. We intend to move on from
|
||||
this phase once enough contributors have joined for the project to be
|
||||
capable of transitioning into a hard fork.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Hard Fork</h3>
|
||||
<p class="description">
|
||||
Like the Soft Fork phase, management structure will still be ad-hoc, but
|
||||
Committees, Special Interest Groups, and Working Groups may start to be
|
||||
formed. Due to there being necessary bootstrapping steps for each,
|
||||
elections will only begin once the Alignment phase has been reached.
|
||||
</p>
|
||||
<p class="description">
|
||||
At this point we will have enough contributors to safely maintain
|
||||
NixPkgs (or a reasonable subset) and Nix ourselves. We will begin
|
||||
allowing divergence from the upstream repository and changes to the
|
||||
repository structure to improve development can be introduced.
|
||||
</p>
|
||||
<p class="description">
|
||||
An initial release of the packages repository will be created and
|
||||
migration from `nix` to `aux` naming will begin to reduce confusion and
|
||||
errors now that the two projects have diverged.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Organization</h3>
|
||||
<p class="description">
|
||||
The packages repository will have sets extracted to allow for Special
|
||||
Interest Groups to more easily manage their lifecycles. For example,
|
||||
`pythonPackages` will be moved to a separate repository that will be the
|
||||
reponsibility of a Python SIG if there is interest.
|
||||
</p>
|
||||
<p class="description">
|
||||
Flakes will be standardized with its current implementation as a v0.
|
||||
While not ideal, the feature is used far too widely to be changed or
|
||||
removed without breaking the ecosystem. Instead, this v0 implementation
|
||||
will be enabled and future work for Flakes that addresses its
|
||||
shortcomings may be handled by a Flakes SIG.
|
||||
</p>
|
||||
<p class="description">
|
||||
The `aux` CLI will be modified to provide more ergonomic management of
|
||||
packages and systems. Additional subcommands such as `aux system switch`
|
||||
and `aux system build` will be added to make onboarding and ongoing
|
||||
maintenance easier.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Infrastructure</h3>
|
||||
<p class="description">
|
||||
Now that the project has significantly diverged from upstream, we will
|
||||
need to provide our own Continuous Integration and Binary Cache
|
||||
services. Existing governance structures will be used to manage the
|
||||
adoption of these technologies.
|
||||
</p>
|
||||
<p class="description">
|
||||
Documentation will be included as a part of the Continuous Integration
|
||||
process and will have Continuous Deployment configured to keep it up to
|
||||
date, making it easier for contributors to create educational materials.
|
||||
</p>
|
||||
<p class="description">
|
||||
Search infrastructure for packages and options will also be created.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Alignment</h3>
|
||||
<p class="description">
|
||||
By this point, we've done it. We have created a sustainable, independent
|
||||
fork of the Nix ecosystem. Now that the initial work has been completed
|
||||
we will begin the governance rotation process with our first elections
|
||||
and education as to how project governance works.
|
||||
</p>
|
||||
<p class="description">
|
||||
Documentation, project branding, and packages will be polished and
|
||||
presented as a fully stable release. From this point forward the
|
||||
Steering Committee will be managing the creation of Special Interest
|
||||
Groups and other necessary Committees. All enhancements will be
|
||||
suggested in Aux Enhancement Proposals which encourage existing SIGs to
|
||||
implement features or encourage the formation of a new SIG to be created
|
||||
for such a purpose.
|
||||
</p>
|
||||
</li>
|
||||
</ol>
|
||||
<div class="phases">
|
||||
<ol>
|
||||
<li class="phase">
|
||||
<h3 class="name">Soft Fork</h3>
|
||||
<p class="description">
|
||||
This initial phase will involve an ad-hoc management structure due to
|
||||
its bootstrapping nature. As such, the project's stated Values, Goals,
|
||||
and Roadmap serve to keep all contributors aligned and safe knowing that
|
||||
the work they have committed to will not change.
|
||||
</p>
|
||||
<p class="description">
|
||||
The initial forking off of Nix and NixPkgs will be performed in this
|
||||
phase and new contributors will be given roles for handling package
|
||||
maintenance and pulling changes from upstream. We intend to move on from
|
||||
this phase once enough contributors have joined for the project to be
|
||||
capable of transitioning into a hard fork.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Hard Fork</h3>
|
||||
<p class="description">
|
||||
Like the Soft Fork phase, management structure will still be ad-hoc, but
|
||||
Committees, Special Interest Groups, and Working Groups may start to be
|
||||
formed. Due to there being necessary bootstrapping steps for each,
|
||||
elections will only begin once the Alignment phase has been reached.
|
||||
</p>
|
||||
<p class="description">
|
||||
At this point we will have enough contributors to safely maintain
|
||||
NixPkgs (or a reasonable subset) and Nix ourselves. We will begin
|
||||
allowing divergence from the upstream repository and changes to the
|
||||
repository structure to improve development can be introduced.
|
||||
</p>
|
||||
<p class="description">
|
||||
An initial release of the packages repository will be created and
|
||||
migration from `nix` to `aux` naming will begin to reduce confusion and
|
||||
errors now that the two projects have diverged.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Organization</h3>
|
||||
<p class="description">
|
||||
The packages repository will have sets extracted to allow for Special
|
||||
Interest Groups to more easily manage their lifecycles. For example,
|
||||
`pythonPackages` will be moved to a separate repository that will be the
|
||||
reponsibility of a Python SIG if there is interest.
|
||||
</p>
|
||||
<p class="description">
|
||||
Flakes will be standardized with its current implementation as a v0.
|
||||
While not ideal, the feature is used far too widely to be changed or
|
||||
removed without breaking the ecosystem. Instead, this v0 implementation
|
||||
will be enabled and future work for Flakes that addresses its
|
||||
shortcomings may be handled by a Flakes SIG.
|
||||
</p>
|
||||
<p class="description">
|
||||
The `aux` CLI will be modified to provide more ergonomic management of
|
||||
packages and systems. Additional subcommands such as `aux system switch`
|
||||
and `aux system build` will be added to make onboarding and ongoing
|
||||
maintenance easier.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Infrastructure</h3>
|
||||
<p class="description">
|
||||
Now that the project has significantly diverged from upstream, we will
|
||||
need to provide our own Continuous Integration and Binary Cache
|
||||
services. Existing governance structures will be used to manage the
|
||||
adoption of these technologies.
|
||||
</p>
|
||||
<p class="description">
|
||||
Documentation will be included as a part of the Continuous Integration
|
||||
process and will have Continuous Deployment configured to keep it up to
|
||||
date, making it easier for contributors to create educational materials.
|
||||
</p>
|
||||
<p class="description">
|
||||
Search infrastructure for packages and options will also be created.
|
||||
</p>
|
||||
</li>
|
||||
<li class="phase">
|
||||
<h3 class="name">Alignment</h3>
|
||||
<p class="description">
|
||||
By this point, we've done it. We have created a sustainable, independent
|
||||
fork of the Nix ecosystem. Now that the initial work has been completed
|
||||
we will begin the governance rotation process with our first elections
|
||||
and education as to how project governance works.
|
||||
</p>
|
||||
<p class="description">
|
||||
Documentation, project branding, and packages will be polished and
|
||||
presented as a fully stable release. From this point forward the
|
||||
Steering Committee will be managing the creation of Special Interest
|
||||
Groups and other necessary Committees. All enhancements will be
|
||||
suggested in Aux Enhancement Proposals which encourage existing SIGs to
|
||||
implement features or encourage the formation of a new SIG to be created
|
||||
for such a purpose.
|
||||
</p>
|
||||
</li>
|
||||
</ol>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<style>
|
||||
|
|
@ -106,6 +108,9 @@
|
|||
max-width: 800px;
|
||||
margin: 0 auto;
|
||||
padding: 4rem 1rem;
|
||||
}
|
||||
|
||||
.phases {
|
||||
padding-left: 2.5rem;
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,7 @@ const { title } = Astro.props;
|
|||
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
|
||||
<meta name="generator" content={Astro.generator} />
|
||||
<title>{title}</title>
|
||||
<meta name="verify" content="https://github.com/jakehamilton" />
|
||||
</head>
|
||||
<body>
|
||||
<slot />
|
||||
|
|
|
|||
Loading…
Reference in a new issue