midgard

At Nemein we do maintenance for quite a few servers of our customers.

While some customers have their own Linux distribution preference - usually RHEL - in most cases we have a say what distribution runs their servers.

So far this has been debian, but now we're going for Ubuntu Server.

Gadgetopia has a post on how CMS's should provide an API for content filtering.

Since Midgard is persistent storage API first, and CMS only second we obviously have nice APIs for doing exactly this.

Yahoo! Fire Eagle, kind of "GeoClue for the Web" was released last week.

There has been some discussion about the deployment model for the upcoming MidCOM 3 MVC framework for PHP and Midgard 2.

My suggestion was to enable WebDAV on all MidCOM servers so content structures, configurations and templates could be moved between them with simple drag-and-drop.

Yesterday Arttu Manninen posted notes on how to use git for MidCOM 3 development.

In addition to the repo.org.cz usage he described, the other way to work on the next generation PHP framework for Midgard is using the GitHub service.

In his recent blog post, Piotr Pokora showed how the the D-Bus API will work in Midgard 2. D-Bus is an interprocess communications system that is used heavily in modern Linux desktops like GNOME and KDE.

There has been some discussion on how the different items in the Midgard roadmap fit together.

Here is my company's view on how we see ourselves proceeding.

We're in Linköping, Sweden for the Midgard developer meeting, and I suddenly realised the Midgard community really likes Nokia's internet tablets.