While DDR4 memory has become quite popular, decode-dimms doesn't know about it and is not able to display any useful information for DDR4 memory modules. I would like decode-dimms to provide the same detailed information about DDR4 memory modules as it does for all older memory types.

The goal is to create a set of YAML files describing L3 supported products with all metadata we need to store there - and a JS presentation layer automatically showing this data in several forms, one of them will be a part of our L3 documentation. Technology: HandleBars.js or similar, plus some YAML technology

Deploy an openQA on my locally virtual machine and create 3 openQA test case for nautilus.

While it is important for package maintainers to track the upstream code base activities and backport significant patches in a timely manner, it could be a tedious work when there's hundreds of packages in a project (ahem, GNOME) to follow manually. So I wish to get mail notifications when new commits with certain keywords (e.g. SIG, {crash, hang}{s, ing, ed}, leak(age), CVE-, https://bugzilla.gnome.org/show_bug.cgi?id=*, etc, etc) come in.

CaaSP is designed to be used with containers based on SUSE micro OS, using Salt as the management tool. CaaSP2 GMC is available at the moment. I want to spend the hackweek 0x10 to play with it, figure out how CasSP integrate and work with Salt. My target is to understand the CasSP, like the advantage it take to k8s. How salt works in CasSP?

How to deploy container - Docker based on SUSE CaaS Platform.

Problem statement

Right now, we have different resources to pool videos. The goal of is to consolidate all video resources into a central place to make them easily searchable, and enable a youtube like experience, rather than a simple file list.

When doing the backport, I sometimes spend some time to check if the commit comes from a patch series and list all commits of a patch series. So I'd like to create a tool for doing this quickly.

YaST dumps quite information to its own log file (placed at /var/log/YaST2/y2log). That info is very useful to understand and discover what is happening when an issue appears. All YaST modules write into this log file, and the brand new yast2-storage-ng is not an exception. Some improvements are necessary regarding to the logging of this new module: * Libstorage-ng is the C++ library powering the rewrite of the YaST storage stack. For using libstorage-ng from yast2-storage-ng in a more Ruby-like way, we created a wrapper that provides several features like automatic downcasting. But the current downcasting mechanism used by the wrapper causes libstorage-ng to introduce a lot of noise in the YaST logs. It would be nice to reduce that noise.

SLE Engineering have a large flatscreen in the shared space just outside of Thorsten Kukuk and Stefan Behlert's office It runs Windows

The DriConf-Project inside of MESA has seen its latest update in 2006 and is implemented with GTK+ 2. https://dri.freedesktop.org/wiki/DriConf/

We got a couple of GSoC projects around Jangouts this year: - https://code-master5.github.io/Aug-22-2017

Problem statement

Once a kernel is built, a developer/janitor may want to boot the kernel for various reasons, such as performing simple boot test or running tests and workloads from user space or simply playing around in a shell. However, an easy to use and a descriptive tool to perform those tasks doesn't exist to our knowledge.

Look at this beauty: https://github.com/crowbar/crowbar-core/blob/master/crowbar_framework/app/models/service_object.rb#L941 Nice uh? Its a 500 lines methods that its distinctly separated into 4 different pieces internally that make 4 very distinct phases inside.

In our team, we currently manually deploy our Terraform code (namely, the SUSE Registry at registry.suse.com) from our own PCs. This is error prone, as it would be very easy to override something by mistake. I want to create the appropriate .gitlab-ci.yml file that will:

Once upon a time there was a bot

@mudler Created devbot that was helping the qa-tools party.