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.

GNOME Software supports distribution upgrade, that only requires a few clicks for upgrading your system. But it's not integrated into Leap. So this is that I plan to do this Hack Week.

Involved components

Zero-ish downtime deploy on da cheap!

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

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.

Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development. In order to modernize the Mash workflow I plan to spend the week digging into a plethora of tools to first learn then build out a new workflow. The goal is to simplify deployment by choosing tools that provide consistency, modularity and repeatability. By leveraging the best tools available we can harden the code and accelerate the release cycle.

Future of tools supporting editors in dealing with particular languages is in my opinion in the LSP protocol. Therefore I look with a bit of worry on the fact that there is no good LSP server based on the top of rope. python-language-server uses it a bit internally, the Microsoft Language Server for Python is in C#, so it is completely something different. The goal of this project is to write a very simple nucleus of the LSP server based solely on rope for the language analysis and actions, which would be at least able to do “jump to the definition of a symbol”.

Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients.

There are various home assistant solutions out there but all of them transfer your voice to some server for processing. This is a no-go for sane people although the technology is interesting and could be useful. There are various open source tools out there to achieve the same result but there is no turn key open source self hosted solution. The goal of this project is to implement a way to have a home assistant running locally - ideally with one command. The project that is closer to the desired result is Mycroft (https://mycroft.ai/). It is very easy to run the client side components using one docker command but their backend is running remotely. All the tools they use though are open source so it only needs one to do the work and package them in a nice little docker-compose file (https://mycroft-ai.gitbook.io/docs/about-mycroft-ai/faq#can-mycroft-run-completely-offline-can-i-self-host-everything).

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.

define data types to collect informations about cameras and lenses to have a shared data store for lensfun and photo editors. Current state:

Libyui REST API

In the previous hack week project I was focused on implementing a REST API for testing the YaST modules.

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

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.

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

Overview

uMEC (aka MicroMEC, or Micro-MEC) is a project under the Akraino Edge umbrella. SUSE joined in 2019 and together with partners we managed to create the 1st prototype infrastructure.

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 is using OBS as a build system and openQA for automated testing purposes. The goal of the study is to find out the strengths and weaknesses of these systems and compare them to other open source alternatives in a structured way.

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.

The Maintenance Coordination, Security and Quality Assurance department documentation is organized and handled on Confluence and there are several pages and how-to available for new team members or other colleagues searching for more information. The processes and workflow documentation is a key asset for on-boarding quickly new employees and for improving existing workflows.

As per the title I am aiming to investigate a much nicer conky default, I have a short list, but it depends on asking people nicely to license there work, if I have to create something from scratch it probably won't happen this hackweek. Now that themes such as Polycore are licensed so they are useable the aim is to build from there.

Working with some of the Linux modding communities I am aiming to make the ultimate guide / knowledge base for modifying the look and feel of your Linux install. The scope of this hackweek project is to get the initial framework set up using Jekyll with some basic content added. Further content will be added in the future.

openSUSE Leap 15.2 is currently under development and it will be released soon. We would like to bring Kubernetes support for it and offer kubeadm deployment on it. As Kubernetes cluster container images we can use images from kubic project.

I plan to summary exist knowledge in filesystem part during hackweek. And learn some more feature about btrfs/xfs/ext4. The motivation is to speed up test result review in the future.

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

I want to study the knowledge of openQA I will read the online documents and do some experiment in virtal-machine.