The current Jangouts UI is limiting us when thinking about adding new features. Some examples: * This (using the whole thumbnail to pin a participant) was implemented, but the result is far from optimal (I have not even deployed it in production).

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. So this project aims at:

Clair is a static vulnerability analyzer for containers. Currently it supports containers based on Debian, Ubuntu and RedHat. I already started this project on the CSM workshop, now I want to finish the integration for openSUSE and SLES based container images. You can track the changes at https://github.com/coreos/clair/pull/199.

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). Also, it could be interesting to generate flatpak bundle directly from OBS, if possible, using either available packages or directly application sourcecode.

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. And it looks like I haven't failed 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. However running java applets in browser is getting harder every day. Especially when the applet isn't signed by a trusted authority.

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. Instead of just uploading some prepared hard disk image, openQA should ideally install Windows itself and save the generated image. In a second run openQA can then install the latest Leap or TW on that disk image.

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

• 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.