KGronlund

I've been running a podcast together with two friends for over a year now. We have a recording and mixing process going, but unfortunately it involves using non-free operating systems and software all the way through. It is probably going to be hard to get away from using the things we use for the actual recording part for a while, but one thing I feel should be perfectly doable in openSUSE is the mastering bit. In theory, Audacity could work for this, but it is old and clunky and doesn't do real-time filtering, making it annoying to use.

I would like to have a programming language that has the performance characteristics of C, but integrates some programming language features that I like from other languages. My first goal would be to start with a language that is very limited in scope and compiles directly to C, and step by step add to it. There are a lot of programming languages, but very few that handles memory as an explicit resource. To be able to explicitly manage memory is a very powerful technique and essential for applications such as high performance video games.

I want to learn Erlang and see if it makes sense to use it in the context of High Availability (it would certainly seem like it). As a learning project, I want to try to reimplement my koi project (https://github.com/krig/koi) in Erlang. Koi is a minimal cluster manager I wrote in C++.

With rust 1.9 released, it should be possible to from now on bootstrap rustc from the previous version of rustc (so 1.10 can be built using 1.9 etc.). This means that it should now be possible to create a rustc package which no longer needs binary snapshots to build, meaning that we might even be able to submit rustc for inclusion in openSUSE Tumbleweed. This is the first goal.

The public cloud is generally not a high availability-friendly environment, with unpredictable I/O latencies and machine stalls, custom tools needed for handling IP assignment etc. The idea with this project is to see if there is any way to leverage the Raft algorithm and booth together with pacemaker_remote for resource management to manage cloud instances and services running in the cloud.

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

I want to experiment with three things: * Blockchain