For some time I've wanted to improve our git based patch workflow for qemu to be more friendly toward "generic joe" contributing fixes, and for handling patching the code in git submodules just as easily as we handle patching for the main qemu code. Once again, I'll try to make some progress here. This time, hopefully it will stick.

This project aims to be able to compile & execute wicked from vscode by generating the RPM files and installing them onto a dynamically created container with systemd support, ultimately allowing to debug from the editor in a matter of seconds. Current situation

In my daily life I work with software that ship PAM modules (samba, sssd) but I haven't looked at PAM internals yet. The goal of this project is to improve knowledge about PAM internals.

Automation is great, but meta-automation is the way to go further, with POWER.

Since RGW already supports beast as the default frontend from nautilus onwards, evaluate the usage of beast as a http client as well. Main implementation would be the need for connection pooling and a higher level http api

I will be testing the software we use in QAM called mtui, using the rapid software testing methodology. This means, we will use efficient ways to test the software, learn the software and file bugs in the given time we have.

I use vim (yes one of those people) but I am a real non power user, I'd like something like Aurelien's smbmode for Emacs to be available when I open samba log files in vim. I have no idea how possible or not this is. I came across this tutorial/book some time ago but didn't find the time to look at it. I'd like to go through the book and hopefully have a crack at starting a samba log reader plugin for vim (duplicating the features from smbmode)