Within SUSE we are using various systems for different tasks. E.g. GitHub and GitLab as DVCS, Jenkins for building or testing, OBS for building… and the list continues. Some of those systems can be interconnected in some way. But not every system can do that, especially if you are behind a corporate firewall and some (I'm looking at you GitHub) have a quota. So wouldn't it be nice to have something like a Big SUSE event bus, where every event we'd be interested in could be queried or subscribed to? But before conquering the world, we have to start small. Let's start with GitHub! GitHub has a decent API that let's you query their system. The goal looks like this: Allow multiple clients to query information from GitHub without using the quota irresponsibly. It should also be possible to push state changes to subscribers.

Improve the progress made with the GfxTablet last year https://github.com/Devp00l/GfxTablet / https://hackweek.suse.com/16/projects/turn-an-android-tablet-into-a-drawing-tablet. TODO:

Once upon a time there was a bot

@mudler Created devbot that was helping the qa-tools party.

I intend to create opensuse docker images ready for mining cryptocurrencies (cpu based algorithms like cryptonight as a first try), and if time permits, I will also try to deploy the containers using kubernetes.

While there are plenty of benchmarks that compare different IO multiplexing techniques such as epoll vs poll/select, there's really nothing out there that particularly measures epoll system call latencies under different scenarios. Design and implement a series of performance benchmarks for this call under the 'perf bench' framework.

PVH domains are a new guest type supported by Xen being as lightweight as possible (e.g. no emulation of legacy devices via qemu) while taking advantage of the hardware virtualization features of the x86 processor. As there is no BIOS for a PVH domain booting is a little bit different than for pure hardware virtualized guests. To be able to start such a guest a little shim is needed to gather some information about the environment (especially memory layout) before the standard kernel boot path can be entered. By using a boot loader like grub2 this shim can be avoided as the memory information is already known by grub2 and stored into the so called zeropage according to the multiboot protocol.

The YaST2 Network module manages network configuration including device configuration, DNS, Routing etc.. The current code is not very object oriented and in many cases there is not a good separation between the business logic and the presentation. The API is also not very clear an many people get confused for example between NetworkInterfaces (class that handles with the ifcfg-files and reside in yast-yast2) and LanItems.

See title

Let's dust off our Amigas, hook up our mice and joysticks, and see what elegant software and hardware could do back in the 80s and 90s!

There are plenty of old games that were compiled for Linux - particularly in Loki times around 2000. Let's see whether they can be played on a modern distribution, and how many compatibility layers are required.

media.ccc.de currently hosts about 5TB of presentation recordings. The main mirrors send about 5TB of videos each in a single month. Several OpenSource conferences are hosted on media, like the last two openSUSE conference, or the "All Systems Go!" conference. What started as a web frontend for ftp.ccc.de in 2007 has become a complex project that integrates deeply into the tooling used by the VOC team.

The DriConf-Project inside of MESA has seen its latest update in 2006 and is implemented with GTK+ 2. https://dri.freedesktop.org/wiki/DriConf/

Look at this beauty: https://github.com/crowbar/crowbar-core/blob/master/crowbar_framework/app/models/service_object.rb#L941 Nice uh? Its a 500 lines methods that its distinctly separated into 4 different pieces internally that make 4 very distinct phases inside.

Crystal [1] is a new language with a syntax heavily inspired by Ruby, but with statically type check and compiled! Its motto is "Fast as C, slick as Ruby", so good reason to start looking at it. I would like to play with it, check the powerful of its compiler and the C-bindings mechanism to call native libraries.

Currently I am using openSUSE Leap 42.2 as base system on the laptop where I do my daily work (Dell Latitude E7470). As a YaST developer my system is a bit broken (as you may guess) and updates are not possible. So it is time to start from scratch. The idea is to adopt some user friendly system for security copies, migrate to Tumbleweed, make extensible usage of virtual machines and try to stay the base system as clean as possible.

During regular L3 work I often don't find enough time to work on the command line disk partitioner parted which I maintain. Changes often directly affect yast-storage(-ng) and libstorage(-ng). @aschnell opens bugs faster than I can solve them. Upstream is often slow and often wants patches differently.

I will implement the ReaR upstream issue https://github.com/rear/rear/issues/1399

Problem statement

Once a kernel is built, a developer/janitor may want to boot the kernel for various reasons, such as performing simple boot test or running tests and workloads from user space or simply playing around in a shell. However, an easy to use and a descriptive tool to perform those tasks doesn't exist to our knowledge.