Chuck Hagenbuch

The November board meeting, already over a week ago (there was also this little election here in the U.S. that occupied a wee bit of my time), was quite productive. I'll give the link to the full log up front; I'm just going to talk about the process of moving libraries over to both Horde 4 code and to the new git repositories. Porting framework packages over is our current Horde 4 priority (over new applications, but not over Horde 3.3 application releases), and the process will be:

1. Write down the new coding standards for Horde 4 libraries. These have been developing somewhat organically, but they need to be codified - what is the package layout, what capitalization, what PHP 5 features to emphasize, what not to use, etc.
2. Focus on converting our existing libraries. Libraries will be moved to the main git repository when:
   1. The code has been reviewed, updated for the new coding standards, potentially refactored
   2. Unnecessary dependencies have been eliminated
   3. Wherever possible they should work without assuming a Horde configuration, $registry instance, etc.
   4. There should be at least basic unit tests
3. When a library is moved to git, it will be deleted from CVS HEAD
4. Applications will be tweaked (in CVS) to work with the newly refactored Horde 4 packages

Some libraries (Autoloader, Log, Support, ...) are already in git as they are already Horde 4 code; several others such as Db, Feed, Argv, ... will join them soon in the move from CVS. The rest - all 80-some other libraries in the current Horde Framework - will be converted over next.