During Hack Week 7 I worked on an archive of Qt-based libraries. The goal was to easily make all available Qt libraries accessible to developers. Think CPAN for Qt. So I hacked on a web site and a command line client.

Description

A web frontend for the mirrors in the mirrorbrain database to allow the mirror admins to manage their entries themself.

• jruby
• ruboto homepage

Initial idea to build a tool to help rubygems community to rotate maintainers for abandoned projects.

Links:

Machinery supports inspection of SLES11 and SLES12 systems right now.

In order to build a community around crowbar, our cloud installer, we need to get this running on openSUSE as well. So let's find some time to move the packaging of crowbar from the ibs to the obs!

The new SUSE Floor is nearly done. The core functionality is already implemented and only some basic features are left.

Yast team has a great experience in automating tasks that can be done by machines in order to save time that can be used better. We usually use Jenkins for running these jobs.

The idea is simple. Dice is a light weight build service for KIWI images with full control over the build power by the user.

Create a system to allow a community to add contextual information to "open books". Think wikipedia for books

The goal of Project MySelf is to build a system to collect data about yourself in a safe and private way, so that you control your data and you can decide what happens with it.

Micro-service for - making a report

Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often".

Machinery [1] supports the inspection of os, packages, patterns, repositories, users, groups, services, config-files, changed-managed-files, unmanaged-files.

or: Static Analysis of nil Values in Ruby Code used in YaST.

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table

Reporting demands on SCC are increasing. Rather than creating hand crafted 'one-shot' reports in response to every request, this project aims to discover whether there is a better way.

Read RoR docs and continue the TODO list from https://events.opensuse.org/conference/oSC16/program/proposal/894 + issues from https://github.com/ChrisBr/rails101/issues as a practice.

The goal of this project is to write a proof of concept of a new philosophy for yast2-storage-ng. Instead of just extending the API offered by libstorage-ng, the idea is wrap libstorage-ng so the Ruby code using yast2-storage-ng does not have direct visibility (unless explicitly desired) on the libstorage-ng classes and methods.

Perl-apparmor is obsolete in the apparmor community. No one is maintaining it. However, opensuse has to keep it to interact with yast, which is the main consumer of perl-apparmor. Getting rid of perl-apparmor would mean:

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.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

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

The subject says it. Learning about DHT seems like a fun project.

I just recently started a new project which is meant to be a wrapper for OBS's API. The library is written in Ruby.

People are interested in Linux on Windows via WSL, especially given the new fully virtualized Linux kernel in WSL 2. It's interesting to know whether registered SUSE installations might be running in WSL as opposed to other Microsoft virtualization platforms, but the current approach taken by SUSEConnect (the client for SUSE Customer Center) does not permit this.

Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients.

Project Description

Description

Project Description

In this project I would like to extend the capabilities of the SLE Release Management Container. This container is used by some colleagues in the SLE Release Management team to have access to osc and other Release Management critical commands inside a container environment. This includes the beta-emails project to send our beta announcements.

Description