Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often". Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.

Our QEMU/KVM testing needs to be improved. I plan on working on an ontology to help form the basis of a thorough test matrix for

While programming is occasionally a very rewarding activity, it's mostly a chore and the rest is filled with frustration. Let's teach an unsuspecting youngster program! To fulfill this nefarious goal I've set out to help my colleague without prior programming experience get hooked on programming, starting with python. The student finished an online tutorial and we pair programmed a tiny-fix-turned-massive-change in a tool used by our team.

froxlor Server Management Panel create and start a push request upstream the openSUSE Leap 42.1 configuration tab

The Nvidia Jetson TK1 is an SBC with Nvidia Tegra K1 SoC (quad-core Cortex-A15, 32-bit ARMv7). I have openSUSE running on the Jetson TK1, but KVM is currently not usable as the CPUs are not booted in HYP mode. Thierry Reding of Nvidia has some work-in-progress for U-Boot and upstream kernel that I would like to test.

Micro-service for - making a report

The software is a rails app with an Angular.js frontend using the gphoto2 library to trigger a Nikon D60 camera. Features: take pictures, browse pictures, automatic upload to a gallery (tumblr, flickr, owncloud), qr code for download,

I'm trying to write a static analyzer for Lua programming language. And I've ready done some parts, say, lexer/parser/AST/types...etc. The challenge part at present, is to write comment-based type annotation, for later type-inference. I plan to implement it in a week. I've spent years on this area. Hope I'm lucky in hackweek.

During the last CSM workshop we identified the need to have a good way to share the images we use for testing. We have documented the requirements and the current status in this wiki page (we even have a diagram). So analysis is done... it's time for action. The solution should be relatively easy to implement using our portfolio of solutions. Coordinating all the potential users should be easier during Hackweek, specially since I'll be in Nuremberg (and I can physically chase most people ;-) ).

open-sTeam is a platform for cooperative work and cooperative learning developed at the university of paderborn in germany. the platform is being used at http://societyserver.org/ and is being developed further.