Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING!
Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.
My home server, and my other box hosting https://sysrich.co.uk are both in need of a bit of a refresh
While I could be nice and conservative and pick an openSUSE regular release, I'm actually considering using openSUSE Tumbleweed, and fully embracing the 'Servers as Cattle' concept
Right now internal SLE development is still organised & structured around the concept of 'Milestones'. Schedules are defined, deadlines are set, and off we go making Alpha 1, 2, 3, Betas 1, 2, 3, RC's, and so on.
Meanwhile, QA has evolved, and with openQA and other automated tooling we are increasingly testing SLE in a more agile, rolling model, testing every single build as soon as it's produced by OBS, and just paying extra attention to the Milestones with additional manual testing.
openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal.
But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?
The Kubic Project currently produces a "CaaSP-like" Tumbleweed OS, focused on Kubernetes clusters
However many of the attributes of Kubic (read-only filesystem, transactional updates, containerised services) could be an interesting platform for another use A Chromebook-like Linux Desktop
While I despise Trello, I quite like the idea of using a Kanban board to organise my individual work and much of my personal projects
So if I have time during Hackweek I plan on looking at https://wekan.github.io/ also
I currently have a lot of personal infrastructure that is in need of some tender loving care and transactionalisation
https://rootco.de is running on a Leap 42.3 Hetzner box. I'd like to replace this with something transactional (either Kubic, Leap 15 or Tumbleweed transactional server)
openSUSE now has a lot of black magic around building distributions for :Factory and :Leap
This includes all of the 000* packages and opensuse-release-tools doing very useful stuff like pkglistgen automatically managing the package lists for .kiwi files so release managers don't need to manually update which packages are going on which media