Laitos is an open source project written in go, it emphasizes simplicity of maintenance and delivers a complete suite of web, DNS, and mail servers to host a personal web server. Beyond the suite of servers, laitos software hooks into numerous API platforms, that altogether enable user access to Internet features (such as Facebook, Twitter, emails) via alternative communication infrastructures such as telephone (PSTN), SMS, and satellite terminals. For added fun, laitos software enables nostalgic computer systems (such as Windows 98 and DOS) to access modern web by rendering web sites on laitos server, and provides web page interactions via text commands and screenshots.

Quite a big part of openQA is testing the installation of SUSE products. All of them are installed by YaST. So a big quantity of problems found during openQA testruns are YaST problems. To find out what has gone wrong during installation YaST developers need to download the tarball containing the logs, unpack it and find the y2log among many other log files. That makes it quite complicated to just have a quick view on a problem.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

Goals: (Subject to change)

Many of the Uyuni / SUSE Manager web UIs are still based on the no longer maintained Struts framework (version 1.2!) and implemented as JSP pages, while we added newer features based on the Spark framework and React. For me there is a vision of using only one technology stack (especially just one web framework, frontend framework and template engine) eventually, so it is about time to get rid of the old stack. While this is surely a huge effort, why not start with a new login page and then go from there rewriting other pages one by one? Things to look at in particular:

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

code:

For years we have been discussing the idea to modularize SUSE Manager. This would enable developers to create their own extensions to SUSE Manager without needing to touch the core repository. There are several frameworks that could be helping in that direction. The goal here is to create a Proof of Concept with the virtualization features moved into an add-on.

Idea is to write FF plugin which would process raw autoinst log and display it in more readable form .

Project Description

Do you need to record podcasts or interviews remotely?

Project Description

I want for long time to get my hands dirty with go and webassembly. we have (openqa-mon)[https://github.com/grisu48/openqa-mon] which is a monitoring tool for OpenQA.

Project Description

Chimera is a Kubernetes policy engine. Its policies are WebAssembly modules, that can be published on regular OCI registries (same place where container images are pushed).

Project Description

Uyuni recently made the switch from Javascript to Typescript. Alas, the team has a very mixed bag of experience with the technology and we could use a way to get everyone up to speed quickly.

Project Description

csbot is a hubot based bot connected to our production RocketChat instance. Most of the functionality in csbot is focused on fun with some scheduling tools available as well. Expanding csbot to have new features will be a fun way to do some creative Javascript coding and see the changes as they land (csbot has a CI/CD pipeline that pushes changes live as they merge!).

Project Description

This Hack Week i want to figure out how to best use Playwright to test Mojolicious applications like openQA in unit tests. Playwright is a (mostly better) alternative to Selenium for browser automation. I'd like to find a way to write entire unit tests in JavaScript, and have those run right next to existing Perl tests with the same test runner using Node Tap and the Test Anything Protocol.

This is a side project I started a while ago. The idea is to implement a tagging engine with some "advanced" features for browser bookmarks. I have many ideas for possible features, but the most basic are inclusion and exclusion relations between tags. For re-finding a given bookmark, I want to implement a TagTree-like structure, to replace the strict hierarchy of folders. This basically defines the MVP for this project.

Project Description

In January, we announced the D-Installer project, an attempt to build a web-based installer on top of YaST and Cockpit. Since then, the codebase has grown significantly, especially the JavaScript part.