motivation

jenkins is a great CI system (continuous integration) with a plethora of plugins available. SUSE QA uses openQA extensively as it excels in distribution and product testing - not only image comparison (common misconception ;-) ). How about combining both in using jenkins with plugins to act as a UI for openQA?

motivation

The one mobile messaging service that shall not be named destroyed the world of "unified communication" by constructing a walled garden in recent years although there was a bright outlook with XMPP/jabber in before bundling all communication by providing an open standard and especially transports. I would like to revisit the state in 2017 and combine my text chat based communication needs from different end devices, namely my work notebook and my private smartphone.

``` ‎zypper ar -f http://dist.suse.de/install/SLP/SUSE-Manager-Server-3.1-GM/x86_64/DVD1/ suma3.1

need to learn more about containers

motivation

I like light weight presentation frameworks based on plain text files. There are quite some frameworks using the browser for presenting but many require a full blown web server. remark seems to be about the lightest I could find. I could make actual use of it when there would be openSUSE(/SUSE) branding.

motivation

Lots of crucial steps in the SUSE/openSUSE product build workflow are not known or not even accessible by many people but hidden as "custom scripts" on "some machine" in the worst cases. Nowadays infrastructure and build pipelines should be written as code, e.g. in git repos, with UI frontends to show the always current state of what is going on, what needs to be done to release products, where are problems. The least we can do is learn a bit more in this direction.

motivation

Many people ask how to start with openQA, ask "can you run these two lines in bash in an openQA" test and some shun the effort to try out openQA because it is "too big".

motivation

As an openQA contributor I could learn from openSUSE release managers how the overall process can be improved.

motivation

Test automation can be fun and openQA is good at it but it has limitations. This project is meant to find out where the limits are for applications with lots of things moving on the screen, e.g. a game. Completely unrelated, web based tools become the norm for many users, e.g. when working from a chromebook or similar environments. The idea here is to try to use only web based tools and not force users to use a terminal which can be frightening :) As a third requirement: Some people are not feeling comfortable using openQA "because tests are written in Perl". This is not necessarily true because tests are rather written using a simplistic test API and only a small subset of Perl knowledge is necessary, however, we still want to support other entry points so there is Python support added in https://github.com/os-autoinst/os-autoinst/pull/1558 . To find out what this new way is capable of this project should use only that Python support and find out any restrictions.

Motivation

When automating tasks often the requirement comes up to retry commands, for example when network connections are involved and commands do not return successfully immediately or if resources are temporarily not available. Sometimes a simple for-loop in bash is sufficient. Sometimes it is necessary to use additional waiting between retries, sometimes timeouts are desired. Getting all those combinations right can be tedious and error-prone so a generic "retry" command should be available in usual environments so we should provide a retry command to openSUSE distributions.

Motivation

The PostgreSQL database implementation is an integral part of many important software stacks, most importantly for me openQA. I learned database "by doing" but never properly. Given that we recently had (again) an incident related to specific details of how a database behaves under load maybe it's time to learn more about PostgreSQL.

Motivation

Many projects rely heavily on CI jobs, e.g. based on github actions. We already had ideas for tight integration of openQA into such workflows for years, e.g. in https://progress.opensuse.org/issues/48641

Motivation

The openQA test database, based on PostgreSQL, has a lot of potential to be able to answer various questions but often we do not know how to put those questions into the right SQL queries so let's harness the power of artificial intelligence to go wild in this direction :)

Motivation

I already have photovoltaics installed on the roof of my house. For years I was looking into home energy storage solutions but commercial offers are too expensive to provide a positive RoI so it is necessary to atleast assemble some parts by hand. I don't feel confident to build individual battery packs together and run multiple kWh in my house for years so I am going with "mid-level components", i.e. commercial off the shelf battery systems and power inverter.