Having gotten access to some SMR prototypes it should be possible to tweak btrfs to run natively on those devices. Using SSD mode helps a lot, but there is still some work to be done. So this will be a good chance to learn something about the inner details of btrfs and see if I can get it to run on SMR drives.

SUSE Manager has the possibility to add custom channels using the GUI. Use cases are:

It's been a little while since I last needed to do some binary reverse engineering, so I want to up my game. Goals

Project Description

Now in Public Cloud and Containers QE team we are using https://github.com/BillAnastasiadis/qe-c-backlog-assistant. But we want to go far from here to be capable of provide more information and analysis

Project Description

Network management is very important for cloud and Edge. CNF(cloud-native network function) is next-generation VNF.

terraform-provider-libvirt supports CoreOS ignition file/content, which end rendered as kernel command line options (the provider does some nice stuff like allowing you to pass the json content and it will take care of putting it into a temporary file). The idea is to:

Learn opencv and Face recognition related knowledge to build Face recognition project on raspberry 4b

Project Description

openSUSE lacks useable cross-compilers to glibc systems. This is the attempt to provide those, most important a cross-compiler for arm/aarch64.

Project Description

Device for connecting an electric guitar or bass to a computer via USB-C. It is basically just a glorified A/D converter, although with a twist. It can emulate proprietary commercial devices for use with applications such as Rocksmith. The name comes from the official device for Rocksmith, which is named Realtone Cable.

The salt-toaster (https://github.com/openSUSE/salt-toaster) is a tool created and developed by SUSE employees that we've been using for testing Salt since few years ago. This tool uses pytest in combination with Docker containers to allow testing the multiple versions of the Salt codebase and as well as Salt packages across multiple distributions.

Salt is moving towards a plugable architecture using POP and Idem. This project is about experimenting with those new concepts by applying them to a real life case: the virt execution and state modules. The goals of this project are:

CephFS is awesome, but without a VPN it's not safe to be routed over the internet, and it lacks client support on many platforms. The Linux Kernel Library allows for the linux kernel to be built as a cross-platform user-space library and integrated into a regular Android, Windows, macOS, etc. application. This project combines CephFS, LKL and wireguard, and sprinkles some io-uring on top. My objectives are:

In https://github.com/SUSE-Cloud/automation/ we already have mkcloud, which can setup a whole SUSE Cloud on a single host for testing. However, it would be cool, if (instead of a single machine) we could use cloud.suse.de with its capability to add extra networks as requested. This can be pretty easy, as much of the mkcloud code is about making libvirt do the right thing

Everybody is talking about (and with) ChatGPT. I tried it and was impressed by how well the language model behaves and finally how real and humanly it appears, despite the obvious nonsense that it outputs. I was wondering how machine learning practically works and how to build a neural network.

Project Description

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.

Motivation

Running async actions in SUSE Manager lacks a user-friendly feedback. For instance, running a salt highstate on a system:

DAPS (https://build.opensuse.org/package/show/Documentation:Tools/daps) is a tool we use in the documentation team to create/validate/export/... docbook documents. It's currently available for SUSE and openSUSE systems, and I believe that packaging it for Debian GNU Linux would help both the DAPS and the Linux community (and me myself as I'm using Debian at home as well :-)

I would like to learn Salt by converting ansible scripts to salt states. Current ansible scripts do some QA tasks on cloud nodes, so i thought it would be a good idea to convert them to salt after reading salt tutorial.

DAPS is the tool used by the SUSE documentation team to generate HTML, ePUB, PDF, ... output of the SUSE manuals from DocBook XML sources. It uses the suse-xsl-stylesheets for this purpose. Currently three different suse-xsl-stylesheet brands exist: SUSE, DAPS, openSUSE. Branding is done by adjusting the xsl-stylesheets directly. It would be desirable to be able to easily change the branding, e.g. via a simple config file in the style of /etc/sysconfig files, since most people cannot hack XSLT. This is also the number one enhancement request we get from DAPS users outside of SUSE.

Currently the Open Container Initiative doesn't specify a distribution protocol or system, and the current "standard" format is the Docker registry protocol. Aside from technical reservations with Docker registry, it is also not an OCI-compliant system and will require a lot of work to integrate it into all of the openSUSE/SUSE tooling. So, a very insane idea I came up with is to convert OCI images to RPMs and then distribute them as simple RPMs. The idea would be to use capabilities (Provides: oci(...)) to implement the different names of images and then also the dependency graph of blobs (which would naturally be de-duplicated).

I want to write a new rubocop cop that verifies that a schema.rb file in a Rails project, references a valid migration.

Connect is the "social network" of the openSUSE community. While this might not sound so important, the problem is that the tool is used for membership management and all the other "administrative" stuff for the openSUSE community, which makes it a very important tool. The bad news is that - since years(!) - there is no-one actively maintaining the application. While the openSUSE Heroes keep the basic infrastructure up and running, they are not responsible for the application itself. Following the standard policy for such services, this would mean that connect has to be shut down immediately. But the openSUSE board heavily depends on this tool and asks every time when it comes to "shut it down" - to not do it.

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.

Pi Security

I've ordered two security modules that can be used with the Raspberry Pi. One simple LetsTrust TPM with the Infineon Optiga SLB 9670 chip and a Zymbit Zymkey 4i Security Module.

With the approach of kernel 5.6 SGI Octanes are supported with builtin IO components. What's missing for a graphics workstation is a driver for the graphics card. There is already a not upstreamed framebuffer driver for Impact graphic cards. Since there will be no new framebuffer driver accepted upstream, the goal of this project is to convert the existing frame buffer driver to a DRM driver and make it ready to be sent upstream.

We kinda need more flexible PXE in Prague office, UEFI would also not hurt - so lets check what we can do to make it better. EDIT (ggherdovich):

Currently, opensuse-quickstart sets up a one-machine Cloud based on OpenStack, either with KVM or virtualisation. In order for bootstrapping further hosts, it would be much easier to set up only a bare-metal cloud on one machine, and PXE boot a 2nd machine via OpenStack Nova/Ironic.

Project Description

GNU Make has been a popular software tool used for automating simple build, test, and general source code management tasks for a long time. You'll find Makefiles in many software repositories – we use it on many projects as SUSE! For the most part, Make does its job, but often what people want to do with it is not exactly what it was designed for. Specifically, Make users often use Makefiles as a means a means of building out a set of commands that can be applied to their repository. But therein lies the problem: Make was not designed to build quick command line utilities at all, and it quickly becomes a nightmare as soon as the user wants to include arguments or options in their commands. The common alternative is simply to build out a tangled mess of build scripts.

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

Option page

Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this. Possible additions:

Checking the status of your Github pull requests is annoying. You have to lose focus from your current work (ie. hacking) and open your browser, type the repo URL in the address bar, click on the Pull Requests page, and look at the status of your PR. This extension makes that process a breeze! By clicking on the Octocat in the status area, you'll have direct access to your favorite repos, and an overview of their PRs' build statuses. Clicking on a certain PR will take you directly to that PR's page.

My car has it, nowadays every smartphone has it. But what's actually the math behind GPS (GLONASS) technique?

Project Description

One of the projects that the EOS open source community has been working on for some years now is the User Story. An open roadmap and feature request tool for open source. https://userstory.eosdesignsystem.com/

I use the KDevelop IDE whenever I can. At SUSE mostly for reading code while debugging some bug. My plan is to create plugin that will show extra information inline with the code to make it easier to explore foreign code. Examples include showing names of function parameters at call site, elided types of variables (e.g. C++ auto, lambda parameters), comments next to closing brackets etc.