Upgrade OBS crash to current upstream latest release

Description

Continue the work on kqlite (Lightweight remote SQLite with high availability and auto failover).

[User]

As we know, we have ABC notation or GNU Lilypond for music staff. It takes ASCII as input and generates music scores and even MIDI format, which is very convenient for people to type music in computer.

Connect is the "social network" of the openSUSE community. While this might not sound so important, the problem is that the tool is used for membership management and all the other "administrative" stuff for the openSUSE community, which makes it a very important tool.

Laitos is an open source project written in go, it emphasizes simplicity of maintenance and delivers a complete suite of web, DNS, and mail servers to host a personal web server. Beyond the suite of servers, laitos software hooks into numerous API platforms, that altogether enable user access to Internet features (such as Facebook, Twitter, emails) via alternative communication infrastructures such as telephone (PSTN), SMS, and satellite terminals.

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.

Right now our concourse instance http://salzbreze.suse.de:8080 runs containerized (via docker-compose) on bare metal

Pi Security

With the approach of kernel 5.6 SGI Octanes are supported with builtin IO components. What's missing for a graphics workstation is a driver for the graphics card. There is already a not upstreamed framebuffer driver for Impact graphic cards. Since there will be no new framebuffer driver accepted upstream, the goal of this project is to convert the existing frame buffer driver to a DRM driver and make it ready to be sent upstream.

Description:

Project Description

The kernel livepatching team developed klp-ccp to automate the work intensive task of copy&pasting self-contained livepatches from the original kernel sources together. We started using it right away as soon as it had been in a somewhat workable state, even though some quirks and workarounds are still required in everyday usage. The main barrier towards developing klp-ccp further is its internal compiler abstraction, intended to keep the generic code independent from the original compiler resp. the target architecture. It evolved over time and had been amended incrementally in an ad-hoc fashion as needed to quickly reach the main goal at the time. So there's room for improvement.

Description

The idea is to build a FOSS command line (for now) secrets management tool, you may have heard of SOPS or Hashicorp Vault, with Spritely Goblins.

Description

This project aims to explore the popularity and developer sentiment around SUSE and its technologies compared to Red Hat and their technologies. Using publicly available data sources, I will analyze search trends, developer preferences, repository activity, and media presence. The final outcome will be an interactive Power BI dashboard that provides insights into how SUSE is perceived and discussed across the web and among developers.

Recently I became a (not very proud) owner of Acer Aspire Switch 10E, a small notebook/tablet convertible based on Intel baytrail platform. Replacing preinstalled (32-bit!) Windows 8.1 with (64-bit) openSUSE proved more challenging than expected, mostly because the device is haunted by a 32-bit UEFI so that it took me a week to make it boot without an external USB flash disk.

In ubuntu, you can install grub-ipxe, which adds an ipxe entry to the grub menu. This allows you to easily pxe boot on machines that may not natively support it. You can also use it along with grub2-reboot to remotely re-image a machine. The project has been started here: https://build.opensuse.org/project/show/home:blarson:grub-ipxe

Being part of SUSE's Storage Team I frequently talk about our Deployment tool called Deepsea.

Once more mailprocessing has developed some bitrot, namely this recent crash:

Hydrogen is a software drum machine and pattern editor.

Last hackweek I have use multi-machine for RMT testing. This hackweek I would like to research how to develop the multi-machine at openQA.

Since a few months it is now possible to build an upstream QEMU which includes only our supported VCPU accelerator.

I'm using soundkonverter a lot (my whole music collection is flac, but for the car or my children I prefer mp3) and it is working fine. However when doing mass conversions, building the list of files to convert can take ages. It seems the filelist is being re-created for every title added. Debug it and try to fix it in order to speed up this operation.

Displays your openQA instance status, the feature/behavior should had at least like the list below,

We had old arndale images working, but those were based on openSUSE-12.x which is now long obsolete and bad (e.g. missing security updates).

The openSUSE build service could build hundreds of packages in parallel but in practice serial package dependencies prevent that.

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE.

Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this.

An initial prototype from the last hackweek can be found on YouTube

I just got the FST-01G device from my friend, which could work as the Gnuk token. I'm going to try to make it work for ssh authentication.

Currently, way we distribute ssh keys within QAM on our testing infrustructure is a bit cumbersome - maybe we should try to (ab)use existing salt used by our internal infra team.

My goal is build on Alberto's work on "yomi" and the new Salt-based virtualization management features that Cedric has contributed, then combine them with a Redfish prototype to do the following from one (ideally idempotent) Salt state (orchestration state if required):

The idea is to hack os-autoinst-distri-opensuse infrastucture and explore design patterns that can fit. The end point of this is to restructure the framework in such a way that the main-common.pm is more efficient, functional and readable.