Intel Rapid Start Technology(IRST) is a firmware mechanism enables your system to get up and running faster from sleep, saving time and power consumption, it will cause the system to wake up from S3 and suspend to S4(with SSD)[1]. Currently kernel 3.11 already support it[2], however there haven't a graphic tool to control its wakeup event and timeout, like as similar tool on Windows[3]. This Hackweek I'll create a YaST module to handle those parameters.

Finish extension for server side history for jabberd2 server and create a simple webui to browse it using tntnet. Part of the project is to learn to use tntnet toolkit, other part is to have server side history.

The goal of my project is to achieve total world domination. == Hell, yeah!

xfstests is rather comprehensive filesystem testing framework used for functional filesystem testing. The aim of this project is to integrate xfstests with our qa_automation framework so that xfstests can be run in it and results are automatically processed and stored in qadb.

Although there isn't much demand right now, it won't be long before >256 vcpus in a KVM guest will be desired. Currently, due to 8 bit apic ids only being used the limit is 256. Implement the x2apic infrastructure that will allow QEMU + KVM to break the 256 vcpu barrier.

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 want to continue my work on this feature for a CAT (Computer Aided Translation) program, OmegaT. When translating a segment (usually a sentence), I would like OmegaT to automatically replace all words it finds in an active glossary by their translations. This will save the translator some time.

Links:

Write a tool to generate documentation (README.md) from chef cookbook attributes files including the comments that describe the attributes. The goal is to use this with the openstack chef cookbooks from https://github.com/stackforge/ and maybe integrate it the upstream Gerrit as a Jenkins job.

In case any of the source files changed, openSUSE Build Service rebuilds the dependent packages regardless of whether that particular modification affects the dependency. This makes our resources footprint bigger (and the electrical power bills higher). It also affects users, because every new package build causes the package manager to include that package in the next update thus consuming network bandwidth and resources of users' computers.

The evfilter project (https://github.com/lhc4/libevfilter/) isn't able to substitute multiple events to one event or vice versa. I want to improve that and repair some other bugs.

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks.

Feeling very comfortable with your (open)SUSE desktop? Don't get too comfortable; there's a lot of innovation out there. Try living in a different system for a few days, and see if you can find some innovative paradigms to bring back 'home' with you. Here's a few suggestions:

pyg will be a PEG parser library formed as an internal Python DSL. it will be used in cramex, a copycat of cram with expect support.

QADB is the database used to strore results of automated tests in SUSE QA.

Initial idea to build a tool to help rubygems community to rotate maintainers for abandoned projects.

The basic idea behind learning language is to ensure three parts:

I've been running a podcast together with two friends for over a year now. We have a recording and mixing process going, but unfortunately it involves using non-free operating systems and software all the way through.

~> osc my pkg | wc -l

The libvirt TCK provides a framework for performing testing of the integration between libvirt drivers, the underlying virt hypervisor technology, related operating system services and system configuration. The idea (and name) is motivated by the Java TCK.

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"