We started the SUSE Musician's Space several Hackweeks ago, out of which we spawned the SUSE band, now known as SUSE LOUD. Since there are a lot of musicians in SUSE, not all rock musicians, we decided to see whether we could get some other music projects off the ground during this Hackweek.

New Development In previous hack weeks, the first few days ended up being wasted on just getting it working. I'm pleased to share that the code quality has improved dramatically since the last hack week and there are now extensive test cases for both unit testing and testing against real vmcores, and we'll use both mypy and pylint (if installed) to perform static analysis. Packages for those are available in openSUSE or as part of the crash-python OBS repo for SLE15. It has been tested with kernels from 3.0 to 5.1.

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) => Automated deployment of virtualization hosts and build up of virtual machines for xen+kvm+related tool testing.

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. git repo: https://gitlab.suse.de/bp/x86d

Description

It can boot up from udisk/floppy.

There is a lot to do in the openSUSE infrastructure land... So let's start, have a look at https://progress.opensuse.org/, take some tickets and try to resolve them as good as possible. There are also other interesting topics:

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. " In short, MineTest is a Free and Open Source re-implementation of MineCraft, but it provide many flexible features compare MineCraft. It's not only a game but also a framework for developers to extend so to make their own worlds.

Use this hackweek to practice and learn more about Go.

Time for technical housekeeping in the shared Gran Canaria office. For the last couple of weeks, the Cubieboard powering our "SUSE office in a box" has been unresponsive. I want to check why. Fix it, update the system, etc.

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

The idea is to create a bootable medium (eg. pendrive) that allows: * Selection of either SLES, Leap or Tumbleweed.

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

The Invis Server

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

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. We also want to create the theoretical foundation for categorizing text to improve the search results.

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. The goal of the project is to understand the workflows and needs of Customer Support, L3 and engineering (Labs) and to implement a system to automate parts of the workflows.

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. - Port some of our tools to the maintenance API

Doc as Code with Asciidoctor, Jekyll, and TravisCI

Goals: (Subject to change)

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. My target is to understand the CasSP, like the advantage it take to k8s. How salt works in CasSP?

Problem statement

Right now, we have different resources to pool videos. The goal of is to consolidate all video resources into a central place to make them easily searchable, and enable a youtube like experience, rather than a simple file list.

Build a base image and template (both kiwi and Dockerfile) for openSUSE Leap 42.3 using the native OBS container building feature. Results/WIP will be available here:

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. Let's see whether they can be played on a modern distribution, and how many compatibility layers are required.

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? But before conquering the world, we have to start small. Let's start with GitHub! GitHub has a decent API that let's you query their system. The goal looks like this: Allow multiple clients to query information from GitHub without using the quota irresponsibly. It should also be possible to push state changes to subscribers.

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: - RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)

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 * Reset

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. Something like a notification with a button to perform the upgrade with just one-click, instead of having to deal with the terminal, that frights some new users and gives them the sensation of an outdated system.

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. And it looks like I haven't failed 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. A lot of this data is in the supportconfig. But this is neither collected, nor centralized, not easily accessible.

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. Lets go on as Standa took care of creating network:cryptocurrencies

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 idea is to:

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: - Separation of the CLI part and the library.

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. Currenly retro-gtk supports only software rendering. There are two ways hardware rendering can be used in retro-gtk:

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. If you own a qmk-running mechanical keyboard or plan on doing so feel free to join me :)

What is HRV ?

HRV is a method for measuring the ability of your heart to respond to inner and outer levels of stress.

Take some online classes for penetration testing tools and then practice using them. The goal is to learn enough to provide some value for pen testing of real products. Originally I was hoping to have a real cloud to pen test, but that appears unlikely so I plan to set up an Apache web server instead as the system under test. It won't matter much as the goal is to learn to use the tools.

As in near future, there will be python2python3 in Factory but no /usr/bin/python and in SLE-15 base no python2 it is necessary to start checking/switching dependencies. See also:

Motivation / Problem

Right now, our QA team tests YaST with OpenQA very much based on keyboard shortcuts: Set the keyboard focus to the "User Name" input field with Alt-U, enter a user name, [Tab] to get to the next field, enter more text, finally Alt-N to activate the "Next" button.

Compared with traditional file systems (e.g. EXT4, XFS), log-structured file systems treat its storage as a circular log and write sequentially to the head of the log. I want to learn about this kind of file system via this hack week, to understand how it manages its data and metadata, to understand how it recover back from crash, to understand its advantages and disadvantages.

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.

The SLE15 development model follows the Factory First policy, where all submissions need to go first to openSUSE:Factory and then to SLE15 repos. This way more bugs are fixed, less patches get lost, less backporting is happening etc. Our openSUSE infrastructure is using salt for configuration management. This was working fine, but suddenly we had to split the openSUSE from the SUSE-DMZ services into separate VLANs, thus the salt codebase had to be split as well. The code itself is mostly formulas and quite similar states between the two set of services though. The only real difference was in the pillars, and even there there was a lot of duplication.

Fresh air and motion helps your brain to come up with new and creative ideas. This hackweek project offers exactly this*. You can expect running exercises along the Nuremberg city wall. Running 25 to 50 meters sidewards, jumping, running stairs, etc. will give your brain new energy.

While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device. This allows to read from inside the VM a blob by reading /sys/firmware/qemu_fw_cfg/by_name/opt/keyname. The driver is included in recent Linux kernels.

This would be a multiple step solution, a first idea that I would explore would be: 1. Query Florian's qam_reposervice API from RRID to base products and modules needed for update

I would like to work mainly on https://fate.suse.com/323638, think of default configuration and perhaps create a small configuration script for conky.

• learn how to write Dracut modules
• investigate running Salt in Dracut initrd

Yes this project is yet another project for creating a Suse Manager clone. The motivation for that comes mainly from my need for a simple suse manager that i can easily run at home without the massive overhead involved in suse manager setup. Also since i mainly need to manage opensuse machines most of which are tumbleweed, suse managers repository model does not really work well in that case.

The DriConf-Project inside of MESA has seen its latest update in 2006 and is implemented with GTK+ 2. https://dri.freedesktop.org/wiki/DriConf/

Look at this beauty: https://github.com/crowbar/crowbar-core/blob/master/crowbar_framework/app/models/service_object.rb#L941 Nice uh? Its a 500 lines methods that its distinctly separated into 4 different pieces internally that make 4 very distinct phases inside.

See title

The YaST2 Network module manages network configuration including device configuration, DNS, Routing etc.. The current code is not very object oriented and in many cases there is not a good separation between the business logic and the presentation. The API is also not very clear an many people get confused for example between NetworkInterfaces (class that handles with the ifcfg-files and reside in yast-yast2) and LanItems.

Currently there is support for TAP being added to OpenQA::Parser::Format However it has basic support, therefore the following is needed:

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.

Automate the process described here: - https://github.com/aspiers/git-deps/#use-case-2-splitting-a-patch-series

Elixir is a Ruby-ish dialect of Erlang with meta-programming capabilities, this is my first project using it: pedro . The idea is to create a task manager that would organize tasks (jobs) and manage them in projects. It will be running locally, remotely or both in multi-node setup, will provide CLI, have web UI relying on http and websockets. It makes use of erlang OTP, web framework phoenix that is inspired by rails. Author of elixir and main contributor to phoenix is Jose Valim, he's also the author of devise rubygem and former contributor to rails.

Live audio tools could use some work in openSUSE and are fun to play with. Finally many of these tools are making it into tumbleweed (And Leap 15.3) especially Cadence.

There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test. But in fact it's a UI desaster that almost never works. So the goal of this hackweek project is to get rid of it - and instead build a real control from the webui into the backend allowing tests to be written on the fly including needle creation/updates. Easy as that.

The openSUSE build service could build hundreds of packages in parallel but in practice serial package dependencies prevent that.

There are many fun peripherials that you can connect to a RPi but PC users are not left out either * attiny85 <a href="http://www.banggood.com/ATTINY85-Mini-Usb-MCU-Development-Board-For-Arduino-p-971122.html&quot;&gt;&lt;img height="48" src="http://img2.banggood.com/thumb/large/2014/xiemeijuan/03/SKU207366/SKU207366-3.jpg&quot;/&gt;&lt;/a> has SPI and i2c interface so could be possibly used as USB<->i2c or USB<->SPI bridge. Unfortunately, the USB support needs some non-standard timings so there is quite a bit of integration and debugging needed.

BPF Compiler Collection (BCC)

https://github.com/iovisor/bcc

My current mail setup is mu4e and emacs based mail client included with the amazing mu mail indexer. mu works similar to notmuch but allows easy bidirectional operation with the original Maildir. Add mbsync (isync) to sync imap locally and msmtp and you have a full mail setup.

Oficina, a mechanical workshop application developed in Qt/C++ Hackweek 17: Work on TODO - Test. Make it very stable, after that, insert it in openQA.

djmount is a neat idea - see UPnP/AV resources in your directly in the file system. Unfortunately the code hasn't been maintained for ~10y, and - at least for me - seems to by plagued by various bugs causing crashes and what not. There's currently no official openSUSE package. This project aims to pick up the code, fix bugs, and make the tool actually useful again. The code itself seems to be in quite a good shape, so this should be doable.

Implement a basic file search for a given OBS project. An example of basic functionality can already be found for Ubuntu or Debian. The goal is to implement,

Features

2019

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.

Plans of the Project

After some time I would like to move KF5 translation ahead again.

Rust Emacs clone (sort of), see README for details.

A nice project for enhancing the winter time: Download Model

With all those analyzers for C code we get so much information about our C code. Yet our shell code regularly nukes systems.

kCFI is a tool that enables the compilation of commodity Operating Systems with Control-Flow Integrity protection. kCFI first prototype was developed/implemented during a PhD program held in the University of Campinas, in Brazil. Although fully functional, the tool remains in a very experimental shape, needing to be refactored prior to being released. As kCFI consists in multiple tools, which include compiler plugins, kernel patches and binary analyzers, its deployment is considerably complex. Once code refactoring is finished, the next step consists in setting up proper repositories for the tool and for each submodule, along with scripts and documentation to enable easy configuration and compilation on new environments.

Everything is (in) a module now. They depend on each other and you need a whiteboard and a few different colors to understand and remember how.

There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started. The project started in Hackweek 16 (fall 2017) and has been worked on since, both in Hackweek 17-19 and outside. First two parts of kernel implementation are in mainline since 5.6-rc1, first part of userspace implementation (ethtool utility) has been submitted to upstream at the end of Hackweek 19 (2020-02-16).

1% of SUSE Manager's functionality in 0.1% of the lines of code

Let's create a much simpler SUSE Manager — one you could use at home! Users should be able to deploy and operate in minutes with minimal configuration, while still retaining the very core features that make SUSE Manager useful!

Most large workloads such as SAP HANA require special, highly optimized configuration to run in a virtual machine. Virtual resources such as memory and CPU must be carefully configured to ensure optimum performance of the virtual machine workload. Default VM configuration created by tools such as virt-install are not optimized and often result in poor performance of large workloads due to memory access latencies and incorrect/incomplete information available to the VM's task scheduler. Currently, users deploying large workloads must manually optimize virtual CPU and memory resources, which can be error-prone and if not done properly can actually degrade performance. This project aims to create a tool that can produce suggested vCPU and vNUMA configuration based on a VM configuration template and capabilities of the target virtual machine host. E.g. something along the lines of

Behavior-Driven Development is a process to follow in software development. I want to learn how BDD testing framework works. Learn how the pieces fall together and how frameworks are put together, as well as best practice of BDD.

I want to experiment with three things: * Blockchain