I’ve promised I would share with you the results of building Kolab for the Raspberry Pi 2 Model B I recently purchased, so here’s a brief description; First, I used an out-of-tree image composed by vaughan from the #fedora-arm IRC channel on FreeNode. Because it is on Google Drive and Google Drive sucks, I’ve uploaded… Continue reading Kolab for Raspberry Pi 2
I manage and have managed thousands and thousands of systems during my career so far, and I continue to believe that a level of configuration management is required for any environment that consists of zero or more nodes. To this purpose, I had deliberately chosen Puppet — some 8 years ago. I’ve authored a couple… Continue reading Puppet is out, in comes Ansible
I should have known better and done my research in advance, buying a Canon Selphy CP910 for Lydia’s birthday. There’s no driver available for Linux, but there are drivers for the same CUPS software that Apple devices run. #fail. The printer will only take JPEG images. Not only will the printer only take JPEG images,… Continue reading @Canon, you suck.
I bought an Intel Pinnacle Canyon NUC5CPYH, a.k.a. an Intel NUC barebone, for my home network. This ships with an Intel Celeron N3050 processor, which RHEL 7.1 is so kind to tell me has not been tested. However, the installation is running fine, so I expect this will “Just Work(TM)”.
The Kolab development team uses the agile development methodology called Scrum. This is an iterative development process set out to achieve a predictable, consistent flow of incremental improvements to a software product, and as such is basically considered mutually exclusive with the concept of a pre-defined end-result. As I’ve mentioned many times before, Kolab includes… Continue reading Waterfall or Agile?
It is not commonly understood how software development projects moving forward as fast as they can and sometimes do, can be in direct conflict with their actual rate of adoption, not to mention their commercial delivery to market. This post outlines the differences between short- and long-term commitments, and how the distinction can be used… Continue reading Short- vs. Long-term Commitments
In the past, even before I joined the Kolab community, our product was released on a feature-based schedule. We’ve changed that to time-based releases, with an aim to be able to provide something new every 6 months or so. We’re now changing it again, but not in the way you might think. Not too long… Continue reading The Evolution of Kolab Development