Currently we use openQA for the the YaST integration tests. It runs YaST in a VM and controls it via emulating keyboard input. The result is checked by comparing the screenshots. This approach has several disadvantages:

Using docker as a development platform for nontrivial development environments sounds interesting. This project is about learning basic docker handling, about exploring how to use it for simplifying development, and maybe (but just maybe) about providing ready-made docker containers for new team members.

there is a small security, data manipulation bug on the hackweek-tool. You can try to find it, i will then post it at the end of the hackweek

gitbot

https://github.com/MalloZup/gitbot

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

The purpose would be to have the equivalent of Ubuntu's "apt-get autoremove" functionality. When you install package P, it might draw in dependancies D1, D2, ... Dn automatically.

The goal is to reduce the number of applications installed on the mobile phone (which consequently reduces the number of ads and spyware) and transfer some of the functionality of the commonly installed apps to a personal Telegram Bot. Bots are a great way of implementing integration with external services, and, to this end, we expect the following functionality: