motivation

The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu. Something like a notification with a button to perform the upgrade with just one-click, instead of having to deal with the terminal, that frights some new users and gives them the sensation of an outdated system.

Last time I checked QEMU lacked support for >= z10 processors. Thus one cannot run SLE12 and newer in a virtual machine on non-s390x host. I'd like to improve the situation during Hackweeks.

To make OpenQA work with real ARM devices, we need to control * Reset

As DBus a main component in Linux user space, in this hackweek I plan to learn more about it. Tentative Plan: a node js binding for sd-bus interface offered by systemd (available in SLE12)

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table Many YaST developers will be at openSUSE Conference, that overlaps with Hackweek. The plan is to lock them all in a room with a blackboard and reach agreements on how the code should be organized in the future. Then use Hackweek to iron the details, document everything in some kind of style guide and, if time permits, even do some experiments about how to adapt the existing code to the new conventions.

This project aims for enabling FCoE over virtio-net. With that we should be able to run FCoE within a KVM guest, and finally have a 'real' FC host in a KVM guest. This should enable 'real' FC testing, like link failure, multipath operations etc.

Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means: * Adding some lines to the corresponding config file