LDAP (Lightweight Directory Access Protocol) is an emerging Internet standard for accessing directory information, and allowing LDAP-enabled applications to access multiple directories. LDAP v3 supports features such as secure connections, entry management, schema management, and LDAP controls and extensions for expanding LDAP's functionality. LDAP Libraries for 'D' enables you to write applications that access, manage, and update information stored in any LDAP-aware directories, using D language (http://dlang.org/).

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

There is a new kernel API/feature: powercapping. The perfect userspace tool to ease up usage and later possibly provide library calls is cpupower.

Look at static code analysis and code coverage for a C++ project, in this case libstorage-bgl-eval. This could include:

<p>There are numerous testing tools for the GFX stack available - the oldes being the xtest suite. At the same time, we are still lacking automated test environments for the funktionalities of DRM, Mesa and X. Ideally the tests should be performed automatically and unattended and the results should be compared to previous runs to detect regressions.</p> <p>Research what tools exist to date and how they can be employed.</p>

This Hackweek I would like to finish enhancing of the mysql-packaging git repository [1]. This improvement mainly consists of scripts for a kind of simple continuous integration and git hooks to enforce a few policies for our project. If there is a time I will also take a look at the mysql package itself and check if there is anything to improve. [1] https://github.com/openSUSE/mysql-packaging

Tahoe-LAFS is an open-source decentralized cloud storage system. It distributes your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security. It provides a provider-independent security where the storage provider does not have access to the unencrypted data because all data is encrypted, erasure-coded, and hashed before leaving the client's machine thus preserving confidentiality, availability, and integrity of the data.

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.