Split Git Repo into individual components.

Bugs

N/A

People

All developers.

Description

Global:

1. Create script to automatically build list of apps/libs (for use by install script)
   • Get all repos via https://api.github.com/orgs/horde/repos
     • Check for horde.yml files at https://raw.githubusercontent.com/horde/[REPO]/master/horde.yml
2. Create single installation script
   • This script can create/clone the git repos as needed.
     • All repos will be stored in a base folder
     • Option to create a separate, web-accessible directory.
     • Includes stuff in framework/bin
     • Includes stuff in horde-support/maintenance-tools
     • 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).
     • Use Horde_Pear libs to query for list of packages to install
     • This script can be packaged via PHAR
       • Allow config file
3. Create autoloader driver for use with script-facilitated development install
4. Create Vagrant image to allow for testing/development

For each application and library:

1. 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)

1. 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
2. Generate documentation for each repo
3. 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?)

---

Back to the Project List