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.

Learn how to develop and create some plugins/apps for rocketchat. One that comes to mind is to enhance gerrit links which all are enriched with the same text, no matter what you link. A plugin could extend those links into printing some proper info like the patch name so its easier to click on those.

I would like to set up a small backup server on my spare hardware What I have:

Be familiar with the process of writing a test case in openQA by taking a ticket from a QA team.

In a 2-node HA cluster without quorum server, since neither of the cluster nodes (partitions) has more than 50% votes in case of split-brain, we should configure corosync.conf to enable two_ndoe: 1, so that both nodes (partitions) will be granted "quorum". But there'll be potential fencing matches which could introduce double-fencing by chances. The current solution is using random/static fencing delays by configuring pcmk_delay_max/base parameters for stonith resources to prevent double-fencing.

CephFS is awesome, but without a VPN it's not safe to be routed over the internet, and it lacks client support on many platforms. The Linux Kernel Library allows for the linux kernel to be built as a cross-platform user-space library and integrated into a regular Android, Windows, macOS, etc. application. This project combines CephFS, LKL and wireguard, and sprinkles some io-uring on top. My objectives are:

Uyuni is an heterogeneous and giant project (actually it is a beast) made of many pieces, many languages, many internal architecture structures, and also very old and new technologies live in it. Said that, and based on the fact Uyuni delivers tons of features/functionalities not all the end users use, it is not trivial at all to understand

Based on an old customer feature request: zypper history command options so that it can show the security patches installed on a server and when they were installed, during a defined period of time.

There is always something to do if you run the infrastructure for such a big project like openSUSE.... Our Admin wiki currently lists over 80 machines - and while we already "salted" some of them, there is always room for improvement and room to learn something new just by making your hands dirty and diving into the administrator role for a machine.

Simplify the codebase by using a more modern toolkit to accelerate maintenance and future development. Enjoy Hakkaweek!

There is a number of annoyances and pending improvements when working with the Salt Formula for provisioning Prometheus Exporters in Uyuni: - Fix issue with cleanup in case the monitoring entitlement is removed.

Recently, ConnMan got support for iwd and WireGuard. The current support is only a starting point and it needs some more changes in the core code base to support the cool features:

Continue improving my personal project, bard. Bard is a music manager for your music. It stores all information about your music collection in a Postgresql database . The current release can be used from a terminal and has the following working features:

Idea is to write FF plugin which would process raw autoinst log and display it in more readable form .

I started Standford's machine learning course but after getting stuck in one assignment (ex4, Week5), it fell of the table due to lack of time and focus. I will use this Hack Week to make some progress on it.

Summary Using K8s for managing VMs is a requirement in many environments, as not all applications are designed to be cloud-ready. Some projects like Kubevirt[1] and Virlet [2] aim to address this requirement. However, they introduce their own complexity, creating a parallel control plane for VMs. RancherVM [3] has a different approach, launching VMs as pods, but requires custom-built images.

I would like to learn and play with RL/ML and Go ( gorgonia for example). The lack of Reinforcement Learning library in Golang makes me very sad, so I wanted to implement a RL algorithm and alongside create a small library for RL and go in general. On the other hand, I would like also to expand and add features on a project that I'm working on: https://github.com/mudler/luet . It's a package manager based on containers, focused on cloud/OTA-alike update delivery. It would be nice to combine the two ideas, for e.g. to achieve one feature.

https://gitlab.suse.de/l3ms/RES-weather/ needs some improvements, e.g. manual generation of statistics and reports.

• Check and verify SGML tools
• Parse and validate mostly markup-less files with SGML tools

Very often people find themselves wanting to store secrets in a way that either they can recover even if (for instance) their house burns down, or allow friends and family to recover if they pass away. Existing solutions to this problem are: * Too complicated to use for ordinary people.

GNOME Software supports distribution upgrade, that only requires a few clicks for upgrading your system. But it's not integrated into Leap. So this is that I plan to do this Hack Week.

Involved components

Zero-ish downtime deploy on da cheap!

This project aims to get a 0-ish downtime deployments (very easily achievable with Kubernetes) just using:

At present it is our practice to "vendor" all dependencies for a Golang package. This has the advantage that everything is in one nice package and self contained but it has the disadvantage that dependencies are hidden and therefore security issues may slip through the cracks. The idea is to investigate and create automation "go2rpm" that generates a spec file with the necessary "BuildRequires:" such that the dependencies can be broken into golang- packages and we get rid of the implicit dependency inclusion via "vendor". The potential problem is scale, with some golang applications having thousands of dependencies.

Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development. In order to modernize the Mash workflow I plan to spend the week digging into a plethora of tools to first learn then build out a new workflow. The goal is to simplify deployment by choosing tools that provide consistency, modularity and repeatability. By leveraging the best tools available we can harden the code and accelerate the release cycle.

Future of tools supporting editors in dealing with particular languages is in my opinion in the LSP protocol. Therefore I look with a bit of worry on the fact that there is no good LSP server based on the top of rope. python-language-server uses it a bit internally, the Microsoft Language Server for Python is in C#, so it is completely something different. The goal of this project is to write a very simple nucleus of the LSP server based solely on rope for the language analysis and actions, which would be at least able to do “jump to the definition of a symbol”.

Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients.

There are various home assistant solutions out there but all of them transfer your voice to some server for processing. This is a no-go for sane people although the technology is interesting and could be useful. There are various open source tools out there to achieve the same result but there is no turn key open source self hosted solution. The goal of this project is to implement a way to have a home assistant running locally - ideally with one command. The project that is closer to the desired result is Mycroft (https://mycroft.ai/). It is very easy to run the client side components using one docker command but their backend is running remotely. All the tools they use though are open source so it only needs one to do the work and package them in a nice little docker-compose file (https://mycroft-ai.gitbook.io/docs/about-mycroft-ai/faq#can-mycroft-run-completely-offline-can-i-self-host-everything).

Finglonger is an internal tool used by the SUSE Manager team intended to make the life of the Round Robin Bug Guy easier. It was originally written by @fkobzik in Clojure. This is an attempt to learn some Go by reimplementing Finglonger.

define data types to collect informations about cameras and lenses to have a shared data store for lensfun and photo editors. Current state:

Libyui REST API

In the previous hack week project I was focused on implementing a REST API for testing the YaST modules.

****The motivation is create a open source solution, base on this business astronomy products: AZWO Asiair

I recently bought a Lioncast LK200 RGB keyboard which is a nice piece of hardware and has exactly the look and feel I want. All basic functions work well under Linux. Unfortunately the manufacturer only provides user software to upload/download profiles and control the LEDs for Windows. The device can be configured and operates autonomously from any OS but color setup is a PITA and it's very easy to factory-reset, and lose all config. I approached them but Lioncast seems neither interested to support native Linux nor to provide protocol specs so one can implement it. I thought to take this as an example to learn about reading and reverse-engineering USB device software.