Starting with CUPS 1.6 things have changed considerably. Clients are no longer discovering broadcasted printers anymore. Distributions (e.g. Debian) has backported the original protocol into cups-daemon package but this doesn't seem to work either on my laptop. I would like to look and try to understand what the hack is going on here. The outcome should be my understanding of the change and how to configure CUPs to behave reasonably again.

We had a quick course of Coccinelle during the last Labs conference. The tool is really great and I would like to explore possibility of checking lock invariants for particular functions. Julia was really prompt and implemented something that should help but I didn't get to it since the conference.

If you want to use the full potential of SSDs as primary (and possibly only) storage on SLE or openSUSE systems, you are supposed to perform several configuration settings to make it fly, including: - changing the io scheduler of the device to noop or deadline

The idea is to produce a standalone, independent tool to save and restore windows positions and sizes, analogous to a similar feature in KDE desktop. This would be handy in various lightweight desktop enviroments.

The kdump package can now use SMP and multiple targets with constant memory requirements. The goal of this project is to find the optimum parameters for dumping a very large machine (SAP can give me access to 6TB, SGI is able to test with 64 TB).

There is quite a popular Android software for connection OBD standard adapters but not for older, brand specific ones. One for pre 2001 VAG cars is this one:

I'm sitting on old patches that implemented predicated value numbering in GCC by combining the algorithms from http://portal.acm.org/citation.cfm?id=512529.512536

Although I've been maintaining CRIU package, I had little time to play with it recently. It's still interesting especially in combination with various containers. So let's spend (or waste) some time.

I want to revive my "Cloud in a Box" project and this time focus on how OpenStack's Heat automation framework can help with setting up a complete demo or QA environment consisting of several SUSE products (e.g. a SLEPOS Admin/Branch/Client environment). Looking for contributors who want to hack OpenStack (especially work on a Horizon UI plugin for managing Heat-based "SUSE blueprints").

provide a summary report of data from a sar data file. Report should be broken down into subsystems - cpu, memory, disk, and network, and provide individual summaries for each device (cpu, disk, nic).