We kinda need more flexible PXE in Prague office, UEFI would also not hurt - so lets check what we can do to make it better. EDIT (ggherdovich):

Build and benchmark some smaller SES clusters (2 - 3 nodes) targetted at edge deployments. Evaluate the performance and configurations.

Background

Given the number of different demands on our time and attention, it becomes increasing hard to focus and find the 'flow state' where a developer can be most productive. Interruptions due to chat notifications, email, and updater applets all break focus. Additionally, the desktop metaphor has in most cases failed to evolve as the browser and other MDI interfaces have become the focus for many users, and increased performance has allowed us to keep more tasks running and present on the desktop at once, presenting a higher cognitive load to the user.

OSC is already available on Homebrew, but it is missing the integration with Staging as the openSUSE-release-tools are not available. In this Hackweek project I would like to get the openSUSE-release-tools running on macOS via Homebrew.

There's a long standing request to extend the output of dmidecode to something that would be machine-readable. Something like an XML or JSON-based format. Unfortunately this can't be implemented right now because the output of dmidecode is generated by open-coded printfs as the DMI table is being parsed, with no intermediate structures nor temporary buffers. While implementing a machine-parseable output is out of scope for a single hack week, let's remember that even the longest journey starts with a single footstep. I would like to try and rewrite the 5200 lines of code of dmidecode in such a way that printing the output would be somewhat separated from parsing the DMI table and done by a limited set of dedicated functions. Alternative output formats could later hook into such functions.

I'd like a way to have a device on my desk which lights up to indicate that I have something I should be paying attention to. Initially, I'd like this to be for Office365 calendar events and GitHub mentions, but ideally it should support arbitrary messages. The plan is to assign specific colors (ideally "patterns" consisting of a sequence of colors and time) to specific message types. I have a handful of raspberry Pi Zeroes, a couple of OLEDs, a strand of individually-addressable RGB LEDs, a power supply, and some misc electronics (like the 3.3-5v logic level shifter necessary for the 5v LED strand). I'm thinking Python is probably the way to go for the software. I'm hoping OpenSUSE actually works on the Pi zero. :D If not, there's an ESP32 with a built-in display and a few Pi 3s laying around barely used, maybe one of them will work.

Since SUSE Manager doesn't scale out and stacking it into another pyramid of susemanagers won't help here, the real architectural changes needs to be done to achieve true scale-out of this product. This hackweek project is about how to Turn SUSE Manager into a cluster. Areas to be tackled:

Salt is moving towards a plugable architecture using POP and Idem. This project is about experimenting with those new concepts by applying them to a real life case: the virt execution and state modules. The goals of this project are:

Motivation

Running async actions in SUSE Manager lacks a user-friendly feedback. For instance, running a salt highstate on a system:

Put together a collection of ideas and resources to mentor people managers on how to make better decisions: - Useful mental models and how they work together

I'm hearing impaired. Where others have no issues following talks or dicussions, I often fail even grasp the bottom line what it's about. I've got hearing aids, but they help only so much. I also have an add-on device for my hearing aids that acts like a bluetooth headset. Unfortunately, making this thing work under my Linux desktop has been an ongoing, frustrating struggle. On the contrary, it works flawlessly with Android devices of different generations, and even with my lowly Gigaset phone. Actually, the thing works better with older kernels/Linux versions than with current TW. While I've little hope to solve the bluetooth audio issues on Linux for good, I hope at least to be able to understand better what's going wrong, and be able to slow down or even stop the deterioration I've observed lately.

I want to study the knowledge of openQA I will read the online documents and do some experiment in virtal-machine.

SUSE is using OBS as a build system and openQA for automated testing purposes. The goal of the study is to find out the strengths and weaknesses of these systems and compare them to other open source alternatives in a structured way.