Overview

With the recent explosion of product extensions, modules, bases, the decomposition of monolithic base products into modules, and the amount of churn in product composition between releases, the task of calculating product dependencies and migrations between products has approached the complexity of package management. We have a state of the art tool for solving package dependencies, so why not apply it to the new domain?

Minnowboard is the platform for UEFI development and supports UEFI capsule update since 0.99, and we are supposed to be able to test the feature with fwupd. However, there is no capsule file in fwupd.org or the official firmware download site. Besides, the Minnowboard firmware source in the current edk2/edk2-platforms git couldn't build due to the recent change of directories. My goal is to rebase the Minnowboard build system to the current git master and create a working up-to-date firmware. Signing the firmware properly would be a plus so that we can apply a private repo in fwupd.org for the development or QA testing.

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.

Description

Recently, I became interested in NFS and want to learn more about it by reading related RFC files. However, there seem to be quite a lot of them. The goal is to glance at them and get a basic feel for the differences between each version.

Description

This project will focus mostly on getting to know the Clojure and ClojureScript ecosystem.

    jikos:~ # tc qdisc show

Every packager encounters boring manual tasks every once in a while and these tasks can most probably be automated to some extent. During Hackweek I aim to try and identify such cases in various packagers' workflow and consider creating a tool that would make these tasks easier. Also, I would like to find out whether there is a demand for such tool. In that case, this Hackweek project will turn into a long-term task I plan to keep working on.

In the last hackweeks and my free time, I've been developing several tools to various degrees of completion. The purpose of this hackweek is to finish three of them, publish them on github and create openSUSE packages.

Try to use apache-rex framework while testing httpd modules.

Exactly what problem will this solve?

Description

There's already an app but code/features already in Syncthing Tray could be reused to create a nicer app with additional features like managing ignore patterns more easily. The additional UI code for the app could then in turn be re-used by other parts of Syncthing Tray, e.g. to implement further steps in the wizard as requested by some users. This way one "UI wrapper codebase" could serve GNU/Linux, Windows and Android (and in theory MacOS) at the same time which is kind of neat.

Description

Using Ollama you can easily run different LLM models in your local computer. This project is about exploring Ollama, testing different LLMs and try to fine tune them. Also, explore potential ways of integration with Uyuni.

Description

Project Description

The idea is to create and internally host a simple webpage with proper backend code allowing quicker and easier lookup for package maintainers and bug owners from OSC. Nothing fancy, just a page with search box and few radio button parameters to execute the lookup and display the results. Obviously it needs to fulfill security measures when it comes to the access to OSC on the service level and also user access rights to the search page itself (e.g. Okta). Currently the lookup can be done via terminal (which is OK), but there are security measures in place which makes the lookup difficult for some and granting an engineering VPN access just for the sake of this OSC lookup is a bit an overkill for people that do not need it for any other purpose.

Prototype