Late July sees a lot of changes in the Midgard Components Framework project. Since its appearance in March 2003, MidCOM has established itself as the standard way of building and managing Midgard CMS sites.
There has been lots of evolution during the way, but the current set of changes is a quite major one:
- Torben Nehmer, the father of the project stepped down as the maintainer in favor of Tarjei Huse
- The project has migrated from CVS to a new Subversion repository
- New build system powered by Phing is under work to replace the custom PEAR packaging scripts
Phing can also be used now for generating components from a template:
$ phing scaffold -Dmodule=some.component.name
In addition to actual project management and maintenance changes, there is discussion of two interesting points on the developer forum:
BTW, is there anybody from Pearified reading this? I’m wondering if we could get Icons_Tango repackaged using Role_Web so that the images would automatically go under DocumentRoot for easier serving. I could do this easily myself, but I’d rather keep the package on Pearified.