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! It doesn't concentrate on what it should do: Tell people about the distro so they download it. It's design is 5 years old, it's not mobile, it's not accessible. There is absolutely no interactive, engaging content at all and the technology used goes as far as a shell script/cron to update dynamic content.

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

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?"

Status at the end of hackweek 10

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

What's about an app that helps you with downloading openSUSE documentation? Does a free app for managing gettext files (.pot, .po) already exist?

Build Service needs an openid. Imagine following case:

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

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. There was a little bit of progress on the project since then, but with the upcoming KDE Frameworks 5 there will be quite a number of additional libraries available for Qt developers. This should be well represented in Inqlude as well. The coverage of Inqlude is also still not complete, and the tooling needs some improvement as well, especially regarding integration with distributions.

Wicked is a network configuration infrastructure incorporating a number of existing frameworks into a unified architecture, providing a DBUS interface to network configuration. https://github.com/openSUSE/wicked

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: * It doesn't detect appointment changes (pretty easy to fix as each event has a unique ID)

<p>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.<p>

some ideas

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

~> osc my pkg | wc -l 699

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: * Feeling really crazy? Try Windows 8

A web frontend for the mirrors in the mirrorbrain database to allow the mirror admins to manage their entries themself. You might know MirrorBrain already: our download redirector and Torrent/Metalink generator used u.a. on download.opensuse.org. It's really a great tool that plays a hidden key role inside the openSUSE infrastructure.

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. However, while Bonjour is popular and widely used in Apple products, few users take advantage of Avahi in Linux world and the number of applications that do integrate Avahi are still just a few and this feature is not often used.

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: * [Support for federated login using GitHub, OpenID, Facebook,...][170]

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 : * Handle I2C slave address collisions. If two SMBus slaves would use the same I2C address, ARP lets one of them pick a different address to avoid the address collision.

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks. For users, this provides an opportunity to influence, or create unique tailored editing experiences for Studio appliances. For Studio maintainers, this provides a road towards a modern appliance editor, and a chance to remove tens of thousands of lines of brittle legacy code. For hackers, this provides a chance to get your feet wet with modern client-side web technologies, like

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.

Current OBS controls for package rebuild triggers