As DBus a main component in Linux user space, in this hackweek I plan to learn more about it.

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

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:

The current Jangouts UI is limiting us when thinking about adding new features. Some examples:

Our previous efforts to enable gdb to open kdumps was not received in upstream as well as we hoped for. The perhaps-acceptable way would be to extend gdb with the possibility of implementing targets in Python, then create example binding to libkdumpfile (which already got a Python binding). We've already tried that, yet it has to be tidyed up.

Clair is a static vulnerability analyzer for containers. Currently it supports containers based on Debian, Ubuntu and RedHat.

Flatpak (previously known as xdg-app) is a bundle system, based on ostree, to easily make available applications bundle to users. Currently, flatpack is available on openSUSE Tumbleweed but we don't ship any runtime based on openSUSE (freedesktop or GNOME runtime).

I've attempted this several times already and each attempt had different shortcomings. I'm kind of curious about how exactly will I fail this time.

Tigervnc comes with two very similar VNC viewers - one written in C++ and one in java. The java one can be embedded in a webpage as a java applet. We use that in our default VNC setup (the one enabled in YaST). That way if user doesn't have VNC viewer installed, browser is enough.

To make sure openSUSE can coexist nicely with an existing Windows installation, we need to have automated regression testing. UEFI and secure boot are especially interesting.That means installing Windows and openSUSE in parallel in openQA.

Automation tools are our emotional friends. Know each other deeper and improve it, it's a way to be harmonious for our friendship.

• Build zookeeper, mesos-master and mesos-slave on SLE12
• Setup a 3-nodes high-availability cluster (zookepper + mesos-master + mesos-slave run on each node)

L3 bug reproduction often requires becoming the admin for a moment. I'd like to write down some nifty tricks I used to get certain “interesting” system configurations to work.

In Beijing HA server room, we have a Huawei switch with a 10GB bandwith uplink FC port, a iSCSI HBA, a desktop computer, and some SFPs, I will build a 10GB bandwith iscsi server.

Implement a Little man computer in the Go programming language.

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA

I want to make ruby-lint usable.

Create a console application for a crossword puzzle generator that can be fed with a custom list of word+explanation pairs. It may be used by people to quickly familiarize with a specific topic (e.g. a knowledge area, new hires to the company ...) to at least understand the terminology and the abbreviations that are used. Or to just have some distraction and fun :-)

QA wants to set up a new QA Portal to get an new organized entry point for all Information that is QA related. The Hackweek Project is to start a discussion with the different QA groups, SLE QA, CSS QA and QAM to collect ideas and make a concrete plan.

There is a super cool framework for mobile phone apps available: ionic (http://ionicframework.com/)

Together with my son, I'm working on improving the Salt support in Manager 3.