Lay out a mock version of an existing SUSE R&D process in JIRA. The process should have a reasonable amount of complexity, like

GOAL

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE. To this end, I'm planning to add unit tests to libvirt.git that test conversion of domain XML to structures used by Xen's libxl interface. The first attempt at such tests was nearly 3 years ago

Having worked on KVM for a long time, it's time I actually start using it myself! I now have a high enough powered laptop to have a permanent setup on my laptop to do almost all the testing needed for releases, as well as maintaining playgrounds for upstream work and involvement. This will include nested virtualization, which is getting pretty bulletproof in latest kernels, as well as being able to play more with these other architectures that we now support KVM on, via improved TCG emulation (of course some testing and development will always rely on the physical hardware, but still a lot can be done via TCG incl. user-linux mode. I'm also seeing which aspects of pass-through testing will make the most sense to perform on the laptop (pci, usb, video, filesystem, etc.). Hopefully at the end of the week I will have gotten a better feel for all aspects of KVM as a "power user', and not just as a developer.

In a quite natural and steady way, all my relatives (wife, kids, mother, aunt...) have adopted openSUSE in their computers. There is only one resistance spot. My father's computer (HP+Windows8) implements all kind of mechanisms to avoid dual boot. I plan to use the spare cycles of my Hack Week to get a dual Windows/openSUSE system on that haunted computer. Killing Windows would be a feasible last resort.

RISC-V is an open ISA (Instruction Set Architecture) based on RISC architecture. It's originated from UC Berkeley and it's attracting more attention in recent years because of its full open architecture so every developer has opportunities to get involved in application processor design or apply it into different applications, such as IoT, Robotics, ... etc. Any topic about RISC-V is welcome, here are some topics you might be interested in:

The idea is to explore the technologies and the various components to realize some AI to predict pitfalls in source code which can potentially generate run-time misbehaviours. The potential area where this idea could have positive implications are: