The Problem: many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one

How many times have you created quick and dirty script to generate C tables, parameterized code, etc. ?

Implement file system image build using the Builder infrastructure. The project will create additional builders for the ext filesystems laying the ground work for restructuring other filesystem builders.

For development purpose, it is very useful to have an infrastructure that can spot regressions based on commit base. Currently, our existing infrastructure runs mainly SPEC benchmark and is cumbersome from perspective of any further development. I would like to build a replacement that will combine buildbot framework with a custom web project (based on Django framework). The web project will be used both for submitting reports coming from a buildbot slave and for UI which will serve plots and data.

Taskotop is a tool to check what taskomatic is currently doing on a SUSE Manager server: it's a command line python tool. The core of the tool is to get some info about jobs that taskomatic is running with a fixed time cycle running some queries and showing results to the shell.

Build a paper folding machine capable of folding Skill Shot.

Implement a basic file search for a given OBS project. An example of basic functionality can already be found for Ubuntu or Debian. The goal is to implement,

After an internal call for help to take over software.opensuse.org deployment, I spend some time studying the code in order to find out what would it mean to take it over.

Idea is to have SUSE system with OpenZFS as root FS.