openSUSE Connect is almost forgotten tool used only for elections. It would be nice to update it, polish it a little bit, disable functions that nobody uses and fix those few that people would actually like to use.

Squeezeboxserver

Test the latest release of guesfs tools, and chech new p2v. Package it for openSUSE My branch

Recently I became a (not very proud) owner of Acer Aspire Switch 10E, a small notebook/tablet convertible based on Intel baytrail platform. Replacing preinstalled (32-bit!) Windows 8.1 with (64-bit) openSUSE proved more challenging than expected, mostly because the device is haunted by a 32-bit UEFI so that it took me a week to make it boot without an external USB flash disk. Even today, a lot of issues persist. As I do not want to waste a (partially) good hardware, I would like to make it as usable as possible. This is much less selfish than it sounds as there are many other devices based on Intel baytrail platform so that the effort is going to help their owners as well (if successful, that is).

openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore. Come up with ideas and a prototype of how manual testing could be guided, tracked, visualized for a rolling development distribution with volunteers testing.

make crowbar+openstack work on openSUSE Leap 42.2 part of this is setting up public CI. For that, we need to port mkcloud to work on Debian.

After an internal call for help to take over software.opensuse.org deployment, I spend some time studying the code in order to find out what would it mean to take it over. The main reason was a PR from the community that has not been merged, and deployment depending on internal SUSE employees.

Build a base image and template (both kiwi and Dockerfile) for openSUSE Leap 42.3 using the native OBS container building feature. Results/WIP will be available here:

Motivation: "Make Jangouts Great Again!!"

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

code:

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.

Video Recording of openSUSE Conference session which introduced the project

Core Project

There is always something to do if you run the infrastructure for such a big project like openSUSE.... Our Admin wiki currently lists over 80 machines - and while we already "salted" some of them, there is always room for improvement and room to learn something new just by making your hands dirty and diving into the administrator role for a machine.

Project Description

For quite some time I am providing a ResourceSpace container on Docker Hub. It is meanwhile pulled about 234K times but unfortunately still based on Ubuntu. Meanwhile I have updated the base to Ubuntu 20.04, but I would like to move it to openSUSE instead. With ResourceSpace 9.5 coming out soon I see a possibility of introducing this switch. Enno Gotthold also did a great job of packaging ResourceSpace on OBS, so this could be used as a starting point for the container.

Project Description

Create a toolset for installing (openSUSE Tumbleweed) on any android-based device (using fastboot)

I'm running a simple home mirror, but I managed to get into a situation where I have to use a bunch of custom excludes. I think we should be able to offer what people want nowadays.\

Let's do what we can to get https://github.com/openSUSE/fuel-ignition running as ignite.opensuse.org respectively ignite-stage.opensuse.org

Project Description

Project Description

We are currently at GHC-9.4.x, which a bit old. So I'd like to take a shot at the latest version of the compiler, GHC-9.6.x. This is gonna be interesting because the new version requires major updates to all kinds of libraries and base packages, which typically means patching lots of packages to make them build again. A significant part of the development effort will be live-streamed on Twitch so that others can collaborate easily.