Tracking and fixing translations in modern applications is a surprisingly complicated task. Visible strings often come from several projects, and strings can be processed by a complex formating. The project should extend the current project trace-wrappers to easily display string sources inside the application. The project successfully reached a working state: watch gettext

Figure out how to get SUSE VPN running on Android.

In GCC we have multiple intermediate languages and for all of them we do manual pattern matching and replacement. The project uses a domain specific language to unify and simplify those pattern matching and replacing code. During hackweek I plan to split out working parts to merge to GCC trunk.

I want to modify the driver so that it:

• a) supports newer hardware

I like to try out if it is possible to write a program that does not have any kind of the traditionally separated documentation (like external files that contain the documentation texts or comments in the program code). Instead all documentation must be implemented as code at the same place where the matching functiomnality is implemented (i.e. each function implements also its documentation). In the end the user should get only the executable that he can run to let it do the intended functionality and also to provide any kind of documentation. What I do not want is a dumb '--help' option that lets the program spit out its built-in documentation. What I would like to have is that the user can run the executable in some kind of self-inspecting way. I mean: While it does the intended functionality, it can also provide documentation so that the user can explore the program while running it. In the end the user experience should be more like a text adventure ;-)

The idea is to play around with a minecraft-like block exploration game, written from scratch in C using SDL2 and OpenGL 3.0. Minimal dependencies, probably won't be a game as such before the end of the week, but the goal is to have a world generated and to be able to walk around in it. Why? Mainly to refresh my 3D knowledge, catch up with what's happened since I last played with that stuff, and to have fun. :) * Source code

1) Add support for the Microsoft Azure File Service REST protocol to Elastocloud, a cloud storage client library created in a previous Hackweek. 2) After completing (1), create an Elastocloud VFS module for Samba that intercepts filesystem IO and locking operations. This would allow for the creation of a globally accessible Samba share backed by cloud storage, which could also be accessed by VMs deployed in the Azure cloud.

Description

Travis provides nice integration with GitHub, it can automatically run tests for every commit or every pull request.

The UEFI image for QEMU/AArch64 is available in the openSUSE build service now. However, there is no openSUSE image for that setup. This project is to make openSUSE run on QEMU/AArch64 + UEFI and this may be useful for the openQA in the future.

Seems that there is currently no good way to check which python modules are outdated in devel:languages:python . AFAIU http://osc-collab.opensuse.org could learn howto handle information from pypi and set the attributes "UpstreamVersion" and "UpstreamTarballURL" for the packages.