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:

This is a side project I started a while ago. The idea is to implement a tagging engine with some "advanced" features for the Django web framework (in what Django calls a "reusable app").

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

Project Description

Explore django