Have a play with SUSE CAP on AWS during this hackweek.

The plan is to start working towards a rewrite of xdg-utils in python, focusing on the really bad bits such as dealing with desktop files and mime handling. In this hackweek, I want to split python-xdg into multiple libraries such as python-mime and python-desktop file and prepare them to be used in helper binaries to handle some of the more complex tasks currently done in shell.

DevOps teams face double sided challenges: development tasks should be planable and maintenance tasks should maintain their flow to provide maximum value through the queue. Build a prototype JIRA project to help them organize their workload with a Scrum board for their development tasks and a Kanban board for their maintenance work, all fed from a common backlog.

SUSE CaaS Platform is a Cloud-Native Computing Foundation (CNCF) certified Kubernetes distribution. - Family with SUSE CaaS Platform

I recently bought a Lioncast LK200 RGB keyboard which is a nice piece of hardware and has exactly the look and feel I want. All basic functions work well under Linux. Unfortunately the manufacturer only provides user software to upload/download profiles and control the LEDs for Windows. The device can be configured and operates autonomously from any OS but color setup is a PITA and it's very easy to factory-reset, and lose all config. I approached them but Lioncast seems neither interested to support native Linux nor to provide protocol specs so one can implement it. I thought to take this as an example to learn about reading and reverse-engineering USB device software.

Finglonger is an internal tool used by the SUSE Manager team intended to make the life of the Round Robin Bug Guy easier. It was originally written by @fkobzik in Clojure. This is an attempt to learn some Go by reimplementing Finglonger.

****The motivation is create a open source solution, base on this business astronomy products: AZWO Asiair

Very often people find themselves wanting to store secrets in a way that either they can recover even if (for instance) their house burns down, or allow friends and family to recover if they pass away. Existing solutions to this problem are: * Too complicated to use for ordinary people.

https://gitlab.suse.de/l3ms/RES-weather/ needs some improvements, e.g. manual generation of statistics and reports.

At present it is our practice to "vendor" all dependencies for a Golang package. This has the advantage that everything is in one nice package and self contained but it has the disadvantage that dependencies are hidden and therefore security issues may slip through the cracks. The idea is to investigate and create automation "go2rpm" that generates a spec file with the necessary "BuildRequires:" such that the dependencies can be broken into golang- packages and we get rid of the implicit dependency inclusion via "vendor". The potential problem is scale, with some golang applications having thousands of dependencies.

Recently, ConnMan got support for iwd and WireGuard. The current support is only a starting point and it needs some more changes in the core code base to support the cool features:

I would like to learn and play with RL/ML and Go ( gorgonia for example). The lack of Reinforcement Learning library in Golang makes me very sad, so I wanted to implement a RL algorithm and alongside create a small library for RL and go in general. On the other hand, I would like also to expand and add features on a project that I'm working on: https://github.com/mudler/luet . It's a package manager based on containers, focused on cloud/OTA-alike update delivery. It would be nice to combine the two ideas, for e.g. to achieve one feature.

There are a number of items related to doing Virtualization CI and testing which I have a hard time getting to during my day job. I'll take Hackweek as an opportunity to get at least a little out of my normal space and improve our methods. This mainly focuses on QEMU/KVM and some of the efforts and infrastructure I've already got in various states of development, or at least investigation. Part of this effort is to try to leverage what is available in this space upstream, and to focus on watching the state of CI as it exists upstream, not just in our shipping products.