Problem statement

Current Zend Framework OpenID implementation does not support the protocol version 2.0 fully. For example the Yadis discovery is not supported at all. Thus the Zend Framework OpenID module can not be used with OpenID providers using this version of the protocol.

Crash has some support for per-cpu variables, but it really only works for static variables. My idea is that you should be able to take a per-cpu pointer and see the formatted data. The syntax should allow to specify a CPU or do it for all:

This would fix the two 'biggest flaws' in the current software installation workflow. Basic support for detecting file conflicts is already provided by libsolv, but it needs to be integrated into libzypp. In order to support rpm %posttrans behavior, zypp needs to collect these scripts during package installation and execute them at the end of it's transaction.

Ticklist is a web application enabling users to record their ascents of climbing routes as well as to maintain their personal list of currently projected routes. My implementation went from working alpha back to pre-alpha status (~ basic things not working) while migrating parts of the codebase (knockout.js -> angular.js). The goal of this hackweek project was therefore to finish this migration and fix the basic features in order to make the app useful at least for personal usage.

There is now bunch of yast devtools but the most of them are obsolete or useful only for ycp developement, which is now dead. It is also mixture of tools to build package, develop single package and new yast meta for doing changes on all modules developed by yast team. So goal is

A few months ago in a random post-PyConAU fit of hackery, I got disk-image-create in TripleO's diskimage-builder project running on openSUSE 12.3, i.e. you can now run disk-image-create on an openSUSE system, and have it create, say, an Ubuntu system image. Time to take the next step, and make it capable of building openSUSE images ;-)

Nodejs is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. It uses NPM as its packaging system.

The webui is currently the poor cousin of the OBS parts even though it's wildly used. It's a pain in the ass to code for it as there is not a API for most things you need to do - and if there is it's cumbersome to use.

Improve OpenStack documentation and tools used by it.

Base on internal user request, I`d to create the dispatcher script for NetworkManager allow run up/down script for DNSMasq when a VPN connection was started. In the current setup when VPN is started via NetworkManager no scripts is run.