Lots to read this week.
Mini-ZFS theme this week.
No theme this week other than of course BSD.
Catching up on some items I missed last week.    
Note the upcoming SEMIBUG meeting.  I'll post a reminder.
It is status report season!
Literally this is my open browser tabs pasted in order.
Done early, and I have more BSD-related tabs to get through.
Well, I made up for last week's short list. Semi-BSD-related: One of my 3 workplaces needs a Software Team Lead.  (scroll down)  The main product is FreeBSD-based, though this team position does not directly work with it.
This bulked up fast this week.
No theme, but plenty of variety.  
Lots of old BSD this week.
Happy leap day!
UNIX history as an accidental theme this week. Update: NetBSD 9.0 is released.
No theme evolved, but lots more links this week.    
It's probably going to be quiet for at least a few days because of the Christmas holiday, though I'll of course have the normal weekend features up. In the meantime, here's something to ponder: this post about tmux and plugins for it led me to thinking about plugins in general.  The pkg system is sort of a plugin scheme for BSDs, much like apt for Debian, yum, etc.  Each language has its own libraries to load and plugins to manage past that, like Perl's CPAN.  Nowadays, applications have their own plugins.  For instance, a system with Wordpress installed with PHP installed with PHP plugins required with Wordpress plugins that also require given PHP libraries.  Wordpress manages keeping itself and its plugins up to date, but not the underlying PHP installation.   You can get something similar with Perl along with the Perl-specific package updates, through cpanm.  Or, npm, which seems to be its own world of constant flux. How many levels could this go?  Like running multiple emulators within each other, how many levels of plugin could you achieve?  There's probably a series of levels proceeding from tedious to barely maintainable to ridiculous.