Basically the idea is to boot inst-sys but to not run YaST and instead run a selfmade script that does the usual disaster recovery steps:

Twinkle, my favourite SIP client, seems no longer developed, has been accused of "bitrotting" and even dropped from some distributions. While I don't believe in bits actually rotting, there is one pressing issue: twinkle uses Qt3.

Get an overview about the unofficial Google Drive clients, which exist for Linux. Give them a broader testing. Figure out which one is usable.

Meet up NBG meeting room Paris with fellow Ruby on Rails hackers, throw an editor/shell onto the wall, grab a cup of coffee and refactor OSEM code together.

Get more familar with Greasemonkey User Scripting, in particular with using the IITC framework, which manipulates Ingress Intel map. The goal is to create a plugin, which highlights portals on the map, which have more fields than links attached. Ingress account is required for this (Android/iPhone).

There's a crmsh history guide in works for a very long time and it really really needs to be finished.

Use Jenkins as a Travis replacement for YaST

The idea is about virt-manager improvement. It calls libguestfs to provide 3 features for virt-manager:

OpenQA uses the VNC protocol to interface with a test system. This limits test systems to be virtualized. Bare metal (physical) systems do not provide VNC out-of-the-box.

While the python-based AppArmor utils (aa-logprof etc.) are much easier to understand and maintain than the old perl code, there are still some terribly long functions like parseprofiledata() in aa.py that are not too easy to understand. Also, using hasher() (a recursive array) as storage can have some strange side effects. Another problem is that test coverage isn't too good, especially for the bigger functions.