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.