As the automation became a standard within Maintenance QA work, I would like to became more familiar with the whole magic behind. Plan is to go through internal docu a try to setup openQA and write some simple tests (and adjust the docu once there are any gaps):

This is my attempt to catch up on the field of machine learning. In order to not "waste" time of exercising with dummy data the Security team came up with a couple of interesting questions:

The goal of this project is to create video tutorial describing configuration of SUSE Manager for Retail.

The day has come to finally merge more and more apps into one single place, and this time it shall be externaltools.

My music manager, Bard, was improved in the last hackweek with a very simple React-based web interface but I didn't like the result at all (basically, after learning React I noticed I didn't like it and all the dependencies and the complexity it added) so since then, I've reimplemented the web interface using just jQuery. Also, in the last months I've added musicbrainz data structures to the database (which was also ported to use Postgresql) to prepare bard to use MusicBrainz's data. I also stopped using other python libraries to read audio files and use the ffmpeg libraries directly instead with a c++ wrapper implemented inside Bard which is much much faster.

Since quite a while I'm interested in learning the programming language golang. I want to use the time to get a basic understanding and maybe realize a small project with the gained knowledge.

Learn Go language by through The Go Programming Language book.

People are interested in Linux on Windows via WSL, especially given the new fully virtualized Linux kernel in WSL 2. It's interesting to know whether registered SUSE installations might be running in WSL as opposed to other Microsoft virtualization platforms, but the current approach taken by SUSEConnect (the client for SUSE Customer Center) does not permit this.

My goal is build on Alberto's work on "yomi" and the new Salt-based virtualization management features that Cedric has contributed, then combine them with a Redfish prototype to do the following from one (ideally idempotent) Salt state (orchestration state if required):

https://github.com/dmulder/phylogen

This is a task to update current WSL-Launcher (which can be already buildt in OBS) with latest-greatest upstream code https://github.com/Microsoft/WSL-DistroLauncher

The plan is to implement a safe path resolution library for Linux to avoid the plentiful numbers of security vulnerabilities that have been seen in the wild related to path resolution race conditions and various other attacks. I've been working on kernel-space solutions but even if they were merged, it is difficult to use them safely directly. So this library intends to provide simple wrappers that everyone can use.

Currently it's pretty difficult to create tests for some specific package. So something like TravisCI for OBS would be good.