It ain't rocket science, it ain't thrilling, it's just useful. Quick Event is an established orienteering management software but it is still distributed in non-standard form for Linux distros. Package the software in standard packages for major distributions.

This can be seen as a subproject of ethtool netlink interface but from the technical view it's independent. Every new piece of software is going to be buggy and with frequent changes and rewrites, new regressions are introduced. Automated selftests can help a lot but as ethtool deals with hardware devices, we do not want these tests to depend on a specific hardware. The netdevsim driver was created as a virtual device which (unlike e.g. dummy) cannot be used for actual network traffic but implements various configuration interfaces so that it can be used for their (automated) testing.

Since Kubernetes already has a clear path of "in-tree" volume plugin to CSI migration. I would like to understand the concept of CSI with writing a simple driver for Kubernetes. Reference:

labgrid [0] is an embedded board control python library with a focus on testing, development and general automation. It includes a remote control layer to control boards connected to other hosts. My idea was to use this to be able to test my MediaTek boards remotely.

During the previous Hackweek [0], I have successfully implemented, tested and merged [1] an implementation of the entire C++ standard header <future>. This time, my aim is to modernize the C++14-esque standard library [2] of HelenOS [3][4] with a C++17 feature - the <filesystem> header. The <filesystem> header is much larger than the <future> header which I barely managed to implement and test in the allocated time for the previous Hackweek, but <future> was mostly OS-independent as it relied only on previously implemented features of the standard library. The <filesystem> header, however, is limited by the filesystem API of the OS and as such implementing of the entirety of it might not be possible, limiting the scope of the project (which is a good thing due to the time constraints). The primary features of the header [5] that should be implemented:

I would like to learn more about something outside of engineering. I have selected to learn more about marketing; something our overall team is doing more of...

• implement a POC deploying CaaSP v4 on top of AWS using: Spotinst's elastigroup
• "Spotinst Elastigroup predicts Spot Instances behavior, capacity trends, pricing, and interruptions rate. Whenever there’s a risk of interruption, Elastigroup acts accordingly to balance capacity up to 15 minutes ahead of time, ensuring application availability.