Workflow preferences - case aarch64 support

[Ville Ilvonen <ville.ilvonen@unikie.com>]

Hi all,

Good news is that the work on aarch64 support has progressed to the point where
the Spectrum host can be built natively and run on aarch64 HW.

It's still a bunch of patches in various stages of WIP or review to
spectrum or further
up the stream.

In short, to "nixpkgs-spectrum":
0001-Allow-static-building-of-dtc.patch
0002-Workaround-ld-script-segmentation-fault.patch /* may be not needed */
0003-Add-imx8-specific-kernel.patch
and to "spectrum":
0001-Add-imx8-kernel.patch

Should anyone want to reproduce, please let me know and I'll try to
find a solution
to share them. Probably worth waiting for cross-compilation support unless you
have powerful aarch64 at your disposal.

In the meanwhile, we try to establish a mechanism to collaborate in branches of
required upstream repos. It's fairly impractical to fork
"nixpkgs-spectrum"-repo due to
its' size, over 2GB,

Which takes me to the discussion point - what's the workflow proposal
on multiple people
working on the same functionality in the same branch? If I'm not
mistaken the email workflow
creates a new branch for each author? Then someone would have to
cherry-pick them to the
same branch to integrate them in dev time hydra builds.

Best,

-Ville