auxolotl/website
24
0
Fork 1
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

feat: update goals, roadmap, and add forum link

Browse source
This commit is contained in:
Jake Hamilton 2024-04-30 13:26:19 -07:00
parent d697f2daf3
commit 134cc83632
Signed by: jakehamilton
GPG key ID: 9762169A1B35EA68
4 changed files with 155 additions and 145 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

97
src/components/Goals.astro
View file

@ -4,52 +4,54 @@
<section id="goals"> <section id="goals">
<h2 class="title">Goals</h2> <h2 class="title">Goals</h2>
<ol> <div class="goals">
<li class="goal"> <ol>
<h3 class="name">Independent</h3> <li class="goal">
<p class="description"> <h3 class="name">Independent</h3>
We will fork and maintain Nix, NixPkgs, and NixOS. Additional support <p class="description">
for projects such as Nix Darwin and Home Manager will be considered. We will fork and maintain Nix, NixPkgs, and NixOS. Additional support
</p> for projects such as Nix Darwin and Home Manager will be considered.
</li> </p>
<li class="goal"> </li>
<h3 class="name">Governance</h3> <li class="goal">
<p class="description"> <h3 class="name">Governance</h3>
A democratic model of governance with elected positions will be used to <p class="description">
manage the project. A steering committee will provide direction with A democratic model of governance with elected positions will be used to
additional committees handling specific logistical tasks. Features or manage the project. A steering committee will provide direction with
individual projects will be owned by Special Interest Groups. SIGs will additional committees handling specific logistical tasks. Features or
collaborate within Working Groups to achieve their goals. Each committee individual projects will be owned by Special Interest Groups. SIGs will
and group will have its goals, requirements, and management process collaborate within Working Groups to achieve their goals. Each committee
clearly defined. and group will have its goals, requirements, and management process
</p> clearly defined.
</li> </p>
<li class="goal"> </li>
<h3 class="name">Stabilization</h3> <li class="goal">
<p class="description"> <h3 class="name">Stabilization</h3>
User-friendly features such as the Nix v3 CLI will be enabled by <p class="description">
default. Nix Flakes are used too heavily to remove or change and will User-friendly features such as the Nix v3 CLI will be enabled by
instead be stabilized as a v0 in its current state with any future work default. Nix Flakes are used too heavily to remove or change and will
being handled by a Special Interest Group. instead be stabilized as a v0 in its current state with any future work
</p> being handled by a Special Interest Group.
</li> </p>
<li class="goal"> </li>
<h3 class="name">Infrastructure</h3> <li class="goal">
<p class="description"> <h3 class="name">Infrastructure</h3>
We will build and maintain the tools and infrastructure necessary to <p class="description">
keep the ecosystem healthy, including Continuous Integration and Binary We will build and maintain the tools and infrastructure necessary to
Caching. keep the ecosystem healthy, including Continuous Integration and Binary
</p> Caching.
</li> </p>
<li class="goal"> </li>
<h3 class="name">Education</h3> <li class="goal">
<p class="description"> <h3 class="name">Education</h3>
Unified documentation, tutorials, guides, and examples will provide a <p class="description">
better onboarding experience for newcomers and a faster iteration cycle Unified documentation, tutorials, guides, and examples will provide a
for experts. better onboarding experience for newcomers and a faster iteration cycle
</p> for experts.
</li> </p>
</ol> </li>
</ol>
</div>
</section> </section>
<style> <style>
@ -57,6 +59,9 @@
max-width: 800px; max-width: 800px;
margin: 0 auto; margin: 0 auto;
padding: 4rem 1rem; padding: 4rem 1rem;
}
.goals {
padding-left: 2.5rem; padding-left: 2.5rem;
} }

7
src/components/Header.astro
View file

@ -10,16 +10,15 @@ interface Props {}
</a> </a>
</div> </div>
<div class="right"> <div class="right">
<!-- TODO: Enable these once the pages are ready. -->
<!--
<nav> <nav>
<ul> <ul>
<!--
<li><a href="https://aux.computer/documentation">Documentation</a></li> <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/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> </ul>
</nav> </nav>
-->
</div> </div>
</header> </header>

195
src/components/Roadmap.astro
View file

@ -4,101 +4,103 @@
<section id="roadmap"> <section id="roadmap">
<h2 class="title">Roadmap</h2> <h2 class="title">Roadmap</h2>
<ol> <div class="phases">
<li class="phase"> <ol>
<h3 class="name">Soft Fork</h3> <li class="phase">
<p class="description"> <h3 class="name">Soft Fork</h3>
This initial phase will involve an ad-hoc management structure due to <p class="description">
its bootstrapping nature. As such, the project's stated Values, Goals, This initial phase will involve an ad-hoc management structure due to
and Roadmap serve to keep all contributors aligned and safe knowing that its bootstrapping nature. As such, the project's stated Values, Goals,
the work they have committed to will not change. and Roadmap serve to keep all contributors aligned and safe knowing that
</p> the work they have committed to will not change.
<p class="description"> </p>
The initial forking off of Nix and NixPkgs will be performed in this <p class="description">
phase and new contributors will be given roles for handling package The initial forking off of Nix and NixPkgs will be performed in this
maintenance and pulling changes from upstream. We intend to move on from phase and new contributors will be given roles for handling package
this phase once enough contributors have joined for the project to be maintenance and pulling changes from upstream. We intend to move on from
capable of transitioning into a hard fork. this phase once enough contributors have joined for the project to be
</p> capable of transitioning into a hard fork.
</li> </p>
<li class="phase"> </li>
<h3 class="name">Hard Fork</h3> <li class="phase">
<p class="description"> <h3 class="name">Hard Fork</h3>
Like the Soft Fork phase, management structure will still be ad-hoc, but <p class="description">
Committees, Special Interest Groups, and Working Groups may start to be Like the Soft Fork phase, management structure will still be ad-hoc, but
formed. Due to there being necessary bootstrapping steps for each, Committees, Special Interest Groups, and Working Groups may start to be
elections will only begin once the Alignment phase has been reached. formed. Due to there being necessary bootstrapping steps for each,
</p> elections will only begin once the Alignment phase has been reached.
<p class="description"> </p>
At this point we will have enough contributors to safely maintain <p class="description">
NixPkgs (or a reasonable subset) and Nix ourselves. We will begin At this point we will have enough contributors to safely maintain
allowing divergence from the upstream repository and changes to the NixPkgs (or a reasonable subset) and Nix ourselves. We will begin
repository structure to improve development can be introduced. allowing divergence from the upstream repository and changes to the
</p> repository structure to improve development can be introduced.
<p class="description"> </p>
An initial release of the packages repository will be created and <p class="description">
migration from `nix` to `aux` naming will begin to reduce confusion and An initial release of the packages repository will be created and
errors now that the two projects have diverged. migration from `nix` to `aux` naming will begin to reduce confusion and
</p> errors now that the two projects have diverged.
</li> </p>
<li class="phase"> </li>
<h3 class="name">Organization</h3> <li class="phase">
<p class="description"> <h3 class="name">Organization</h3>
The packages repository will have sets extracted to allow for Special <p class="description">
Interest Groups to more easily manage their lifecycles. For example, The packages repository will have sets extracted to allow for Special
`pythonPackages` will be moved to a separate repository that will be the Interest Groups to more easily manage their lifecycles. For example,
reponsibility of a Python SIG if there is interest. `pythonPackages` will be moved to a separate repository that will be the
</p> reponsibility of a Python SIG if there is interest.
<p class="description"> </p>
Flakes will be standardized with its current implementation as a v0. <p class="description">
While not ideal, the feature is used far too widely to be changed or Flakes will be standardized with its current implementation as a v0.
removed without breaking the ecosystem. Instead, this v0 implementation While not ideal, the feature is used far too widely to be changed or
will be enabled and future work for Flakes that addresses its removed without breaking the ecosystem. Instead, this v0 implementation
shortcomings may be handled by a Flakes SIG. will be enabled and future work for Flakes that addresses its
</p> shortcomings may be handled by a Flakes SIG.
<p class="description"> </p>
The `aux` CLI will be modified to provide more ergonomic management of <p class="description">
packages and systems. Additional subcommands such as `aux system switch` The `aux` CLI will be modified to provide more ergonomic management of
and `aux system build` will be added to make onboarding and ongoing packages and systems. Additional subcommands such as `aux system switch`
maintenance easier. and `aux system build` will be added to make onboarding and ongoing
</p> maintenance easier.
</li> </p>
<li class="phase"> </li>
<h3 class="name">Infrastructure</h3> <li class="phase">
<p class="description"> <h3 class="name">Infrastructure</h3>
Now that the project has significantly diverged from upstream, we will <p class="description">
need to provide our own Continuous Integration and Binary Cache Now that the project has significantly diverged from upstream, we will
services. Existing governance structures will be used to manage the need to provide our own Continuous Integration and Binary Cache
adoption of these technologies. services. Existing governance structures will be used to manage the
</p> adoption of these technologies.
<p class="description"> </p>
Documentation will be included as a part of the Continuous Integration <p class="description">
process and will have Continuous Deployment configured to keep it up to Documentation will be included as a part of the Continuous Integration
date, making it easier for contributors to create educational materials. process and will have Continuous Deployment configured to keep it up to
</p> date, making it easier for contributors to create educational materials.
<p class="description"> </p>
Search infrastructure for packages and options will also be created. <p class="description">
</p> Search infrastructure for packages and options will also be created.
</li> </p>
<li class="phase"> </li>
<h3 class="name">Alignment</h3> <li class="phase">
<p class="description"> <h3 class="name">Alignment</h3>
By this point, we've done it. We have created a sustainable, independent <p class="description">
fork of the Nix ecosystem. Now that the initial work has been completed By this point, we've done it. We have created a sustainable, independent
we will begin the governance rotation process with our first elections fork of the Nix ecosystem. Now that the initial work has been completed
and education as to how project governance works. we will begin the governance rotation process with our first elections
</p> and education as to how project governance works.
<p class="description"> </p>
Documentation, project branding, and packages will be polished and <p class="description">
presented as a fully stable release. From this point forward the Documentation, project branding, and packages will be polished and
Steering Committee will be managing the creation of Special Interest presented as a fully stable release. From this point forward the
Groups and other necessary Committees. All enhancements will be Steering Committee will be managing the creation of Special Interest
suggested in Aux Enhancement Proposals which encourage existing SIGs to Groups and other necessary Committees. All enhancements will be
implement features or encourage the formation of a new SIG to be created suggested in Aux Enhancement Proposals which encourage existing SIGs to
for such a purpose. implement features or encourage the formation of a new SIG to be created
</p> for such a purpose.
</li> </p>
</ol> </li>
</ol>
</div>
</section> </section>
<style> <style>
@ -106,6 +108,9 @@
max-width: 800px; max-width: 800px;
margin: 0 auto; margin: 0 auto;
padding: 4rem 1rem; padding: 4rem 1rem;
}
.phases {
padding-left: 2.5rem; padding-left: 2.5rem;
} }

1
src/layouts/Layout.astro
View file

@ -15,6 +15,7 @@ const { title } = Astro.props;
<link rel="icon" type="image/svg+xml" href="/favicon.svg" /> <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<meta name="generator" content={Astro.generator} /> <meta name="generator" content={Astro.generator} />
<title>{title}</title> <title>{title}</title>
<meta name="verify" content="https://github.com/jakehamilton" />
</head> </head>
<body> <body>
<slot /> <slot />