The idea is quite simple, and all the pieces should already be there - but what is, IMO, lacking is putting them all together: * take the TMP ownership,

A common task in L3 is to find a difference between package release X+1 which is reported as broken by customer and X which was working fine. OBS does not provide easy mapping between their revisions and package release numbers. It has "rdiff" command for comparing two packages from different projects, but it does not allow to select only one file or specify different revisions for compared packages. The goal is to prepare script that allows following checks:

I would like to learn more about ARM/AArch64 emulation in QEMU, especially the boot process and different board emulation. Goals:

Basically $topic, as of the latest release of ceph, we have some not so trivial support to pull off something like this at least for metadata, need to see if data sync is also permitted, and then probably hook it to sync to AWS itself

Small non profit organisations or activist groups need a Web presence that is easy to maintain by several authors. When using a CMS they do not have the resources to secure the CMS from the various possible attacs most CMSes are notorious for. Defacement or placing malicious content can damage the reputation of such non profit organisations. The solution would be to combine an of the shelf CMS with a static web server that is hosted on a different IP address. The authors would access the CMS through a kind of remote access gateway e.g. openvpn) where access can be well secured with certificates or even hardware tokens.

Rewrite the authboss Go library (authentication engine) for use with JWTs. Clean up existing code. Fix bugs etc. https://github.com/go-authboss/authboss

This is more like a learning project for me as a new hire, so please do not expect too much, :-) Compare difference of maintain flow for Libvirt and QEMU between SLE and HPE Linux

I freshly bought a small and cheap laptop ASUS 200H based on Cherrytrail. My plan is to install openSUSE on it, and bring it along with my vacation in the following week :)

This is preparation/accompanying project to my school thesis. Fontconfig is library that keeps database of fonts installed in system and gives applications ability to query it. Fontconfig is currently searching the database in naive way and can be quite slow if there is many fonts installed. Most applications make several font queries when starting and fontconfig is slowing down their start.

oscar is short for osc sugar, it will be a collection of little wrapper scripts on top of the openSUSE build service command-line tool that make it easier to use.

2019

Just an excuse to learn more about antlr and parsing in general. Update Implemented a very simple interpreter https://github.com/mateiw/littlebasic

openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal. But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?

1. currently when you navigate to Test Results page - it will load everything before show you the page. I plan to change this model into "load on demand" approach
2. Test Details page currently show you thumbnails for all modules. Want to add expand/collapse functionality for thumbnails - by default you will not see them for passed modules. But you will have ability to expand them. Also I will add "Expand All"/"Collapse All"

COREWAR is a programming game in which two or more programs (warriors or viruses) compete for the control of a virtual computer. The programs are written in Redcode, an abstract assembly language. - Learn about optimizing assembly: reading Redcode guides and manuals (individually or in group)

OpenStack is, undoubtedly, a really huge ecosystem of cooperative services. Rally is a benchmarking tool that answers the question: “How does OpenStack work at scale?”. To make this possible, Rally automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a pluggable way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an OpenStack CI/CD system that would continuously improve its SLA, performance, and stability. <img src="https://wiki.openstack.org/w/images/thumb/e/ee/Rally-Actions.png/850px-Rally-Actions.png" width="700">

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,

Features