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.

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.

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

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.

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

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

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

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)

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.

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.

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.

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

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.

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

The Invis Server

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!

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.

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

Description

It can boot up from udisk/floppy.

Why Knowledge is only useful if it is accessible.

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.

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

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

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.

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.

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'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.

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

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

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.

I'm using Conversations (XMPP+OMEMO) as an encrypted IM solution. Since a lot of groups organizing them self using WhatsApp, it's hard to stay away from it.

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:

After an internal call for help to take over software.opensuse.org deployment, I spend some time studying the code in order to find out what would it mean to take it over. The main reason was a PR from the community that has not been merged, and deployment depending on internal SUSE employees.

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:

Learn how openQA was implemented in details. And will spend some time to learn Perl (e.g. read the book <Learning Perl>)

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.

Customers are using complex storage stacks such as LVM over dm-crypt over MD RAID over multipath over iSCSI and FC with LOTs of LUNs, and we're facing problems in that area which are usually very hard to reproduce. It's also hard to guard against regressions. Being able to quickly and reliably set up VMs with various types of storage / multipath is a key part of testing multipath. It's doable, but cumbersome and has a steep learning curve. I want to create easy-to-understand manual recipes plus scripts that are both easy to understand / customize and deploy.

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.

Lately the necessary patches to get rudimentary support for the Mediatek chromebook with a mainline kernel got posted. There are some hacks and I'll work on some good solution to get graphics go, at least.

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.

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.

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).

meson[0], a replacement to autotools, is very popular nowadays. It's a lot faster than autotools as far as what I hear and see. Besides lots of GNOME projects has been ported to meson. As one of the maintainers of GNOME Logs[1], I need learn meson and try to port Logs to meson for faster building. *[0] http://mesonbuild.com/

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

I want to experiment with three things: * Blockchain

Are you interested in pairing? Are you wondering whether it is something that would help you and your team members in your current project? Would you like to try it out before you fully commit to such an extreme idea? Then this is your lucky day Sir/Madam! Within the Cloud Foundry project you are expected to pair pretty much every time you are working on something. In the BOSH OpenStack CPI team this isn't the exception, so I've been doing it for the past 15 months. I'd like to transfer some of that experience to you fellow SUSE colleague. We can discuss about the pros and cons that this agile methodology has. For example, there are many misconceptions on how to pair, for once, having the right hardware makes a huge difference. During Hack Week 16 you have the chance to test drive a dual-control workstation (see image) which I believe is one of the biggest differentiators to have a good experience when pairing full time.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

Goals: (Subject to change)

There is a couple of libraries available for asynchronous and non-blocking processing of HTTP requests (in Java) that can be used to avoid having threads waiting for responses in request intensive applications, for example: - Apache HttpAsyncClient

Use this hackweek to practice and learn more about Go.

Mottainai - Task/Job/Build Server for everyone!

Written in Golang. You can find the source code on GitHub and docs here.

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 idea is getting a general knowledge of how QT Linguist works, and help FET with some translations. FET is a timetable creator, that is available for openSUSE at https://en.opensuse.org/FET, and allows a user to create a timetable, usually for educational institutions, with a lot of different available constraints.

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.

First part is to support automated builds on git pushes also with gitlab, similar to what we do already with github.com. This means OBS would get notificated in a save way to refetch sources and start build on each commit. Second part is to support automated branching when a pull request gets created. This allows CI similar to travis on pull requests.

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.

Let's dust off our Amigas, hook up our mice and joysticks, and see what elegant software and hardware could do back in the 80s and 90s!

An initial prototype from the last hackweek can be found on YouTube Some may know the reality TV show shark tank where entrepreneurs pitch their startup ideas to get an investment. There is a German franchise of this show called "Höhle der Löwen".

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

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.

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

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.

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.

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.

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:

I am currently using odpdown for presentations (tl;dr: it lets you write your slides in Markdown and generates Libreoffice slides from that and a Libreoffice slide master (such as a corporate identity template)). It is currently not available in OpenSUSE so it needs to be packaged and submitted to Factory. If somebody other than me wants to take this on, please ping me. There used to be a package in the author's home project on OBS which has since vanished. I think I've still got a checkout somewhere...

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 :)

Right now portusctl is a tool which is embedded into the Portus source code. This was done out of simplicity and with the hope that we would share as much code as possible with Portus itself. However: - portusctl got bigger and bigger, and it starts to look like a good candidate for getting it in another repository.

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.

OpenFaaS - Functions as a Service Get familiar with one of the hottest topics for this year: https://www.openfaas.com/

Hackweek 18 Update

What Has Been Done During HackWeek 18

Laitos is an open source project written in go, it emphasizes simplicity of maintenance and delivers a complete suite of web, DNS, and mail servers to host a personal web server. Beyond the suite of servers, laitos software hooks into numerous API platforms, that altogether enable user access to Internet features (such as Facebook, Twitter, emails) via alternative communication infrastructures such as telephone (PSTN), SMS, and satellite terminals. For added fun, laitos software enables nostalgic computer systems (such as Windows 98 and DOS) to access modern web by rendering web sites on laitos server, and provides web page interactions via text commands and screenshots.

Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this. Possible additions: