In reply to @fricklerhandwerk:matrix.org
One practical problem I've observed in the Nix maintainer team, where we have a very formalised meeting structure and in fact curate the board very nicely, is that the process nudges us to delegate tasks we don't actually have time to follow through with. So the tail end of the pipeline is broken due to limited capacity and the challenges to estimate workload. The front end works fairly well though, because we do triaging to determine whether something fits current priorities and direction, or make design decisions to help produce sustainable solutions. Some contributors follow up, many don't, due to lack of time to actually finish tasks that very often blow up in size once you take a close look at them.

We have the exact same problem in documentation, except we stopped assigning tasks as we were all fully booked at some point. And since contributions tend to be either very small or very large, triaging doesn't seem to serve much of a purpose. We should probably try to find some middle ground, to really get an up-to-date grasp on who's currently working on what, how complex a given task is (and which rabbit holes it uncovers), which resources are available to finish it, etc. -- simply to know what to focus the effort on to get it over the finish line.

In reply to @fricklerhandwerk:matrix.org
One practical problem I've observed in the Nix maintainer team, where we have a very formalised meeting structure and in fact curate the board very nicely, is that the process nudges us to delegate tasks we don't actually have time to follow through with. So the tail end of the pipeline is broken due to limited capacity and the challenges to estimate workload. The front end works fairly well though, because we do triaging to determine whether something fits current priorities and direction, or make design decisions to help produce sustainable solutions. Some contributors follow up, many don't, due to lack of time to actually finish tasks that very often blow up in size once you take a close look at them.

We have the exact same problem in documentation, except we stopped assigning tasks as we were all fully booked at some point. And since contributions tend to be either very small or very large, triaging doesn't seem to serve much of a purpose. We should probably try to find some middle ground, to really get an up-to-date grasp on who's currently working on what, how complex a given task is (and which rabbit holes it uncovers), which resources are available to finish it, etc. -- simply to know what to focus the effort on to get it over the finish line.

In reply to @fricklerhandwerk:matrix.org

It is meant to be used, but given the very limited amount of time we have, we usually prioritise group reviews to get things merged that have happened in between meetings.

We should probably have a formalised meeting agenda that gives the board a couple of minutes of attention.

In reply to @bzzm3r:matrix.org
Or...should I just re-write the nix-build CLI? 🤔

In reply to @jade_:matrix.org
you know you can nix build -f . someAttr on non flakes yeah?

does anyone know how to run the individual phases in the nix.dev repo?

i tried:

nix-shell default.nix -A build
$ buildPhase

but it doesn't work, and type buildPhase gives me the generic phase rather than the one defined in default.nix

In reply to @asymmetric:matrix.dapp.org.uk
fricklerhandwerk: can you help me understand the redirects file? so for example, here i see a redirect, but if i try to go to the redirected url, it 404s. the same doesn't happen with for exapmle this line, which redirects correctly

In reply to @fricklerhandwerk:matrix.org
The redirects in the Nix manual source have no effect yet. We merged that only recently and the PR to set them up on nix.dev doesn’t work yet because last time I touched it we didn’t have the right Nix builds in the binary cache

In reply to @fricklerhandwerk:matrix.org
So whatever you’re seeing happening on nixos.org is determined by the redirects there