Description

Create a tool which will make it possible to monitor the lifecycle of pods in a kubernetes cluster (as well as other types of tabular or structured data), and provide a convenient user interface for viewing and interpreting that data. This will be useful in development and testing of our kubernetes-based container platform (Cloud Application Platform), as it will allow us to better understand where things are going wrong when we encounter component failures.

GitLab provides a bridge to connect to Gitter using an IRC client.

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

I tried to work blockchain into this, just so we could cover the trifecta of buzz words. Sadly I could not maintain saintly and do this.

Let's pick some old classic game, reverse engineer the data formats and game rules and write an open source engine for it from scratch. Some games from 1990s are simple enough that we could have a playable prototype by the end of the week.

We currently maintain all drivers in the SUSE kernel tree. While this is a well-established procedure, it also has a number of drawbacks in my opinion. I've been experimenting with a different model, tracking (so far, only one) driver in a separate git repository, and packaging it as kernel module package (KMP). This way of working fits my own mental model of code development better than the quilt style we employ in day-to-day driver maintenance.

The goal is to find a way for developing and simple testing an IONIC based multiplatform app with REST API on openSUSE. The focus is to find a way to secure token handling for SSO.

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.

ABF is a buildsystem developed by ROSA (rosalab.com) and OpenMandriva (https://www.openmandriva.org/) currently being used for their distribution.

Take the oportunity to learn Kubernetes, to play with AWS and compare performance and availability of openQA and OBS instances and openSUSE Mirrors running on AWS.

Debian

I got a Raspberry pi 4 not long ago, I'd like to install openSUSE Leap 15.2(Alpha) on it, and set up hass - Home Assistant, a open source home automation assistant on rpi4, then have some fun with it!

The Gameshell is a small game console based on AllWinner R16 (Cortex-A7, IIRC the same CPU that the RPi2). Currently is supporting Debian, and some community member ported ArchLinux on it.

Many cases are Client-Server testing or Multi-Machine testing in FIPS area, I plan to hack and learn more deeply about Multi-Machine test automation in openQA.

Create DevOps automation for testing PTFs prior to delivering to customers, that will be available to each of the team members using standard L3 tools.

Investigate possibilities for the distributed builds for Ceph to speed up builds.

Learn and use tools to build/deploy SUSE/openSUSE to the KVM environment for developing kernel CVE patches and testing automation

I started 3 years ago creating a CNC, but soon last past 6 monts I realized that I could use it as a 3D printer. The software was good enough, the hardware and firmware had evolved. And now I could print 200x200x300 pieces with 0.1mm precision.

Solid Ground is an essential software tool for the daily tasks of an L3 agent. A continuous integration/continuous delivery (CI/CD), and even more a continuous deployment, approach is currently missing from its development ecosystem slowing down its release cycles.

Put together a collection of ideas and resources to mentor people managers on how to make better decisions:

Diagnosing issues with stalling desktop application (or a whole desktop environment) is difficult these days as the application often requires multiple processes interconnected with sockets, pipes, futexes, etc. to work and often it is not clear which process is the one responsible for blocking the whole ecosystem. The idea of this project is to write a tool that gathers information about processes in the system and for each process that is sleeping display the resource (file, socket, futex) it is waiting on as well as the process that is likely responsible for unblocking (feeding pipe, sending data to socket, unlock futex, ...). Once the information is gathered, we can also plot it for graphical displaying with tools like graphviz.

This issue has been blocked for a while due to time constraints so I want to take Hackweek 19 to work on it.

Currently AWS uses a SMT solver to decide on public/non-public policies https://aws.amazon.com/blogs/security/protect-sensitive-data-in-the-cloud-with-automated-reasoning-zelkova/

Avahi is (among others) a domain names auto-configuration system for Linux compatible with Bonjour.

transactional-update, the application to update read-only systems such as openSUSE MicroOS and openSUSE Kubic and the Transactional Server installations of openSUSE Leap, openSUSE Tumbleweed and SUSE Linux Enterprise Server, evolved from a POC to a fully fledged solution - and is currently completely written in Bash. This has been working really well in the past, but is gradually reaching its limits, especially when thinking about supporting additional file systems or ports to other Linux distributions - yes, we have a huge interest in other distributions adopting our technology.

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.

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

Testing GUIs is hard: unit tests require a tremendous amount of mocking and often don't capture the exact user input anyway, integration tests on the other hand are difficult to setup as they often require a dedicated infrastructure with virtual machines.

Motivation

For years we have been discussing the idea to modularize SUSE Manager. This would enable developers to create their own extensions to SUSE Manager without needing to touch the core repository.