There are issues with S3 and S4 handling in a KVM SLES or openSUSE guest. I'd like to figure out what's going wrong and get things fixed as much as possible.

I just learned about xenctx, which is used to help debug Xen issues. I am wondering if it would be easily ported to KVM. If not, perhaps at least creating the equivalent for KVM may be useful for handling problems with KVM guests.

inputlirc is superior to previous lirc input daemon as it can monitor multiple input sources at the same time. This is needed for some new remote controls that appear as two devices, providing both virtual keypresses as well as mouse clicks. Since I'm too lazy to always build the package manually, I would like to have it available for OpenSUSE.

For development purpose, it is very useful to have an infrastructure that can spot regressions based on commit base. Currently, our existing infrastructure runs mainly SPEC benchmark and is cumbersome from perspective of any further development. I would like to build a replacement that will combine buildbot framework with a custom web project (based on Django framework). The web project will be used both for submitting reports coming from a buildbot slave and for UI which will serve plots and data. If you want to inspire a bit more, please visit Chrome Performance Dashboard or Mozilla telemetry. I hope I can make a simple extendable project that is going to eventually replace existing implementation.

Smalltalk is an object-oriented, dynamically typed, reflective programming language and Pharo is a modern, open-source,

Test the latest release of guesfs tools, and chech new p2v. Package it for openSUSE My branch

Enhance nm-applet icons

I would like to continue to work on a web UI for the Docker registry. I know we already got Portus which is based on Ruby on Rails, but I would prefer a project based on Golang with a singlepage application for the frontend based on RactJS. So because of the singlepage application we are forced to write proper APIs that gets consumed by the javascript application, beside that I also want to add a CLI client for managing the system. You can find the project at https://github.com/harborapp.

Implement a Little man computer in the Go programming language. Accepts LMC assembly code, compiles it and executes it.

We used trinity to make fuzzing test, but it hard to reproduce bugs. I'd like to try to use syzkaller or other fuzzy tools to find a stable process to reproduce fuzzy bugs.