Since I'm already working on a work-related project (https://hackweek.suse.com/14/projects/1388), I decided to also spend some time improving some of my toolbox. This includes configurations, scripts, pet projects and so on. I don't expect anyone to collaborate on this, but if someone is interested to know which scripts, programs and such I'm going to touch, feel free to ping me.

During the last CSM workshop I started to refactor zypper-docker in a way that: - The CLI code and the "library" part got split.

Distributed teams, cultural differences, expectations and habits are a natural enemy of vibrant, productive meetings (yes, meetings can be productive!). In this project I'd like to work on a different format and targeted exercises to provide ideas and a resource library to anyone interested in spicing up stale meetings. I am looking for your ideas, problems and examples - Feel free to join!

Sometimes it is hard to promote our project at conferences and events. During this hackweek I'd like to prototype a papercraft for promoting Portus at the upcoming containercon.

There are vastly different syntaxes being used by Linux softwares nowadays - Apache, Bind, NTP, Postfix, just to name a few. It is a very tedious task to implement comprehensive parser for every single configuration file, and even more difficult to produce configuration text (file content) from parsed syntax tree. The project tackles those difficulties by presenting an implementation of a universal parser that is capable of:

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.

Did you know that more that 60% of the food we produce it's thrown away? Why create pollution? Why spend out time to create something that in the end get wasted?

DAPS is the tool used by the SUSE documentation team to generate HTML, ePUB, PDF, ... output of the SUSE manuals from DocBook XML sources. It uses the suse-xsl-stylesheets for this purpose. Currently three different suse-xsl-stylesheet brands exist: SUSE, DAPS, openSUSE. Branding is done by adjusting the xsl-stylesheets directly. It would be desirable to be able to easily change the branding, e.g. via a simple config file in the style of /etc/sysconfig files, since most people cannot hack XSLT. This is also the number one enhancement request we get from DAPS users outside of SUSE.