Learn the inner workings of TCP as implemented in the Linux kernel. This will involve * reading textbooks and IETF docs

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA Topic 1:

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.

What's about an app that helps you with downloading openSUSE documentation? Does a free app for managing gettext files (.pot, .po) already exist?

For years we have been discussing the idea to modularize SUSE Manager. This would enable developers to create their own extensions to SUSE Manager without needing to touch the core repository. There are several frameworks that could be helping in that direction. The goal here is to create a Proof of Concept with the virtualization features moved into an add-on.

I want to create devel project for cryptocurrencies/mining tools/blockchain related stuff, fill it with packages and submit at least some of them to Tumbleweed. Lets go on as Standa took care of creating network:cryptocurrencies

The goal of openQA is "test as a QA engineer". But openQA has no ears - all we can test for are DTMF sounds. And even those are very bad. So my hackweek project is to do research on how to do proper sound verification. The keys are proper normalization of the volume and the sample rate.

Build Service needs an openid. Imagine following case:

Setup a patchew instance

patchew allows you to easily track patch series sent to a mailinglist and see the diff between the different series.

Tronsmart has a Rockchip rk3368 based set-top-box [1]. I want to use it as a arm64 based workstation running openSUSE.

Project Description

I recently used melange and apko to build a from scratch image. The result was a set of auditable and easy to use container and apk repository. The toolkit reduces the work need to make from scratch images with minimal work on the actual docker container(which can be quite painful if you've tried making a from scratch image on your own).

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

The situation of maintained ansible roles for boring server stuff like setting up a LEMP stack (Linux, nginx, mariadb, php) is dire and I would like to improve that. This project is about creating a handful of ansible roles with focus on * Fully supported in openSUSE (Leap and Tumbleweed)

The recent glibc 2.33 version recently available in Tumbleweed includes this change: ```

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

With rust 1.9 released, it should be possible to from now on bootstrap rustc from the previous version of rustc (so 1.10 can be built using 1.9 etc.). This means that it should now be possible to create a rustc package which no longer needs binary snapshots to build, meaning that we might even be able to submit rustc for inclusion in openSUSE Tumbleweed. This is the first goal.

Language Server Protocol (LSP for friends) is used in a number of code editors these days. There are implementations for various languages, but none for Salt States. The idea is to leverage Salt state module to parse edited files to provide completion of the state ids or paths.