Create a prototype of an agent on kvm hosts to control the distributen of master / worker nodes between different kvm hosts. No central control plane should be used - the main design goal should be: as simple as possible :-)

Termux is already bringing a terminal and debian package manager to Android. Let's see if we can reuse it and provide a base system with zypper and build openSUSE:Factory for it in OBS.

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.

Currently we have two sponsored 3D printers available in the Nuremberg office. Both are located in a lab - which makes it hard to access them. Both also need some (hardware) maintenance. This (hopefully short) side project should make the printers more usable and accessible for others.

The project aims to port openSUSE to the ROCKPro64. The ROCKPro64 is the most powerful Single Board Computer released by Pine64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a MALI T-860 Quad-Core GPU.

Last hackweek filtra was created – a tool to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban. The collected metrics can then be visualized with Grafana. Currently there are two problems with filtra:

Why is it nice?

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. What do I plan on doing? a few things, so please reach out if you would be interested in any one of them. I will update with a list later.

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.

SUSE CaaS Platform is a Cloud-Native Computing Foundation (CNCF) certified Kubernetes distribution. - Family with SUSE CaaS Platform

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.

This project aims to run VMs in a CaaSP 4 cluster using kubevirt and a libvirt+qemu container (aka compute container) based on SLES15 SP1/2. Compute containers based on openSUSE Leap15.1 and SLES15 SP1 already available in registry.opensuse.org and registry.suse.com respectively. VMs can be deployed to the cluster but there are several functional problems that need investigating, e.g. accessing the VM's serial and VNC consoles, proper network access, etc.

With 'pint' the Public Cloud Team already provides a command line based tool to get information about the images we're hosting in the public clouds. It's provided via the Public Cloud Module in SLE as well as in the Cloud:Tools repo. As more and more people are asking about information on the images we've published but not all of them feel comfortable using tools on the command line we like to provide a web UI which shows that data. One should be able to search for specific images, sort by regions or state etc.

Give a more complete overview of the infrastructure and the processes the documentation team uses to write, maintain, and publish the documentation for the SUSE products. Add missing information/chapters to the guide.

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

It would be nice to have a OS that can be tinkered with easily by having only a compiler as the only binary on the system.

The next release of Ceph (Octopus) will be delivered via containers.
A new tool named cephadm is being developed to bootstrap and manage Ceph containers.

The goal is to use the work from the debug-early GCC branch to generate better debug information for LTO compiled objects, especially with regarding to language specifics like classes and templates. This has now been achieved and openSUSE Factory

I have several themes in progress, they all need lots of work before they could be used with openSUSE. * The gtk people keep changing things so the gtk theme I use to match my enlightenment theme also needs fixing.

openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore. Come up with ideas and a prototype of how manual testing could be guided, tracked, visualized for a rolling development distribution with volunteers testing.