QA engineers often tests same/similar parts of software, and if they find a bug, the information they need to collect can be predicted. For example, for apache2 problems, following are needed:

Scanning books stopped 6 years ago. We need volunteers to take the scanner and walk through the offices. This is a good learning opportunity for trainees. The software could also be updated. If anybody looks for a replacement with a more mature opensource solution, Lars suggests KOHA which he already packaged in obs.

A project idea I've been carrying around for several years now. Based upon the 'referrals' concept from SPC-4 it should be rather easy to build up large volumes spread over several nodes. I'm thinking of an iSCSI target here, which gets updated via a corosync engine with any volume updates from the cluster.

The File Server Remote VSS Protocol (FSRVP) was recently defined by Microsoft. It allows for SMB clients to remotely request the creation, exposure and destruction of share snapshots. Aside from support in Windows Server 2012, preliminary FSRVP server support has also been implemented for Samba.

Elasto is a cloud library and client utility for managing and manipulating cloud storage objects via REST. Functionality was recently added to istgt so that it can expose an Azure storage blob for access via iSCSI, it does so using Elasto's file API.

Create a kernel module, which provides a virtual alsa sink, which transmits the audio through the air. see https://github.com/bmwiedemann/PiBits/tree/master/PiFmDma (code uses less cpu power)

Wayland would replace X11 in the future (maybe soon?), we're researching/learning Wayland. And I planed to try a tiny Window Manager of Wayland for a practice. It's meaningful I think, since there's little independent WM for Wayland, except for Mutter which is a part of Gnome desktop environment.

Tempest is a functional test suite used for OpenStack. It would normally run in the order of 800 tests over the period of 2 hours on a newly installed OpenStack infrastructure. Tempest is written in Python and uses nosetests as the basis of its test framework. There is a large amount of verbose that is streamed to the log file and there is also considerable ambiguity in the overall success rate.

html5 gives a new way of exchanging and expressing ideas and telling stories. simple, slide-like examples:

For the Bavaria 2013 elections I had created an interactive political landscape visualizing the party stances according to the Wahl-O-Mat with d3.js. I have tons of ideas to improve this:

one of the top features a distribution must always ship in a working state is wireless. Yet we have no way to test it in an automated way. To be able to do that via openQA we need qemu to emulate a wireless adapter. Whether it's emulating existing hardware or implements some virtio device that only works on Linux doesn't matter.

Step 1. Control Robotis servo from raspberry pi<br> Step 2. Setup OpenCV on for raspberry pi / camera<br>

The idea is to execute user defined scripts before and after creation of snapshots with snapper. The feature request covering this (fate #316315) was rejected. But I would like to use it anyway for fate #316232.