[[toc]]

• Split Git Repo into individual components.

++ Bugs

N/A

++ People

All developers.

++ Description

Global:

X Create script to automatically build list of apps/libs (for use by install script)

• X Get all repos via https://api.github.com/orgs/horde/repos
• X Check for horde.yml files at https://raw.githubusercontent.com/horde/[REPO]/master/horde.yml

O Create single installation script

• X This script can create/clone the git repos as needed.
• X All repos will be stored in a base folder
• X Option to create a separate, web-accessible directory.
• O Includes stuff in framework/bin
• O Includes stuff in horde-support/maintenance-tools
• O Includes the groupware install code (in fact, the Horde_Core_Bundle code is probably a good place to start in terms of creating the install script).
• O Use Horde_Pear libs to query for list of packages to install
• O This script can be packaged via PHAR
  • O Allow config file

O Create autoloader driver for use with script-facilitated development install

O Create Vagrant image to allow for testing/development

For each application and library:

Split git repo

• Tool at framework/bin/horde-git-split
  • Example: ./horde-git-split --component Imap_Client -- horde_imap_client_3
• Stored in separate git repo.
  @@--- # Merge master into FRAMEWORK_5_2 for all libraries @@ (Only necessary when doing the split //after// the Horde 6 release)

Add files to new repo

• composer.json
  • Ensure that composer.json points to packagist/composer install paths instead of PEAR
• Travis
  • .travis.ini, .travis.yml
• Need to add gitignore files for each repo (the release script uses this to know not to add e.g., .git/* files to package.xml.

Set up email updates for new repo

Generate documentation for each repo

Add package-specific entry to bugs.horde.org (if it doesn't exist)

++ Open Questions (Votes)

• Prefix split repositories with "horde-"?
  • Jan: no
  • Mike: no
• What to do with the "horde" base repository. Delete current "horde" repository and replace it with the current "horde" application, or find a new repository name for the current "horde" application and keep or empty the current "horde" repository.
  • Jan: leaning to the former
  • Mike: leaning to the later (Wouldn't deleting the contents of the current repository mess anyone who has it checked out?)
  • Outcome: use "base" as a name.

Back to the ((Project|Project List))