This would be a multiple step solution, a first idea that I would explore would be:

Currently, each filesystem developer does his fstests runs (a testsuite for regression-testing of filesystems) on his dedicated test machine, on Orthos machine, ... This not only means duplication of efforts to automate this testing but also leads to inefficient use of resources (sometimes the test machine is just idle, sometimes you would need more tests to run in parallel to speed up development). The goal of this effort is to use SUSE Engineering Cloud to implement fire-and-forget fstests runs where you specify kernel to test (fetched from git tree or so), fstests configs to run, and then just pick up test results later on...

The aim of this project is to finish up the work already done in previous editions of Hackweek in regards to zypper-docker. That being:

Two trainees embarking on their coding adventure!

I would like to work mainly on https://fate.suse.com/323638, think of default configuration and perhaps create a small configuration script for conky.

This will greatly enhance the usefulness of QEMU virtual serial ports, because the Linux kernel interprets a break on the serial console as a SysRq, but there is currently no way to pass this signal over a pseudo-terminal.

While in the past MIPS boards were either low-end PIC32 or found in routers running OpenWRT at most, Imagination themselves have recently released the Creator CI20 board (Ingenic, MIPS32) running Debian. And the Shield Pro (previously iGuardian) kickstarter project (Octeon-III, MIPS64) promises to become a playground for testing KVM hardware virtualization.