[commits] [Wiki] changed: Project/SplitGitRepo

[Jan Schneider]

jan  Tue, 30 May 2017 20:24:22 +0000

Modified page: https://wiki.horde.org/Project/SplitGitRepo
New Revision:  21
Change log:  Ideas for a roadmap

@@ -10,11 +10,34 @@

  All developers.

  ++ Description
+
++++ Steps for the split
+
+# Notify mailing lists
+# Split git repo with framework/bin/horde-git-split-all
+# Set up email updates for new repo
+# Add files to new repo
+  * .travis.ini, .travis.yml
+  * .gitignore
+# Create FRAMEWORK_5_2 branch in libraries
+# Update website
+
+Later:
+
+# Use more standard directory layout
+  * phpunit.xml and other dev tool configurations in base directory.
+  * README -> README.rst and COPYING -> LICENSE, and move to base directory.
+  * PSR-4 layout
+# Generate documentation for each repo
+# Add package-specific entries to bugs.horde.org
+
++++ Todos

  Global:

+# **O** Prepare website with new instructions
  # **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
@@ -28,26 +51,8 @@
    * **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-"?