It would be excellent if Hackweek projects had a standard way to include URLs for their code repositories, as well as URLs for communication methods like chat and email. This would allow folks who are interested in a project to either lurk a bit to learn more, or directly reach out to the folks running the project.

Current virtualization requirements mainly come from fate, and I haven't got chance to try freely many features of qemu/libvirt. So I will try to play it.

Currently Salt is using supportconfig utility alongside with the SUSE Manager installation. Every single bugreport for Salt, that contains its logs are always useless that regard. It might work for SUSE Manager, but for Salt it doesn't. And even after asking user to switch the cluster into a debug mode or even trace mode, it is still far away from being useful enough, so the supporter don't need to dance with the tambourine around the fire, guessing what ghost just munged what component.

Since my mailbox has migrated to office365 mailbox a couple of weeks ago, I tried to optimize my tool chain to sync my mail and calendar and integrate to the gnome-shell (calendar, notification). So far I am comfortable with such a set and gonna use 2-3 hours in hackweek to summarize the practice of combining the following tools in written format:

Investigate possibilities for the distributed builds for Ceph to speed up builds.

Project Description

Explore django

Build a network of ("edge") humidity sensors using Raspberry Pis with SenseHats and additional cheaper sensors

Description

Implement a trentoctl CLI for interacting with a trento installation

Description

Description

A long time ago I explored using the Robot Framework for testing. A big deficiency over our openQA setup is that bringing up and configuring the connection to a test machine is out of scope.

Working on a way to add exceptions using javascript (jquery), php, json, and mysql to modify the generated calendar used to manage who is on after hours.

Although I've been maintaining CRIU package, I had little time to play with it recently. It's still interesting especially in combination with various containers. So let's spend (or waste) some time.

Since I'm a maintainer of Gnome-Logs, I'd like to hack on Gnome-Logs. During the hack week I'll focus on the bug 753471 of Logs.

There are vastly different syntaxes being used by Linux softwares nowadays - Apache, Bind, NTP, Postfix, just to name a few. It is a very tedious task to implement comprehensive parser for every single configuration file, and even more difficult to produce configuration text (file content) from parsed syntax tree.

Sometimes, you want a flexible way to handle certain situations involving C++ exceptions, particularly those for which alternative actions are either easily encapsulated, do not substantially interrupt the program flow, or must cross a foreign-function interface or thread boundary.