Midgard

Lodz, December 18th 2008 -- The Midgard Project has released a second release candidate for the third maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software content management ... [More] framework.The 8.09.3 release focuses on API and architecture cleanups in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs. When out, the final 8.09.3 release will be recommended for all users of Midgard. This release includes several major - backward compatible - improvements and fixes. Main changes from 8.09.2: MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599) There is a new online help and documentation viewer Safari user experience has been greatly improved (#583, #585) Basic authentication on Midgard level has been fixed (#485) MidCOM cron is now automatically set up for new virtual hosts (#378) All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477) Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564 File attachments now have MultiLang emulation (#420) In-page Ajax editing can now be disabled and enabled globally (#526) Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625) HTTP errors can be mapped to notifications or special logging (#305) The Midgard PHP extension is now approximately 50% faster In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 RagnaroekPlanned for next maintenance release: More performance tuning Unit tests for midgard-php and MidCOM DBA layers New Midgard visual guidelines deployed more widely Filesync git integration for collaborative site development MidCOM packages distributed by a Midgard-powered PEAR channel See the full list in:http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=prioritySource downloadshttp://www.midgard-project.org/download/Binary packageshttp://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/Getting startedhttp://www.midgard-project.org/documentation/getting-started/Issue trackerhttp://trac.midgard-project.org/roadmapMore informationPiotr Pokora, Midgard release managerpiotrek.pokora(at)gmail.com Henri Bergius, Midgard bug masterhenri.bergius(at)iki.fiThe Midgard Projecthttp://www.midgard-project.org/ [Less]

Lodz, December 15h 2008 -- The Midgard Project has released a release candidate for the third maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software content management framework.The 8.09.3 ... [More] release focuses on API and architecture cleanups in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs. When out, the final 8.09.3 release will be recommended for all users of Midgard.Main changes from 8.09.2: MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599) There is a new online help and documentation viewer Safari user experience has been greatly improved (#583, #585) Basic authentication on Midgard level has been fixed (#485) MidCOM cron is now automatically set up for new virtual hosts (#378) All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477) Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564 File attachments now have MultiLang emulation (#420) In-page Ajax editing can now be disabled and enabled globally (#526) Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625) HTTP errors can be mapped to notifications or special logging (#305) The Midgard PHP extension is now approximately 50% faster In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 RagnaroekPlanned for next maintenance release: More performance tuning Unit tests for midgard-php and MidCOM DBA layers New Midgard visual guidelines deployed more widely Filesync git integration for collaborative site development MidCOM packages distributed by a Midgard-powered PEAR channel See the full list in:http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=prioritySource downloadshttp://www.midgard-project.org/download/Binary packageshttp://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/Getting startedhttp://www.midgard-project.org/documentation/getting-started/Issue trackerhttp://trac.midgard-project.org/roadmapMore informationPiotr Pokora, Midgard release managerpiotrek.pokora(at)gmail.com Henri Bergius, Midgard bug masterhenri.bergius(at)iki.fiThe Midgard Projecthttp://www.midgard-project.org/ [Less]

As part of the Midgard Gathering held in Espoo, Finland last weekend, Midgard's SVN repository was reorganized to follow the new release synchronicity strategy. The repository is now organized in the following way: trunk: The next generation of ... [More] Midgard that is currently under development, at the moment 9.03 Vinland branches/ragnaroek: Midgard 8.09 Ragnaroek LTS branches/thor: Midgard 1.8 and MidCOM 2.8 branches/loki: Midgard 1.7 and MidCOM 2.6 branches/classic: Midgard 1.6 and MidCOM 2.4 Under each of these there are two subdirectories: midgard: Midgard core and language bindings midcom: The Midgard components framework The policy on working with Midgard sources is that each generation branch, and Midgard trunk should be kept stable. To make larger changes possible, it is recommended that developers utilize git-svn and feature branches for their work. To make a local git checkout of Midgard's SVN repository, use the following command: git svn clone https://svn.midgard-project.org/midgard/ -T trunk -b branches -t tags For working with Git, there are some useful tutorials: Git SVN crash course How to track multiple SVN branches in git Feature branches in Midgard development with git Commit access to the repository can be requested from the VCS Tyrant Eero af Heurlin, who also monitors all commits. The same username and password as used on this site is applicable with Midgard SVN. [Less]

Lodz, November 3rd 2008 -- The Midgard Project has released the secondmaintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is aLong Term Support version of the free software content managementframework.The 8.09.2 release focuses on major ... [More] performance improvements and easeof upgrade from earlier Midgard 1.8 installations. It is the firstmaintenance release in the Ragnaroek series that combines both Midgardand MidCOM.The version 8.09.2 is recommended to all users of Midgard 1.8 and 8.09.Main changes from 8.09.0: MySQL errors when upgrading old databases have been fixed (#355) SQL queries generated by MidCOM's DBA layer have been optimized (#412) Midgard now sets up a standalone Asgard administrative interface for all new site setups (#36 and #329) MidCOM has a new handler for catching PHP Exceptions (#352) MidCOM DBA is bypassed for configuration and element loading (#414 and #415) Midgard Collector is now able to query metadata properties (#417) MultiLang support has been improved with index articles and attachments (#288 and #420) Debian and Ubuntu packages now automatically install memcached and SOLR (#380 and #381) Datagard upgrade from 1.8 now installs same MidCOM packages to Ragnaroek (#363) Swedish translations are now included In total 98 tickets have been closed for this release. See the Midgardissue tracker for a full list:http://trac.midgard-project.org/query?status=closed&milestone=8.09.2 RagnaroekPlanned for next maintenance release: More performance tuning Changing MidCOM DBA from subclasses to decorators Unit tests for midgard-php and MidCOM DBA layers New Midgard visual guidelines deployed more widely Filesync git integration for collaborative site development See the full list in:http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&milestone=8.09.3 RagnaroekSource downloadshttp://www.midgard-project.org/download/Binary packageshttp://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/Getting startedhttp://www.midgard-project.org/documentation/getting-started/Issue trackerhttp://trac.midgard-project.org/roadmapMore informationPiotr Pokora, Midgard release managerpiotrek.pokora(at)gmail.comHenri Bergius, Midgard bug masterhenri.bergius(at)iki.fiThe Midgard Projecthttp://www.midgard-project.org/ [Less]

The Midgard Project switched to a new synchronized release model with the 8.09 "Ragnaroek LTS" release. Synchronized release model means that a major release of Midgard will happen every six months, tuned to be part of the larger Linux software ... [More] ecosystem as described by Mark Shuttleworth: WHAT IF you knew that the next long-term supported releases of Ubuntu, Debian, Red Hat and Novell Linux would all have the same major versions of kernel, GCC, X, GNOME, KDE, OO.o and Mozilla. Would that make a major difference for you? I’m willing to bet not - that from a customer view, folks who prefer X will still prefer X. A person who prefers Red Hat will stick with Red Hat. But from a developer view, would that make it easier to collaborate? Dramatically so. Another member of the audience came up to talk about the fashion industry. That’s also converged on a highly coordinated model - fabrics and technologies “release” first, then designers introduce their work simultaneously at fashion shows around the world. “Spring 2009″ sees new collections from all the major houses, many re-using similar ideas or components. That hasn’t hurt their industry, rather it helps to build awareness amongst the potential audience. The same model has been employed very successfully by major projects like GNOME, Eclipse and the Ubuntu distribution. As Midgard relies on many GNOME technologies, being in the same release cycle with them helps our development immensely, and makes Midgard more easy to install because we have a more stable set of dependencies. This coming weekend Midgard developers will convene in Otaniemi, Espoo, Finland to discuss the plans for the next release, 9.03 "Vinland", the first release to be fully legacy free. The Coccinella IM project which also utilizes the synchronized release model has posted a list of release synchronicity myths and facts. [Less]

  Binary packages (including i586 and amd64) are available for downloads and installs. Midgard 8.09 repository is hosted on OpenSuse Build System. www.midgard-project.org provides apt-get friendly mirror for Debian administrators. Please follow debian related documents which also contain repository addresses.    

  We just made MidCOM 8.09.1 hotfix release. It fixes important privilege inheritance bug. Additionall, there's also new org_routamc_photostream package, which fixes random problems with image uploads. Small fixes included in midgard_admin_asgard ... [More] and midcom_helper_reflector. If you have "Ragnaroek" installed, update those packages with pear: pear install ragnaroek/midcom pear install ragnaroek/org_routamc_photostream pear install ragnaroek/midgard_admin_asgard pear install ragnaroek/midcom_helper_reflector You can also update them with datagard: datagard -a pear Note that datagard perform every single package update, so it may take some.           [Less]

Lodz, October 7th 2008 -- The Midgard Project has released stable release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end web services. About ... [More] this release. Midgard 8.09.0 "Ragnaroek LTS" release is another release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu. Midgard 8.09.0 "Ragnaroek LTS" is a Long Term Support version of Midgard for which bug fixes and minor feature improvements will be supplied by the Midgard community for several years. It is recommended that all Midgard users upgrade their installations to the Midgard 8.09 series for stability, performance and maintainance reasons. Upgrade from MidCOM 2.8 installations running with PHP5 has been made as seamless as possible. The version is targeted to ease transition from web services using the deprecated Midgard 1.x APIs to the new Midgard2 architecture. Because of this, the release provides both API versions. This means that the release can be used to run both Midgard 1 applications like the version 2.9 of the MidCOM component framework, and Midgard2 applications like MidCOM3. Changes from Midgard 1.8 and MidCOM 2.8: Midgard and MidCOM now follow an unified release schedule and roadmap There is a new command-line database and website setup utility There is a new Site Wizard web interface for website creation PHP4 support has been removed in favor of PHP5 GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons Repligard package has been removed and replaced by new built in replication API The MidCOM framework uses autoloading to reduce memory usage and processing time Prototype Javascript framework has been removed in favor of jQuery New Midgard logo and graphical guidelines have been deployed across the system Packages are built for several Linux distributions using the openSuse Build Service Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5 midgard-config command-line tool replaced with Midgard configuration supported by pkg-config In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers: D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API Event handling also available for languages without event support (like PHP5) New authentication and user management API New API for objects' attachments and parameters New API for binary blobs Planned for next releases Long Term Supported Midgard 8.09 "Ragnaroek" version First Midgard 9.03 ("Midgard2") stable release: March 2009 Targeted as general, replicated persistent storage framework reaching further than just the web Automated database MgdSchema management and table initialization Language bindings for Python and Mono (.Net) Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3") XMPP Peer-to-Peer replication Removed Apache module Redesigned and web server independent PHP extension (Apache and Lighttpd support) Development coordinated via Git instead of Subversion About Midgard Midgard is a capable open source content management package targeted for mid-to-high-end websites. The Midgard community has always focused on clean and manageable code, high security and multilingual support in the toolkit. Some feature highlights: Modular system that allows construction of a site by creating a directory hierarchy powered by different components Powerful templating of all output in the system Highly configurable content entry views Full caching of generated pages and uploaded file attachments "Double click to edit" on-site WYSIWYG editing Comprehensive access controls Content replication for clustered setups and staging/live publishing Hosting multiple sites and organizations within one Midgard installation Full-text search powered by SOLR The components available for Midgard provide functionality ranging from typical content-oriented websites to highly personalized web services supporting features like geographical positioning and recommendation mining. Several Midgard components include integration features for synchronizing content from popular Social Web services like Flickr, Jaiku and Twitter. Midgard includes: System library for persistent storage, replication and interprocess communication Apache module for HTTP request mapping PHP5 extension for object-oriented data handling API MidCOM MVC framework for PHP5 Content management tools and user interfaces Additional components that may be installed using the PEAR package management tool Get started with Midgard today! Licensing Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL) Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License System requirements Linux, Unix or any POSIX server Apache 2.x HTTP server GLib 2 C library PHP 5.x programming language MySQL 5.x database APC or other PHP byte code cache recommended 1GB of RAM or more recommended (with MidCOM3 256MB is enough) Find out more about Midgard Download page and changelog of latest release Documentation wiki Unofficial Midgard wiki Trac bug and project tracker Ohloh analysis on Midgard sources Midgard Community Since 1999, Midgard has been worked on by an international team of free software developers. Unlike many other open source CMS projects, Midgard is not controlled by a single corporation, but instead the development work is coordinated and shared by a cluster of organizations mainly located in north Europe. All decisions and development directions in the community are discussed openly, and the decisions are made in Midgard Gatherings - events that are arranged twice a year. Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community Mailing lists Users' forum Developers' forum IRC: #midgard on irc.freenode.net #Midgard on Jaiku More information Piotr Pokora, Midgard release manager piotrek.pokora(at)gmail.com Henri Bergius, Midgard spokesman henri.bergius(at)iki.fi The Midgard Project website www.midgard-project.org [Less]

Lodz, October 2nd 2008 -- The Midgard Project has released second 'Release Canditate' release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end ... [More] web services. About this release Midgard 8.09.0RC "Ragnaroek LTS" release is the fourth release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu. When finalized, the 8.09 "Ragnaroek LTS" will be a Long Term Support version of Midgard for which bug fixes and minor feature improvements will be supplied by the Midgard community for several years. It is recommended that all Midgard users upgrade their installations to the Midgard 8.09 series for stability, performance and maintainance reasons. Upgrade from MidCOM 2.8 installations running with PHP5 has been made as seamless as possible. The version is targeted to ease transition from web services using the deprecated Midgard 1.x APIs to the new Midgard2 architecture. Because of this, the release provides both API versions. This means that the release can be used to run both Midgard 1 applications like the version 2.9 of the MidCOM component framework, and Midgard2 applications like MidCOM3. Changes from Midgard 1.8 and MidCOM 2.8: Midgard and MidCOM now follow an unified release schedule and roadmap There is a new command-line database and website setup utility There is a new Site Wizard web interface for website creation PHP4 support has been removed in favor of PHP5 GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons Repligard package has been removed and replaced by new built in replication API The MidCOM framework uses autoloading to reduce memory usage and processing time Prototype Javascript framework has been removed in favor of jQuery New Midgard logo and graphical guidelines have been deployed across the system Packages are built for several Linux distributions using the openSuse Build Service Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5 midgard-config command-line tool replaced with Midgard configuration supported by pkg-config In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers: D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API Event handling also available for languages without event support (like PHP5) New authentication and user management API New API for objects' attachments and parameters New API for binary blobs Planned for next releases First stable release of 8.09 ("Ragnaroek LTS"): October 6th, 2008 Long Term Supported Midgard version First Midgard 9.03 ("Midgard2") stable release: March 2009 Targeted as general, replicated persistent storage framework reaching further than just the web Automated database MgdSchema management and table initialization Language bindings for Python and Mono (.Net) Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3") XMPP Peer-to-Peer replication Removed Apache module Redesigned and web server independent PHP extension (Apache and Lighttpd support) Development coordinated via Git instead of Subversion About Midgard Midgard is a capable open source content management package targeted for mid-to-high-end websites. The Midgard community has always focused on clean and manageable code, high security and multilingual support in the toolkit. Some feature highlights: Modular system that allows construction of a site by creating a directory hierarchy powered by different components Powerful templating of all output in the system Highly configurable content entry views Full caching of generated pages and uploaded file attachments "Double click to edit" on-site WYSIWYG editing Comprehensive access controls Content replication for clustered setups and staging/live publishing Hosting multiple sites and organizations within one Midgard installation Full-text search powered by SOLR The components available for Midgard provide functionality ranging from typical content-oriented websites to highly personalized web services supporting features like geographical positioning and recommendation mining. Several Midgard components include integration features for synchronizing content from popular Social Web services like Flickr, Jaiku and Twitter. Midgard includes: System library for persistent storage, replication and interprocess communication Apache module for HTTP request mapping PHP5 extension for object-oriented data handling API MidCOM MVC framework for PHP5 Content management tools and user interfaces Additional components that may be installed using the PEAR package management tool Get started with Midgard today! Licensing Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL) Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License System requirements Linux, Unix or any POSIX server Apache 2.x HTTP server GLib 2 C library PHP 5.x programming language MySQL 5.x database APC or other PHP byte code cache recommended 1GB of RAM or more recommended (with MidCOM3 256MB is enough) Find out more about Midgard Download page and changelog of latest release Documentation wiki Unofficial Midgard wiki Trac bug and project tracker Ohloh analysis on Midgard sources Midgard Community Since 1999, Midgard has been worked on by an international team of free software developers. Unlike many other open source CMS projects, Midgard is not controlled by a single corporation, but instead the development work is coordinated and shared by a cluster of organizations mainly located in north Europe. All decisions and development directions in the community are discussed openly, and the decisions are made in Midgard Gatherings - events that are arranged twice a year. Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community Mailing lists Users' forum Developers' forum IRC: #midgard on irc.freenode.net #Midgard on Jaiku More information Piotr Pokora, Midgard release manager piotrek.pokora(at)gmail.com Henri Bergius, Midgard spokesman henri.bergius(at)iki.fi The Midgard Project website www.midgard-project.org [Less]

Lodz, September 29th 2008 -- The Midgard Project has released first 'Release Canditate' release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end ... [More] web services. About this release Midgard 8.09.0RC "Ragnaroek LTS" release is the third release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu. When finalized, the 8.09 "Ragnaroek LTS" will be a Long Term Support version of Midgard for which bug fixes and minor feature improvements will be supplied by the Midgard community for several years. It is recommended that all Midgard users upgrade their installations to the Midgard 8.09 series for stability, performance and maintainance reasons. Upgrade from MidCOM 2.8 installations running with PHP5 has been made as seamless as possible. The version is targeted to ease transition from web services using the deprecated Midgard 1.x APIs to the new Midgard2 architecture. Because of this, the release provides both API versions. This means that the release can be used to run both Midgard 1 applications like the version 2.9 of the MidCOM component framework, and Midgard2 applications like MidCOM3. Changes from Midgard 1.8 and MidCOM 2.8: Midgard and MidCOM now follow an unified release schedule and roadmap There is a new command-line database and website setup utility There is a new Site Wizard web interface for website creation PHP4 support has been removed in favor of PHP5 GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons Repligard package has been removed and replaced by new built in replication API The MidCOM framework uses autoloading to reduce memory usage and processing time Prototype Javascript framework has been removed in favor of jQuery New Midgard logo and graphical guidelines have been deployed across the system Packages are built for several Linux distributions using the openSuse Build Service Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5 midgard-config command-line tool replaced with Midgard configuration supported by pkg-config In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers: D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API Event handling also available for languages without event support (like PHP5) New authentication and user management API New API for objects' attachments and parameters New API for binary blobs Planned for next releases First stable release of 8.09 ("Ragnaroek LTS"): October 6th, 2008 Long Term Supported Midgard version First Midgard 9.03 ("Midgard2") stable release: March 2009 Targeted as general, replicated persistent storage framework reaching further than just the web Automated database MgdSchema management and table initialization Language bindings for Python and Mono (.Net) Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3") XMPP Peer-to-Peer replication Removed Apache module Redesigned and web server independent PHP extension (Apache and Lighttpd support) Development coordinated via Git instead of Subversion About Midgard Midgard is a capable open source content management package targeted for mid-to-high-end websites. The Midgard community has always focused on clean and manageable code, high security and multilingual support in the toolkit. Some feature highlights: Modular system that allows construction of a site by creating a directory hierarchy powered by different components Powerful templating of all output in the system Highly configurable content entry views Full caching of generated pages and uploaded file attachments "Double click to edit" on-site WYSIWYG editing Comprehensive access controls Content replication for clustered setups and staging/live publishing Hosting multiple sites and organizations within one Midgard installation Full-text search powered by SOLR The components available for Midgard provide functionality ranging from typical content-oriented websites to highly personalized web services supporting features like geographical positioning and recommendation mining. Several Midgard components include integration features for synchronizing content from popular Social Web services like Flickr, Jaiku and Twitter. Midgard includes: System library for persistent storage, replication and interprocess communication Apache module for HTTP request mapping PHP5 extension for object-oriented data handling API MidCOM MVC framework for PHP5 Content management tools and user interfaces Additional components that may be installed using the PEAR package management tool Get started with Midgard today! Licensing Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL) Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License System requirements Linux, Unix or any POSIX server Apache 2.x HTTP server GLib 2 C library PHP 5.x programming language MySQL 5.x database APC or other PHP byte code cache recommended 1GB of RAM or more recommended (with MidCOM3 256MB is enough) Find out more about Midgard Download page and changelog of latest release Documentation wiki Unofficial Midgard wiki Trac bug and project tracker Ohloh analysis on Midgard sources Midgard Community Since 1999, Midgard has been worked on by an international team of free software developers. Unlike many other open source CMS projects, Midgard is not controlled by a single corporation, but instead the development work is coordinated and shared by a cluster of organizations mainly located in north Europe. All decisions and development directions in the community are discussed openly, and the decisions are made in Midgard Gatherings - events that are arranged twice a year. Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community Mailing lists Users' forum Developers' forum IRC: #midgard on irc.freenode.net #Midgard on Jaiku More information Piotr Pokora, Midgard release manager piotrek.pokora(at)gmail.com Henri Bergius, Midgard spokesman henri.bergius(at)iki.fi The Midgard Project website www.midgard-project.org [Less]