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.