Motivation / Problem

Right now, our QA team tests YaST with OpenQA very much based on keyboard shortcuts: Set the keyboard focus to the "User Name" input field with Alt-U, enter a user name, [Tab] to get to the next field, enter more text, finally Alt-N to activate the "Next" button.

Lately the necessary patches to get rudimentary support for the Mediatek chromebook with a mainline kernel got posted. There are some hacks and I'll work on some good solution to get graphics go, at least.

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.

djmount is a neat idea - see UPnP/AV resources in your directly in the file system. Unfortunately the code hasn't been maintained for ~10y, and - at least for me - seems to by plagued by various bugs causing crashes and what not. There's currently no official openSUSE package. This project aims to pick up the code, fix bugs, and make the tool actually useful again. The code itself seems to be in quite a good shape, so this should be doable.

There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started. The project started in Hackweek 16 (fall 2017) and has been worked on since, both in Hackweek 17-19 and outside. First two parts of kernel implementation are in mainline since 5.6-rc1, first part of userspace implementation (ethtool utility) has been submitted to upstream at the end of Hackweek 19 (2020-02-16).

meson[0], a replacement to autotools, is very popular nowadays. It's a lot faster than autotools as far as what I hear and see. Besides lots of GNOME projects has been ported to meson. As one of the maintainers of GNOME Logs[1], I need learn meson and try to port Logs to meson for faster building. *[0] http://mesonbuild.com/

Most large workloads such as SAP HANA require special, highly optimized configuration to run in a virtual machine. Virtual resources such as memory and CPU must be carefully configured to ensure optimum performance of the virtual machine workload. Default VM configuration created by tools such as virt-install are not optimized and often result in poor performance of large workloads due to memory access latencies and incorrect/incomplete information available to the VM's task scheduler. Currently, users deploying large workloads must manually optimize virtual CPU and memory resources, which can be error-prone and if not done properly can actually degrade performance. This project aims to create a tool that can produce suggested vCPU and vNUMA configuration based on a VM configuration template and capabilities of the target virtual machine host. E.g. something along the lines of

I want to experiment with three things: * Blockchain

Are you interested in pairing? Are you wondering whether it is something that would help you and your team members in your current project? Would you like to try it out before you fully commit to such an extreme idea? Then this is your lucky day Sir/Madam! Within the Cloud Foundry project you are expected to pair pretty much every time you are working on something. In the BOSH OpenStack CPI team this isn't the exception, so I've been doing it for the past 15 months. I'd like to transfer some of that experience to you fellow SUSE colleague. We can discuss about the pros and cons that this agile methodology has. For example, there are many misconceptions on how to pair, for once, having the right hardware makes a huge difference. During Hack Week 16 you have the chance to test drive a dual-control workstation (see image) which I believe is one of the biggest differentiators to have a good experience when pairing full time.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

Goals: (Subject to change)

There is a couple of libraries available for asynchronous and non-blocking processing of HTTP requests (in Java) that can be used to avoid having threads waiting for responses in request intensive applications, for example: - Apache HttpAsyncClient

Use this hackweek to practice and learn more about Go.

Mottainai - Task/Job/Build Server for everyone!

Written in Golang. You can find the source code on GitHub and docs here.

Yes this project is yet another project for creating a Suse Manager clone. The motivation for that comes mainly from my need for a simple suse manager that i can easily run at home without the massive overhead involved in suse manager setup. Also since i mainly need to manage opensuse machines most of which are tumbleweed, suse managers repository model does not really work well in that case.

The idea is getting a general knowledge of how QT Linguist works, and help FET with some translations. FET is a timetable creator, that is available for openSUSE at https://en.opensuse.org/FET, and allows a user to create a timetable, usually for educational institutions, with a lot of different available constraints.

Time for technical housekeeping in the shared Gran Canaria office. For the last couple of weeks, the Cubieboard powering our "SUSE office in a box" has been unresponsive. I want to check why. Fix it, update the system, etc.