reveal.js is a modern & lightweight HTML5/js-based presentation framework – much smarter than LibreOffice Impress can ever be (for a software developer). Richard Brown was so kind to create a proper LibreOffice presentation template for openSUSE and I would like to bring that design to reveal.js so next time I do a presentation I can happily use reveal.js while keeping up the openSUSE flag. :-)

A few months ago, I started thinking "it cannot be that hard to model my house using some CAD software". And of course I miserably failed.

Simplify, modernize, and accelerate the process and tools for reviewing YES submissions from partners. Hopeful goals to accomplish:

openSUSE Leap 15.2 is currently under development and it will be released soon. We would like to bring Kubernetes support for it and offer kubeadm deployment on it. As Kubernetes cluster container images we can use images from kubic project.

openSUSE code

Description

I had presented the "Wicked Network Manager" talk at openSUSE Asia summit @Beijing. I would like to keep studying the topic continuously. Getting involve the source code and study the operating style and components. I also met some problem after discussing and testing issues while my research , I want to keep it as a record and writing the technical document on wiki too.

The Idea

Since some time I am interested in getting better at C++ and learn more about Qt framework. Since I learn best with having a project/goal I came up with this:

There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test.

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

Learning design model can help to produce high quality codes, which will benefit our products.

Bisection is a well known method of localizing which commit caused a regression in a code repository. git-bisect is a particularly used tool for this problem in git repositories. However it is often the case that the failure is probabilistic in nature - either because we don't have a reliable reproducer of the failure and thus not reproducing a problem on a particular commit does not mean the problem is not still present there, or because of inherent variability of e.g. performance regressions. Bisection for such failures is problematic as it takes only one false result for the bisection to end up in an unrelated part of code history. So in these cases we usually have to heavily extend runtime of a reproducer or do multiple test runs or multiple bisection runs to minimize a chance of error.

Project Description

Description

Over lunch the machinery team was talking about telepresence and mobile solutions and I came up with the idea of abusing a cheap wifi controlled toy tank as base for such a project.

The goal is to jump forward with this fate: https://fate.suse.com/319319

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.

BPF Compiler Collection (BCC) https://github.com/iovisor/bcc

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

In-depth understanding of how ptrace works; get the implementation mechanism of ptrace;

Working with some of the Linux modding communities I am aiming to make the ultimate guide / knowledge base for modifying the look and feel of your Linux install.

Bug reports can be a great source of information, but usually finding the information requires extensive work in reading through all of the discussions and understanding the details about it.

Description

Implement new features in openqa-trigger-from-obs to make xml more flexible.

Project Description

Description

MIDI supports volume control, so why not use that for ALSA?

Dive into VLC and fix mixing video and audio sources together with multiple transcoding and multiple outputs.

The trend of adopting Web technology in Desktop is ubiquitous these days. Both as a learning project and a proof of concept, we'd like to

Overview

With the recent explosion of product extensions, modules, bases, the decomposition of monolithic base products into modules, and the amount of churn in product composition between releases, the task of calculating product dependencies and migrations between products has approached the complexity of package management. We have a state of the art tool for solving package dependencies, so why not apply it to the new domain?

Minnowboard is the platform for UEFI development and supports UEFI capsule update since 0.99, and we are supposed to be able to test the feature with fwupd. However, there is no capsule file in fwupd.org or the official firmware download site. Besides, the Minnowboard firmware source in the current edk2/edk2-platforms git couldn't build due to the recent change of directories. My goal is to rebase the Minnowboard build system to the current git master and create a working up-to-date firmware. Signing the firmware properly would be a plus so that we can apply a private repo in fwupd.org for the development or QA testing.

As per the title I am aiming to investigate a much nicer conky default, I have a short list, but it depends on asking people nicely to license there work, if I have to create something from scratch it probably won't happen this hackweek.

Description

Recently, I became interested in NFS and want to learn more about it by reading related RFC files. However, there seem to be quite a lot of them. The goal is to glance at them and get a basic feel for the differences between each version.

Description

This project will focus mostly on getting to know the Clojure and ClojureScript ecosystem.

    jikos:~ # tc qdisc show

Every packager encounters boring manual tasks every once in a while and these tasks can most probably be automated to some extent. During Hackweek I aim to try and identify such cases in various packagers' workflow and consider creating a tool that would make these tasks easier. Also, I would like to find out whether there is a demand for such tool. In that case, this Hackweek project will turn into a long-term task I plan to keep working on.