We started the SUSE Musician's Space several Hackweeks ago, out of which we spawned the SUSE band, now known as SUSE LOUD.

New Development

Python is well known all over the world and has wide range of usage. Lets dive into to a bit.

TecnoAlarm is a house alarm system. The input devices are communicating with the main node of the system via an RS 485 bus. In order to be able to plug in such systems in a house automation system, its communication protocol needs to be reverse engineered.

Running openATTIC and DeepSea on Multiple Distributions

This was planned for previous hackweek (hw16-1)

This is the tool I've been working on since HW11 and it needs more work. Actually, there's always something which could be done on it. It is basically an x86 instruction decoder with special emphasis on the kernel and decoding interesting pieces of it in order to help in the development of low-level patching techniques, among others.

Description

It can boot up from udisk/floppy.

There is a lot to do in the openSUSE infrastructure land...

An introduction from minetest website: " Minetest is a near-infinite-world block sandbox game and a game engine, inspired by InfiniMiner, Minecraft, and the like. Minetest is available natively for Windows, OS X, GNU/Linux, Android, and FreeBSD. It is Free/Libre and Open Source Software, released under the LGPL 2.1 or later. "

Use this hackweek to practice and learn more about Go.

Time for technical housekeeping in the shared Gran Canaria office.

SUSE Manager can do some virtual machines management, but needs a lot to be complete. This project is about investigating more on that topic.

Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components:

The idea is to create a bootable medium (eg. pendrive) that allows:

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

The Kubic Project currently produces a "CaaSP-like" Tumbleweed OS, focused on Kubernetes clusters

In this hack week we want to focus on improving the existing components used for http://docsearch.nue.suse.com. Creating separated repositories for each service and pushing them to github.com is also desired.

Kernel dumps, provided by our customers, are uploaded by Customer Support to ziu.suse.de and shared via NFS to L3 servers at which they're analyzed. This procedure works, but likely has room for improvement.

L10N for the book entitled Designing with LibreOffice by Bruce Byfield

The goal of this project is to extend and consolidate the tools used by the Emergency Update Team.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

CaaSP is designed to be used with containers based on SUSE micro OS, using Salt as the management tool. CaaSP2 GMC is available at the moment. I want to spend the hackweek 0x10 to play with it, figure out how CasSP integrate and work with Salt.

Problem statement

Build a base image and template (both kiwi and Dockerfile) for openSUSE Leap 42.3 using the native OBS container building feature.

Problem statement

Once a kernel is built, a developer/janitor may want to boot the kernel for various reasons, such as performing simple boot test or running tests and workloads from user space or simply playing around in a shell. However, an easy to use and a descriptive tool to perform those tasks doesn't exist to our knowledge.

There are plenty of old games that were compiled for Linux - particularly in Loki times around 2000.

Within SUSE we are using various systems for different tasks. E.g. GitHub and GitLab as DVCS, Jenkins for building or testing, OBS for building… and the list continues. Some of those systems can be interconnected in some way. But not every system can do that, especially if you are behind a corporate firewall and some (I'm looking at you GitHub) have a quota. So wouldn't it be nice to have something like a Big SUSE event bus, where every event we'd be interested in could be queried or subscribed to?

Last time I checked QEMU lacked support for >= z10 processors. Thus one cannot run SLE12 and newer in a virtual machine on non-s390x host. I'd like to improve the situation during Hackweeks.

To make OpenQA work with real ARM devices, we need to control

The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu.

I've attempted this several times already and each attempt had different shortcomings. I'm kind of curious about how exactly will I fail this time.

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.

We all pant for customer data. Which hardware do customers run ? Which packages are installed ? Which services are running ? etc. pp.

I want to create devel project for cryptocurrencies/mining tools/blockchain related stuff, fill it with packages and submit at least some of them to Tumbleweed.

We need to package avocado, get it into distro and migrate some of our testsuites from ctcs2. Atm avocado is present in openSUSE:Factory and Backports exist at my home project

terraform-provider-libvirt supports CoreOS ignition file/content, which end rendered as kernel command line options (the provider does some nice stuff like allowing you to pass the json content and it will take care of putting it into a temporary file).

The aim of this project is to finish up the work already done in previous editions of Hackweek in regards to zypper-docker. That being:

retro-gtk is a toolkit for GTK+-based Libretro frontends. It is mainly used by GNOME Games to play retro games via Libretro gaming console emulators.

A lot of custom-built or ethusiast-level keyboards such as the Planck, Zeal60, Let's Split and many more use an open-source firmware called QMK. This firmware allows you to freely define your keyboard layout and add a lot of functionality (i.e. emitting a different keycode on long and short keypress, dual-function keys, leader keys (think of vi's :)). We could use the Hack Week to add functionality, check the source code for security issues and add support for more keyboards.