[en] Welcome to euroquis.nl. Originally intended as a site for a European source-code-quality project, it now serves as the hub of my online presence. Most of what happens here goes on on the blog.
[nl] Welkom bij euroquis.nl. Dit was oorspronkelijk bedoeld als site voor een Europees code-kwaliteitsbeoordelingsproject. Nu is het centrum van mijn online aanwezigheid. Er gebeurt vooral wat op mijn blog.
It’s been nearly three months since Calamares transitioned to a community-maintainence model. That’s when I left Blue Systems as the paid maintainer, and so it’s been all-volunteer work since then. “Volunteer” can still mean “an 8 hour day hacking at issues”, but in terms of regularly available time, there’s been a sharp drop off. But let’s take a look at what those three months have brought:
Testing OS releases with VirtualBox, ZFS, and FreeBSD is still one of those “that’s amazing” things for me. This post reprises two earlier posts (laptop inception and vzvol) with some succinct instructions. Trigger for looking this up again was a question about FreeBSD 12.3 compatibility for KWin.
At work-work there are educational sessions for the software team. They last about 2 hours, generally filled with a mix of watching a talk, discussing how the talk applies to the codebase, and individual developers presenting something. Typical conference talks might come from CPP on Sea). Discussion might go on about vocabulary types – what are the things in our system? Presentations are whatever somebody feels is interesting, and I’ve written up two 20-minute talks so far.
KDE Plasma in FreeBSD ports is still version 5.24.6 (in ports HEAD, while the quarterly has 5.24.5). It will remain stuck at that release for a while longer.
The KDE Community has used – and gently encouraged – the Fiduciary License Agreement (FLA) which was created by the Free Software Foundation Europe (FSFE) some 15 years ago. The FLA is a kind of copyright assignment that preserves the Free Software underpinnings of the software, ensures the contributor can (re)use the work and that the fiduciary can handle licensing questions around the contributed code. A CLA without the corporate-style downsides.
subscribe via RSS