A web frontend for the mirrors in the mirrorbrain database to allow the mirror admins to manage their entries themself. You might know MirrorBrain already: our download redirector and Torrent/Metalink generator used u.a. on download.opensuse.org. It's really a great tool that plays a hidden key role inside the openSUSE infrastructure.

Hamsta currently lacks a standardized network interface that would allow other systems accessing its capabilities. There is a custom network interface with text-parsing based protocol that is poorly documented and needs to be implemented on the client side to be usable. This interface does not use any standardized way of communication or library. This project suggests to add a standardized web service interface (let us call it API) to Hamsta. Expected attributes are following.

Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components: - RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)

In case any of the source files changed, openSUSE Build Service rebuilds the dependent packages regardless of whether that particular modification affects the dependency. This makes our resources footprint bigger (and the electrical power bills higher). It also affects users, because every new package build causes the package manager to include that package in the next update thus consuming network bandwidth and resources of users' computers.

Current OBS controls for package rebuild triggers

Displays your openQA instance status, the feature/behavior should had at least like the list below,

Option page

The webVTT standard (nearly the same as the older SRT subtitles) allows to add subtitles to a video. We could use this in openQA to show which keys were pressed at that point in the video, in which line of code we were or on what event we waited. This could make debugging easier and might be instructive to users, too.

openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal. But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?

This is an idea that's been kicking around for a while... maybe it's finally time to "make it so." Minimally:

I've been doing a terrible job of maintaining GNU Stow the last year, and there's quite a backlog of bugs, feature requests, support requests etc. So it's a good time to catch up on these.

A lot of openSUSE bugs are filed with plenty details but without a specific assignee so often many days are lost between filing and a developer seeing the report. Instead of training a neuronal network to do artificial intelligence, this project focuses on the integration of how we can make useful proposals of assignments. It will probably use perl regexps for the start.

The idea is to hack os-autoinst-distri-opensuse infrastucture and explore design patterns that can fit. The end point of this is to restructure the framework in such a way that the main-common.pm is more efficient, functional and readable.

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.

Project Description

yamltidy is a tidier/linter for YAML files. It's pretty new.