Often when we test maintenance updates or when we decide to push an update for a package we want to know what that change may cause. Right now it is really difficult to figure out what package depends on a given package.

Motivation

Project Description

• Create an automated L0-support-like analytics solution for supportconfig data that is tiered across a customer's environment and SUSE environment (similar to a very modular AIOps Edge-Core approach). A pictorial overview of the ecosystem

Deploy Uyuni as an app from the Rancher marketplace - or install via Helm on any Kubernetes cluster, on any OS, or any Public Cloud.

The dream

Project Description

Make use of the Studio Kiosk in front of my office:

The Kubic Project currently produces a "CaaSP-like" Tumbleweed OS, focused on Kubernetes clusters However many of the attributes of Kubic (read-only filesystem, transactional updates, containerised services) could be an interesting platform for another use A Chromebook-like Linux Desktop

Flatpak (previously known as xdg-app) is a bundle system, based on ostree, to easily make available applications bundle to users. Currently, flatpack is available on openSUSE Tumbleweed but we don't ship any runtime based on openSUSE (freedesktop or GNOME runtime). Also, it could be interesting to generate flatpak bundle directly from OBS, if possible, using either available packages or directly application sourcecode.

Idea is to have SUSE system with OpenZFS as root FS. Why ZFS

Matrix.org is a project to create a protocol and server implementation to replace IRC. Unlike closed tools like Slack, or even open Slack clones like Rocket.chat, Matrix is not focused on a web-client only, but on the protocol to cover all types of clients (text, desktop, web), it is federated (no single server), and it covers good IRC integration (the public matrix server is even on Freenode), and it adds features that Slack clones have like persistent history, pictures, etc.

L3 bug reproduction often requires becoming the admin for a moment. I'd like to write down some nifty tricks I used to get certain “interesting” system configurations to work.

Project Description

Let's write a decent replacement for software-o-o. We want to choose the right technologies for the project, as technologies and missing volunteers is where we failed this time.

Initially, the Agama D-Bus service was written 100% in Ruby. For many things, it relies on YaST, so it makes sense to use the same language. It was great to have something working quickly, but it also had some drawbacks. The main problem is that, as YaST is not thread-safe, we separated the service into different processes (storage, software, localization, etc.). The system became most responsive but at the cost of eating a lot of RAM.

Moving to Rust

Continuing last year tweaks of packman project we should proceed in the good work and reduce the packman to provide smallest set of packages possible on Tumbleweed (later on inherited by 43.0...). One of the cool results planned is that on stock openSUSE Tumbleweed user will be able to run most of the multimedia apps and play youtube (this is already working) and also with addition of non-free repository being able to run netflix.

Let's use the Hackweek to improve Ruby, the programming language I use every day. It is while using a language when you can realised that things that need/can to be improved, so there are many things that only Ruby developers can raise up. Also, getting involved in the development of Ruby will help to get a better understanding of how it works. So I will take my ideas/concerns to the Ruby community and implement some of the them in the code of the Ruby core. Ruby features and bugs are tracked in https://bugs.ruby-lang.org/projects/ruby-trunk/issues

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"

Status at the end of hackweek 10

The idea is to create a fantastic robotic SUSE pet using cheap materials. It will be moved with you remote control of your TV. After building the prototype the schemes and Arduino code will be delivered for everyone to try building it at home.

Sometimes you search for a package, and you don't find it because you're not typing it right. Of course there's regex support behind the scenes but it requires conscious effort to make use of.

Motivation

Project Description

The folks at Asahi linux have been working on porting linux on the Apple Silicon. In a recent blog post they announced they will be joining forces with Fedora on releasing a Fedora Asahi Remix. I would be happy to see this level of collaboration between Asahi and openSUSE community, too.

There are a couple of interesting initiatives that make the openSUSE project interesting for SMB, such as

The Invis Server