During Hack Week 7 I worked on an archive of Qt-based libraries. The goal was to easily make all available Qt libraries accessible to developers. Think CPAN for Qt. So I hacked on a web site and a command line client. There was a little bit of progress on the project since then, but with the upcoming KDE Frameworks 5 there will be quite a number of additional libraries available for Qt developers. This should be well represented in Inqlude as well. The coverage of Inqlude is also still not complete, and the tooling needs some improvement as well, especially regarding integration with distributions.

Use machine learning and natural language processing techniques to analyze the changes made in a project, and classify them in: * Small / unimportant fix

Yast team has a great experience in automating tasks that can be done by machines in order to save time that can be used better. We usually use Jenkins for running these jobs.

Why to use automation?

This is about porting the old KDE 3 based KDirstat to the latest Qt 5. KDirStat didn't use that much KDE infrastructure to begin with, and KDE seems to be more and more a moving target. Project repo and web site with more details:

kubeojo in 10 seconds-click-me to visualize-demo-link

code:

Rationale:

There is around in the clojure community (https://clojure.org/) a GitHub opensource organization which aims to maintain in a centralized manner some useful community libraries.

I'd like a way to have a device on my desk which lights up to indicate that I have something I should be paying attention to. Initially, I'd like this to be for Office365 calendar events and GitHub mentions, but ideally it should support arbitrary messages. The plan is to assign specific colors (ideally "patterns" consisting of a sequence of colors and time) to specific message types. I have a handful of raspberry Pi Zeroes, a couple of OLEDs, a strand of individually-addressable RGB LEDs, a power supply, and some misc electronics (like the 3.3-5v logic level shifter necessary for the 5v LED strand). I'm thinking Python is probably the way to go for the software. I'm hoping OpenSUSE actually works on the Pi zero. :D If not, there's an ESP32 with a built-in display and a few Pi 3s laying around barely used, maybe one of them will work.

Last hackweek filtra was created – a tool to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban. The collected metrics can then be visualized with Grafana. Currently there are two problems with filtra:

Zero-ish downtime deploy on da cheap!

This project aims to get a 0-ish downtime deployments (very easily achievable with Kubernetes) just using:

Project Description

multipath-tools is in urgent need of better CI, both unit tests and "real world" tests. We a very basic set of unit tests, but the coverage is miserable. Also, there's some minimal github workflow code, which could be improved a lot while I'm learning about github workflows.

Project Description

Legal reviews have been a quite painful part of our development process. The current situation in Factory waits for legaldb for a limited amount of time and simply proceeds further if the review is not "approved" within a few hours.

Project Description

Jobs in openQA are usually reviewed via the web UI. Inspecting os-autoinst logs requires significant insight into the inner workings. Tests run in a CI such as GitHub are thus not easy to debug.

Avahi Integration and Network Connection

Project Description