The Kolab Weekly

Welcome back to the Kolab weekly. In these weeklies, I summarize what’s been happening in the Kolab universe 😉

Product Ownership

I’m pleased to announce we have an official product owner: me. More on this later, but …

This means that I’m in charge of understanding what the needs are for feature requests that come in, and outline the overall strategy for the product as a whole, in pursuit of our vision for Kolab.

I do not do many of the things associated with my new role alone or by myself though, as we have both limited resources and we have experts on subject matters not my expertise.

See the Architecture & Design workboard for things under consideration (“Inception”) and things being worked on (“Elaboration”), topics undergoing actual contribution and development (“Construction”) and the stage where Architecture & Design has its minimal engagement (“Transition”, a stage in the process that involves tweaking delivery, real world deployment scenarios, etc.).

Again, more on why it’s called “Architecture & Design” later on.

ClamAV Now Starts

A default Kolab installation may have found ClamAV didn’t start, but the known workaround is now included with PyKolab’s setup-kolab, so no-one needs to worry about the workaround any longer.

This still doesn’t exonerate us from the principle of fixing it at the origin, upstream, the EPEL 7 package for ClamAV, but the code executed here runs a check to determine (best it can) whether the systemd unit file clamd@.service would work, or would not.

SELinux MUST not be Enforcing

Another setup-kolab enhancement, for a very liberal definition of the word enhancement, causes the setup to bail out very early if SELinux is currently enforcing or the configuration for SELinux is found to return to enforcing upon a system restart.

This too does not exonerate us from the responsibility of writing the necessary SELinux policies. This has been worked on by yours sincerely in the past, and just needs to be completed. More on this later.

We Have a Sprint

The 201609 sprint can be called an actual sprint, since the sprint’s backlog is just a tiny little bit too long — and I’ll be making it slightly longer even, over the course of the weekend, and than work my ass off ever so slightly much harder over the course of the sprint. I plan on an excellent retrospective as well as some genuine progress by next Friday.

It’s also a genuine sprint in that we’ve not compromised the team’s velocity with interruptions.

We’ve Let Winterfell Eat Babies

Driving technology forward is never a road without bumps, sometimes severe bumps, and last week we’ve found that Winterfell is indeed broken. The fixes for it are now a part of the 201609 sprint, so expect Winterfell to return to normal for at least as far as Guam and PyKolab IMAP usage is concerned. Did I mention we do things properly or not at all? The current workaround is to make PyKolab use port 9993 on localhost rather than regular IMAPS on port 993, but this is not valid for distributed environments.