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.

Look once again on Xperia Tablet Z and try to have there openSUSE running natively as alternative operating system.

Talking to people, getting the information about what had happened in the SUSE history, bringing all together to kind of a chronicle. Let's give it a try :-)

Installing linux on z/VM requires some way to punch kernel/initrd/parmfile into the reader which in turn can be booted. In a previous hackweek, I wrote a small tool, that makes it possible to do so directly from the internal ftp server. this has been proven valuable but not perfect.

In short, give second breath to http://hall.suse.de/bugs/defects.cgi.

Write a simple command line tool for getting the open pull request from github and put it into a trello card. The tool should periodically update a list of pull request. In addition it would be great to have a connection between the trello card and github pull request.

Pebble smartwatch is a nice gadget I own and I'd like to start playing with it at the code level.

SeaMonkey is the successor of the Mozilla Suite. The mail client allows connections over POPv3 and IMAPv4. In some cases one wants to leave the program running for longer periods of time, but once the mail client has password for a mail server it just stays connected. In case of "keep everything on server" profiles this means that the mail may stay accessible even when the machine is left unattended (which it often is). The purpose of the extension is to enable requesting the client to forget mail server passwords, so that the mail is no longer accessible without entering it again.

The Problem: many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one

My idea was created out of a need in my current team(Hardware-enablement). Whilst excessive SLE testing on multiple machines i was forced to remember tons of ips to debug remotely. Since i had to reinstall new releases over and over again, ips differ, obviously.

Gerrit is used for code reviews by openstack and its related projects (e.g. chef cookbooks). The web interface is too slow when you get 100 changes to review each day. It would be nice to have a faster CLI. There are already some python client libraries available. I am thinking about either doing this as a standalone application with python and something like ncurses or an emacs/lighttable plugin.

Plan

I have a Canon PowerShot S120, which allows for browsing / copying photos over WiFi. There are apps for Android, iOS, and Windows to do that. The protocol uses upnp to discover the camera and the smartphone/computer and them some HTTP-based protocol. I have some code using libupnp for the discovery and a perl script that is capable of transfering one file, but it's far from complete. Plus, I need to refresh my memory, because the last commit is from January :-(. Now, there seems to be some support for such cameras in gphoto already. So the plan is to dive into gphoto and use what I learned about the protocol to fix the gphoto support.

Moses is a statistical machine translation system that allows you to automatically train translation models for any language pair. Intention of the project is to tune up existing software, where a glimpse shows that majority of time is consumed by memory allocation, dynamic casting and other calculation non-related stuff. I would like to inspect many techniques (like perf profiling, GCC LTO, GCC profile-guided optimization, code refactoring, OpenTuner, etc.) which may bring really significant performance gain. Moreover, it would be really beneficial to come up with a cookbook that can be used by folk in general. If possible, I would like to create a step-by-step performance improvement graphs.

The idea is to have an internal web page that mainly presents new SUSE employees or the ones you might not know yet. Other topics can be covered like reports about hack week projects or other interesting stuff apart from the daily work we all do.