www.opensuse.org is the single most accessed page in the SUSE/openSUSE universe. With 1.5 million visits per month it generates 2.5 million page views and has around 500 people on the page at any given time. Yet it's one of the oldest, crufty pages we have!

The new SUSE Floor is nearly done. The core functionality is already implemented and only some basic features are left.

Redmine.suse.de (as an inhouse tool) is very close to be a jump in replacement for Trello.com (the outhouse tool). Investigate into setting up a redmine-board so that it has exactly (and only) the features a Trello board has,

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"

Use machine learning and natural language processing techniques to analyze the changes made in a project, and classify them in:

What's about an app that helps you with downloading openSUSE documentation?

Build Service needs an openid.

The huge glass front of the Allhands Area facing Maxfeldstrasse wants to shine in Geeko-Shape.

During Hack Week 7 I worked on an archive of Qt-based libraries. The goal was to easily make all available Qt libraries accessible to developers. Think CPAN for Qt. So I hacked on a web site and a command line client.

Wicked is a network configuration infrastructure incorporating a number of existing frameworks into a unified architecture, providing a DBUS interface to network configuration.

I already have a [python script][0] processing mails received in the Calendar folder to get the ical event and push it to [radicale][1]. It has several drawbacks:

**Rescue system** has a lot of options , but most of them can only be set at boot time, first idea is too provide a way to configure them while the system is running.

After https://hackweek.suse.com/projects/105 the next thing to merge is hermes.

~> osc my pkg | wc -l

Feeling very comfortable with your (open)SUSE desktop? Don't get too comfortable; there's a lot of innovation out there. Try living in a different system for a few days, and see if you can find some innovative paradigms to bring back 'home' with you. Here's a few suggestions:

A web frontend for the mirrors in the mirrorbrain database to allow the mirror admins to manage their entries themself.

Zeroconf/Bonjour/Avahi is a very interesting technique that targets at freeing users of services from tedious IP-based network configuration by automatic-distributed address-assigning, name-assigning and service discovery/browsing. It's named officially as zeroconf, Bonjour is the implementation in OS X, iOS and Windows, while Avahi is for Unix-like system.

openSUSE lacks useable cross-compilers to glibc systems. This is the attempt to provide those, most important a cross-compiler for arm/aarch64.

Currently, opensuse-quickstart sets up a one-machine Cloud based on OpenStack, either with KVM or virtualisation. In order for bootstrapping further hosts, it would be much easier to set up only a bare-metal cloud on one machine, and PXE boot a 2nd machine via OpenStack Nova/Ironic.

My plan is to add some more features to Weblate. The list is definitely not complete, but I'd like to check at least following areas:

Gathering detailed information about hardware in an automated way with chef using an ohai plugin enhances transparency about the hardware being used in a datacenter. The idea is to write a plugin for ohai that gatheres information from hard drives used in a node that runs chef-client.

The SMBus standard specifies an address resolution protocol (SMBus ARP.) It has two key features :

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks.

In case any of the source files changed, openSUSE Build Service rebuilds the dependent packages regardless of whether that particular modification affects the dependency. This makes our resources footprint bigger (and the electrical power bills higher). It also affects users, because every new package build causes the package manager to include that package in the next update thus consuming network bandwidth and resources of users' computers.