Look at static code analysis and code coverage for a C++ project, in this case libstorage-bgl-eval. This could include:

<p>There are numerous testing tools for the GFX stack available - the oldes being the xtest suite. At the same time, we are still lacking automated test environments for the funktionalities of DRM, Mesa and X. Ideally the tests should be performed automatically and unattended and the results should be compared to previous runs to detect regressions.</p> <p>Research what tools exist to date and how they can be employed.</p>

This Hackweek I would like to finish enhancing of the mysql-packaging git repository [1]. This improvement mainly consists of scripts for a kind of simple continuous integration and git hooks to enforce a few policies for our project. If there is a time I will also take a look at the mysql package itself and check if there is anything to improve. [1] https://github.com/openSUSE/mysql-packaging

Tahoe-LAFS is an open-source decentralized cloud storage system. It distributes your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security. It provides a provider-independent security where the storage provider does not have access to the unencrypted data because all data is encrypted, erasure-coded, and hashed before leaving the client's machine thus preserving confidentiality, availability, and integrity of the data.

Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often". Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.

While in general everything still works, the current (patached/extended) planet installation behind planet.opensuse.org is a bit outdated and not maintained any more. The initial plan is to:

Given that Leap is now available, as installation media, we are going to dedicate some time to release ready to use 'Just enough Operating

SCC doesn't require an email address, so could you automatically generate random keys until one matches and effectively 'steal' SCC licenses from customers?

Porting training labs to Python. This includes re-implementing the host side BASH scripts (which handle VirtualBox and KVM related tasks) to Python. For full details on this please follow training-labs project: git://git.openstack.org/openstack/training-labs.git

Let's do this :) !!! https://build.opensuse.org/project/show/systemsmanagement:crowbar:master

By analysing a VNC session, we can create a draft of an openQA testcase (detecting keystroke, mouse click and generating fullscreen needles). The project is to :

As a counter-program to the daily usage of dynamic languages, I want to use this Hackweek to explore the web stack provided by very good static typed languages: - Haskell (e.g. Servant)

A normal Xen server today has many single points of failure. Those can be reduced by disaggregating Dom0 into multiple domains (xenstore, driver domains, admin domain). Following this path to it's logical end will lead to a setup where the running domUs won't be depending on Dom0 any more, so Dom0 itself can be made restartable. This project aims at beginning with a prototype by setting up a configuration with a xenstore domain and a driver domain for networking. This will allow running a pv-domU with network resources only (nfs or iscsi root file system) no longer needing Dom0 to run.

gdb-kdump (and libkdumpfile) needs a plenty of improvements and tasks to be done. For HackWeek 13, Vlastimil chose to work on SLAB memory support, Petr, amongst other things, reorganized the libkdumpfile code and alnovak begun with libkdumpfile's ppc64 support. Our status in 4/5 of HackWeek 13:

SLAB

Linux Certification Preparation Preparation for different Linux Certification:

using perl's Inline::Python module, it should be possible to define openQA test modules in python instead of perl.

Openstack Congress provides Policy as a service solution for Openstack based clouds. Policy based fulfillment makes it convenient to write policies for VM migrations and evacuations based on data monitored from various data sources. The aim of the project is to integrate the service to SUSE openstack cloud and evaluate the use of policies as a means to develop HA solutions. The steps for this project:

I have a few ideas of improvements for the delogo filter included in ffmpeg's libavfilter. As a first step I would like to clean up the code by removing one unneeded option and then removing all the subsequently dead code.

I want to learn Erlang and see if it makes sense to use it in the context of High Availability (it would certainly seem like it). As a learning project, I want to try to reimplement my koi project (https://github.com/krig/koi) in Erlang. Koi is a minimal cluster manager I wrote in C++.

In openSUSE Asia summit 2015, there was a talk about the software defined networking, from the virtual switch, the controller, to the simulator. Just want to take a look at open vswitch and Ryu to learn more about SDN.

Learning REXX and improve FTPBOOT for installing and testing our S390 builds