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. But in fact it's a UI desaster that almost never works. So the goal of this hackweek project is to get rid of it - and instead build a real control from the webui into the backend allowing tests to be written on the fly including needle creation/updates. Easy as that.

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

Learning design model can help to produce high quality codes, which will benefit our products. I'll do it mainly by reading "Design Patterns: Elements of Reusable Object-Oriented Software".

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. The aim of the project is to implement stochastic bisection for git. I.e., a method that will count with the fact that test results at each point of code history have some error rate and provide points in code history to test to find commit in code history that is with high probability introducing the regression in the smallest possible number of tests. Then we can use this method for bisection of performance problems in our performance testing grid Marvin.

Project Description

Due previous hackweek (https://hackweek.opensuse.org/projects/test-mainline-kernel-on-an-older-qualcomm-soc-msm89xx-explore-mainline-kernel-qualcomm-mainlining) both msm8994 angler and msm8992 bullhead are booting and due other activity (including my work) both have working SD card, but that's just start. Add support for other functionality.

Project Description

It is time to resurrect the dreaded green owl of legend, and return to learning some languages.

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. So here I am, having a cheap remote toy spy tank sitting on my desktop - waiting to be hacked :)

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. The scope of this hackweek project is to get the initial framework set up using Jekyll with some basic content added. Further content will be added in the future.

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. Could it be that machine learning can be used to extract meaningful information out of that? That's what this project is about.

Project Description

It's time to learn a bit more about best practices in service management organization. This includes especially Service Level Agreements and the creation of a Service Catalog.

Project Description

Study/Trace SCMI code stack in ARM Trusted Firmware, such as build flow, included drivers, and protocols.

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. Now that themes such as Polycore are licensed so they are useable the aim is to build from there.

Project Description

A tool that may be a good place to start with a more modern UI for TC is https://cockpit-project.org/. This is being researched by the SUSE MicroOS development and now the YaST team. The TC/harness could be a module, that utilizes other SUSE modules. Cockpit has a web interface that can be accessed through any browser.

This project will focus mostly on getting to know the Clojure and ClojureScript ecosystem. As part of this project I want to see how good the integration with the respective hostplatform is and how easy it is to use libraries for e.g. JavaScript in ClojureScript.

jikos:~ # tc qdisc show qdisc tbf 10: dev eth0 root refcnt 2 rate 800Mbit burst 131000b lat 1.0ms

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.

In the last hackweeks and my free time, I've been developing several tools to various degrees of completion. The purpose of this hackweek is to finish three of them, publish them on github and create openSUSE packages. * finddupmusic

Try to use apache-rex framework while testing httpd modules.

Project Description

The idea is to create and internally host a simple webpage with proper backend code allowing quicker and easier lookup for package maintainers and bug owners from OSC. Nothing fancy, just a page with search box and few radio button parameters to execute the lookup and display the results. Obviously it needs to fulfill security measures when it comes to the access to OSC on the service level and also user access rights to the search page itself (e.g. Okta). Currently the lookup can be done via terminal (which is OK), but there are security measures in place which makes the lookup difficult for some and granting an engineering VPN access just for the sake of this OSC lookup is a bit an overkill for people that do not need it for any other purpose.

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.

I had an application can't run on recent openSUSE for some time but it can run on openSUSE13.1 before. So I'd like to have a docker container (image) to run the application and learn some about docker container

1% of SUSE Manager's functionality in 0.1% of the lines of code

Let's create a much simpler SUSE Manager — one you could use at home! Users should be able to deploy and operate in minutes with minimal configuration, while still retaining the very core features that make SUSE Manager useful!

The current crash-setup source is located here. Pretty much is working nicely but it doesn't care for the debug source making it impossible to use the crash> gdb list *<symbol> command right away. This is bug 997558 which should be worked on.

Right now, during the (open)SUSE installation process, the changes to be performed on the storage devices are presented as a list of actions such as: * Resize ntfs partition /dev/sda1 by 100 GiB

What I do: learn the virtualization knowledge, get familiar with various ways to migrate guest, know the user's normal scenarios and requirement. Goals: give an introduction or a summary to share, including text and graphics about virtualization and guest migration.