sumaform is a set of terraform modules to deploy SUSE Manager installations originated in Hackweek 14. One year later, it is used virtually by all SUSE Manager developers daily and in our automated test suites - some consultants and SEs also use it.

Turn an android tablet into a drawing tablet

At the end of the project we should be able to use an android tablet as a drawing tablet in our Linux environment.

Farfalla, is a bot for analyze cucumber failures on the fly. https://github.com/MalloZup/Farfalla

Have some knowledge on Dockers , but now taking the next step in understanding and expanding my skill set in containers and kubernetes. Goals for the Hackathon

I just want to learn how OpenCV works. And having a portable version would be great. - learn how to install SLES on RPi

Learn about developing a YaST plugin by creating a plugin to manage SSH Tunnels. Creating SSH port tunnels along with corresponding iptables rules is a useful technique for being able to access virtual machines on a remote host that only visible on a private network. Managing and maintaining these connections via scripts and tmux sesssions is less desirable than doing it through a nice UI like YaST. Note that the CLI tool https://www.npmjs.com/package/ssh-tunnel-manager has some nice ideas for managing groups and profiles that may be useful.

I recently got Jeedom working on SLES for Raspberry Pi. However, I'ld love to play more with it like controlling my window shutters. This hackweek could also be an occasion to get as much as possible of the jeedom plugins to work on SLES and openSUSE.

To implement OTR function on IRC client, to make chatting private. pure-python-otr (potr) has lack of maintenance for a long time and been considered as "potentially insecure". So I will call libotr5 directly with C.

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

BPF Compiler Collection (BCC) https://github.com/iovisor/bcc

This is an idea that's been kicking around for a while... maybe it's finally time to "make it so." Minimally:

I am HA developer, don't have any experience on machine leaning field. Recent years, many topics like "Data Analysis, Data Mining, Data Science, Machine Learning, and Big Data, etc... (I don't forget AI, but in not this time)" become more and more popular and seems interesting to me. I also want to know how high availability function implemented in some distributed system for the core part. Google TensorFlow1.0 just released, it is the time to play on it.

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 project is about hacking and pushing further an engine called BPAEngine written in plymouth that enable people to develop better boot screens without much effort. Having those new boot screens in our distributions would be great. Plymouth is a "basic" scripting language for developing boot screens (See some Fedora examples running). Our openSUSE distributions have their own plymouth themes packaged on the branding-openSUSE package. And in my opinion they are very basic..., just a dot moving in 3 positions with the nice background and a logo.

This project is about fixing this known Jangouts issue that is reported over and over, since many user experiencing problem with the outgoing WebRTC traffic or with camera authorization can "lurk" what happens in the room without being noticed. Copy&Paste from the last comment there: It's true there is a lot of room for improvements to raise the awareness about "lurkers". For example, we could compare the number of people subscribed to your stream and the number of publishers. If numbers do not match, there is somebody listening but not being displayed. That's something we could show in the UI.

Packages added by the dependency solver in order to resolve a user's request, are marked as having been automatically installed. They may later be removed, if no more manually installed packages depend on them (e.g. by zypper remove --clean-deps). However things may go haywire. Automatically installed packages may turn out to be useful, and you may want to exclude them from any automatic cleanup. And vice versa.