A week of learning, improving and playing with some of the relatively new front-end stacks and patterns. * Angular 2+

I'm planning to do some research about RV32E which has only 16 GPRs, but riscv-pk doesn't have RV32E support so that the RV32E aware GCC (https://github.com/kito-cheng/riscv-gcc/tree/riscv-next) cannot build riscv-pk. I'm going to study how the proxy kernel works so that I can do some modification to let it support RV32E.

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.

• learn how to write Dracut modules
• investigate running Salt in Dracut initrd

Lately the necessary patches to get rudimentary support for the Mediatek chromebook with a mainline kernel got posted. There are some hacks and I'll work on some good solution to get graphics go, at least.

FIPS 140-2 , The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2), is a U.S. government computer security standard used to approve cryptographic modules. The title is Security Requirements for Cryptographic Modules.

Learn Vim by reading book of Practical Vim

I would like to work mainly on https://fate.suse.com/323638, think of default configuration and perhaps create a small configuration script for conky.

This would be a multiple step solution, a first idea that I would explore would be: 1. Query Florian's qam_reposervice API from RRID to base products and modules needed for update

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

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".

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?

Use this hackweek to practice and learn more about Go.

During testing virtualization , I usually met some issue and can not position the issue location (host or guest), so I would like to deeply learn QEMU code, card the work flow, understand communication mechanism between host and guest. Targets:

As live migration is widely used in many scenarios nowadays, spend one week time to study it and try to improve its efficiency, e.g. seamlessly migrate with less downgrading the guest. Another challenging part is memory migration, as it involves the dirty memory's detection, record and copy.

Learn how openQA was implemented in details. And will spend some time to learn Perl (e.g. read the book <Learning Perl>)

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.

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

While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device. This allows to read from inside the VM a blob by reading /sys/firmware/qemu_fw_cfg/by_name/opt/keyname. The driver is included in recent Linux kernels.

Flickr provides not only a large space for photos but also nice features around, including tags and other metadata allowing sorting of photos by different criteria - but one is very limited in the design of something like "frontpage" of such galleries. The solution is to use 3rd party JS solutions using Flickr API, like nanogallery. The purpose of this project is to learn to create such galleries, the best would be to add social features of flickr directly there, like comments or faves.

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