Horde CVS Modules

The following modules are in the Horde CVS Repository, with the listed production level code tags available. If no tags are listed, then there has not yet been a stable release of that module.

All modules have the HEAD tag available, which contains the current bleeding-edge code.

Module Release Description Tags Status
horde3.3.4 The core Horde libraries and frameworkFRAMEWORK_3, RELENG_2, STABLE_1_2Production
framework  Horde Framework librariesFRAMEWORK_3Production
 
agora  Forum moduleFRAMEWORK_3Beta
anselH3 (1.0) Photo Gallery applicationFRAMEWORK_3Production
beatnik  DNS record management user interfaceDevelopment
choraH3 (2.1) HEAD is only supported in git. CVS HEAD WILL NOT WORK
CVS repository front-end		FRAMEWORK_3, RELENG_1Production
dimpH3 (1.1.2) HEAD is only supported in git. CVS HEAD WILL NOT WORK
Dynamic IMP		FRAMEWORK_3Production
forwardsH3 (3.1) E-Mail forwarding moduleFRAMEWORK_3, RELENG_1, RELENG_2Production
genie  Wishlist applicationBeta
gollemH3 (1.1) Web-based File ManagerFRAMEWORK_3Production
goops  Meta search engineBeta
hermesH3 (1.0) Time-tracking/billing data systemFRAMEWORK_3Production
hordedoc  Horde documentation project
hordeweb  The horde.org website
impH3 (4.3.4) HEAD is only supported in git. CVS HEAD WILL NOT WORK
The IMP Webmail Client		FRAMEWORK_3, RELENG_3, STABLE_2_2Production
incubator  Projects that are in development - "incubating"Alpha, Beta, Experimental
ingoH3 (1.2.1) Mail filtering administrationFRAMEWORK_3, RELENG_1Production
jetaH3 (1.0) HEAD is only supported in git. CVS HEAD WILL NOT WORK
Wrapper around the Java Telnet App		FRAMEWORK_3Production
jonah  RSS/News moduleBeta
juno  Checkbook tracking moduleAlpha
klutzH3 (1.0) Comics moduleFRAMEWORK_3, RELENG_1Production
kronolithH3 (2.3.1) HEAD is only supported in git. CVS HEAD WILL NOT WORK
Calendar and scheduling		FRAMEWORK_3, RELENG_1Production
luxor  LXR PortBeta
merk  Online shopping systemBeta
midas  Ad/banner serving and managementBeta
mimpH3 (1.1.1) HEAD is only supported in git. CVS HEAD WILL NOT WORK
A Mobile (WAP, etc.) version of IMP		FRAMEWORK_3Production
mnemoH3 (2.2.1) A Memo/Notepad applicationFRAMEWORK_3, RELENG_1Production
mottle  MOTD toolAlpha
nagH3 (2.3.2) Task ManagerFRAMEWORK_3, RELENG_1Production
nic  Basic network service monitoringBeta
passwdH3 (3.1) Password changing moduleFRAMEWORK_3, RELENG_1, RELENG_2Production
presentations  Horde-related presentations
sam  A Spam Assassin moduleBeta
scry  Polls applicationFRAMEWORK_3Beta
sesha  Inventory managerBeta
skeleton  A template for new Horde applications
sork  Alias for accounts, forwards, passwd, and vacation
swoosh  SMS messengerBeta
trean  Bookmarks managerBeta
turbaH3 (2.3.1) Contacts/Addressbook systemFRAMEWORK_3, RELENG_1Production
ulaform  A form generation/processing toolBeta
vacationH3 (3.1) E-Mail vacation notice moduleFRAMEWORK_3, RELENG_1, RELENG_2Production
vilma  Virtual email domain administratorAlpha
volos  Guestbook applicationBeta
whupsH3 (1.0) A project management systemFRAMEWORK_3Production
wicked  A WikiFRAMEWORK_3Production

When checking out applications, you should probably check out horde first, then cd horde, and then check out any additional modules that you want. hordeweb, hordedoc, and presentations are the exceptions to this; the documentation and presentations can live wherever you like, and the website should probably live elsewhere in your web tree.

A note on stability

The HEAD branch of a module will almost always be development code, and may be unstable. The stability listed for each module is the general state of that module. However, just because that IMP and Horde are listed as Production quality software, doesn't mean that HEAD will always work, be documented, compile, or not cause frogs to dive-bomb you from tall trees. You've been warned. ;)

A note on tags

The tags generally take one of three formats:

  1. HEAD -- This is always the current development branch, and may be unstable and undocumented. Any code that has not yet been released will have only a HEAD branch. All other branches will be branches off the HEAD branch.
  2. FRAMEWORK_* -- These branches are created for major stable releases. Modules with a FRAMEWORK_* tag are compatible with each other. For example, IMP FRAMEWORK_3 is compatible with Horde FRAMEWORK_3.
  3. RELENG_* -- These are the RELease ENGineering branches. These branches are the code for the next releases. Each RELENG branch is identified by a number which indicates the version of the software. So RELENG_1 corresponds to the 1.x releases, RELENG_2 to the 2.x releases, RELENG_3 to the 3.x releases, and so on. These tags are obsolete. Use the FRAMEWORK_* tags instead.
  4. There are other tags available, but there use is not generally needed or recommended, or have been obsoleted, and hence they are not discussed here.