https://software.opensuse.org/ is aging. Richard made a proposal using Jekyll to statically generate a new layout: https://software.opensuse.org/newsite/, code at https://github.com/sysrich/new-software.o.o

MALLOC_CHECK_ and MALLOC_PERTURB_ variables are environmental variables which help identify problems with Glibc's malloc() allocations. I intend to set them "globally" for every process via /etc/environment file and see, if test suites behave in usual way, identify problems.

Mojolicious is a web development toolkit and framework built around an event loop. That has many performance and scalability advantages, but can also make debugging slow code a bit of a challenge. Especially in big projects like openQA, where Devel::NYTProf can be a bit tricky to use, it would be nice to have more built-in diagnostics tools at the event reactor level. Mojo::UserAgent already has very good diagnostics features with MOJO_USERAGENT_DEBUG, and we should be able to do something similar for Mojo::IOLoop.

For far too long openQA instances are crippled by insufficient I/O throughput when under heavy load. This results in incomplete and aborted tests prolonging new snapshots testing and also adding confusion into the release process. OpenQA itself doesn't require any exact technology for its remote workers, but so far we relied on NFS. This was fine for few workers, now with 50+ of them this stopped to be a viable route however. There are some custom made mitigations like rsyncing tests, assets and needles before the actual test job run, but this feels like reinventing the wheel to me.

Fedora 25 has enabled Wayland by default for GNOME. Tumbleweed ships with Wayland too, but how far can we go in removing X11 components and get a X11 server free system, while keeping X11 applications support.