> [arbs] is a tool for keeping an OBS project in sync with an ArchLinux package repository. More specifically, I use it to sync [home:roman-neuhauser:arch-community][h:rn:ac] with [community.git][c.git], a mirror of the actual svn repository underlying community. arbs already exists but has many rough edges. the goal of this hackweek project is to make it resilient in the various failure scenarios so it can be used in a truly unattended fashion.

CalDAV [1] and CardDAV [2] are client/server protocols designed to allow users to access and share calendar and contact data on a server. There are many CalDAV and CardDAV clients around, e.a. Thunderbird/Lightning and also free CalDAV and CardDAV servers like Baïkal. With that project I want to create a client in PHP to be able to create and modify data in calendars and addressbooks from websites.

SELinux Common Intermediate Language is a language that allows the creation of SELinux policies. Some of the traditional constrains (tight coupling, nested optionals, ...) are lifted or not as problematic. http://github.com/SELinuxProject/cil/wiki/

This is about starting to use functional programming paradigms that get used more and more? It is mainly about rewriting a small test program (repclean) in a functional style, using immutablity, parallelism and async techniques.

Linux From Scratch (LFS) is a project that provides you with step-by-step instructions for building your own customized Linux system entirely from source. Build the customized linux step-by-step is good way to understand linux system deeply. (Include cross compile TEC which I have interest )

Spacewalk is the upstream project of SUSE Manager. Currently Spacewalk runs on RHEL, CentOS and Fedora, while SUSE Manager runs on SLES.

VOVO is a server-client architecture to determine current abuild load on devel-network machines. The goal is to trigger machines on and off depending on build power. It is an attempt to reduce power consumption. Current status:

Make a final attempt to implement a graphical user interface for grub2 (gfxboot2).

It's quite some work, unfortunately. Here's what's done so far:

CoreOS is a new Linux distribution that has been rearchitected to provide features needed to run modern infrastructure stacks. CoreOS is popular on most cloud providers (EC2, Rackspace, GCE), virtualization platforms (Vagrant, VMware, OpenStack, QEMU/KVM) and bare metal servers (PXE, iPXE, ISO, Installer). Play with CoreOS during hackweek and see how and why it works well for HA.

Storing the devices in libstorage as a graph looks like a natural approach. The boost graph library (BGL) could be used here instead of the selfmade iterator over iterator (not a graph) concept currently used. Together with a redesign of the current objects several features would be simple, e.g. using disks for filesystems, renaming LVM volume groups and logical volumes, switching to and from partitioned MD RAID.

It is well-known that two git commits within a single repo can be independent from each other, by changing separate files to each other, or changing separate parts of the same file(s). Conversely when a commit changes a line, it is "dependent" on not only the commit which last changed that line, but also any commits which were responsible for providing the surrounding lines of context, because without those previous versions of the line and its context, the commit's diff would not cleanly apply. As with most dependency relationships, these form a directed acyclic graph. Sometimes it is useful to understand the nature of parts of this graph; for example when porting a commit "A" between git branches via git cherry-pick, it can be useful to programmatically determine in advance the minimum number of other dependent commits which would also need to be cherry-picked to provide the context for commit "A" to cleanly apply.

Using traditional hardware development tools, apply a Non-uniform Choppy Transformation to a block of ligneous substance. The end result should be a 3D rendering of the Geeko glyph.

GNU Guile-2.2 will be based on brand new backend, CPS(continuation passing style) as the most significant IR, and a RegisterVM. These are the prerequisite for the final AOT compiler. The old Guile-Lua is old for compatible with the brand new RegisterVM, moreover, it uses LL(1) which is painful for hacking. I've rewritten the parser with LALR and all the intermediate part before transfer it to Tree-IL which is another iR before CPS. Besides, I'm trying to add type-inferencing and partial-evaluation for Lua specific optimizing. Although there's partial-evaluator in Guile backend, it's a generic one for all the front-end languages.

Currently whenever there is a test, we need to find or build environment on our own machine or borrow some one else's machine temparorily. I hope we can collect all testing machines in our local team and build a sharable testing environment. Every one can reserve and use the machine, add machine, check machine info to find proper one (hardware and software) for test, share vm images, share other testing related resources, etc.

Learn ceph architecture and try to deploy a ceph cluster.

The virtualization team's automated testing has a long history. It was born in the old Novell Integration Test framework. The virtualization lab ran an instance of this framework for many years. Over time, those who knew the framework left the company, taking their knowledge and leaving little documentation behind. As our testing needs increased, we found the old framework insufficient, but saw little value in improving it given the available open source CI frameworks. Before burying ourselves in SLE12 development, we took some time to move our automated tests under control of a Jenkins instance running in our lab. Tests were configured to run when new packages landed in our SLE12 devel project, ensuring our queued SLE12 submissions were continuously tested. But more is needed.

I just learned about xenctx, which is used to help debug Xen issues. I am wondering if it would be easily ported to KVM. If not, perhaps at least creating the equivalent for KVM may be useful for handling problems with KVM guests.

Each of the core dump upload servers in Europe and USA could be improved if the shell scripts were combined so that the same tasks can be performed on each site, e.g. downloading of all packages needed for crash usage with a specified core dump by allowing for configurable (or even automated) selection of locations to obtain data packages from.

Working on a way to add exceptions using javascript (jquery), php, json, and mysql to modify the generated calendar used to manage who is on after hours.