The kernel livepatching team developed klp-ccp to automate the work intensive task of copy&pasting self-contained livepatches from the original kernel sources together. We started using it right away as soon as it had been in a somewhat workable state, even though some quirks and workarounds are still required in everyday usage. The main barrier towards developing klp-ccp further is its internal compiler abstraction, intended to keep the generic code independent from the original compiler resp. the target architecture. It evolved over time and had been amended incrementally in an ad-hoc fashion as needed to quickly reach the main goal at the time. So there's room for improvement.
Human interactions are influenced by a myriad of subconscious biases. When these interactions move online and become text-based, plenty of us choose to conceal certain aspects of our identity. How many Twitter profile pics are real photos of the person running the account? How many female Warcraft characters are played by people who identify as men? I'd like to take it all a step further and create a place to experience real-time conversation with as minimal personal identification as possible.
This started as a sub-project of QDirStat, but it turned out that this may be useful in general, and it would be too dangerous and too error-prone to offer it directly in the QDirStat GUI. Things can easily go wrong, there may be many pathological situations, and many operations require root permissions; not anything a GUI program should rely upon.
Many years back I created a simple python based CLI package that wrapped the NWS API to get weather forecasts, discussions and current conditions. Meanwhile I have not had time to keep it up-to-date so many pieces are broken or using deprecated features of the REST API. The package is useful to get weather information much quicker from CLI than clicking through the NWS website.
Sometimes when we reproduce a customer issue, it doesn't always demonstrate the same behavior the customer is having. So, we engage backline or open a bug or throw up our arms in frustration. I have one such customer with just an issue like this. Running the exact same commands in an almost identical sles4sap version environment and yet I cannot reproduce what she is seeing? What to do?
Test drive some Kubernetes network plugins
Kernel livepatching tooling: improve klp-ccp's target abstraction
Bring opaws to Rust
Clandestine Chat Room(s)
Learn python, python-gtk3, play with orangepi zero, experiment ili9341 and 20x4 LCD screen
Resurrect NWS CLI project
Evaluating the influence of agile changes on the milestone delivery - assessing the risks
